-
Notifications
You must be signed in to change notification settings - Fork 0
Conversation
Create bee file with cp linux-5.4.54-339.bee linux-5.4.57-340.bee
Remove the parameter BLK_DEV_SR_VENDOR which no longer exists.
Restore RCU_CPU_STALL_TIMEOUT to its default value (21s). It is unclear, why we changed that.
Change CONFIG_LOG_BUF_SHIFT from its default 17 ot 19. This increases the kernel log buffer from 128k to 512k, which seems to avoid a problem, which causes some log messages from early boot to be lost.
Use patch ported to v5.4.57.
Use patch ported to v5.4.57
Create bee file with cp nvidia_linux-5.4.54-339-440.44-0.bee nvidia_linux-5.4.57-340-440.44-0.bee
Oh, well... rename the branch? |
Please add the tag |
Not necessary for me. |
but for me. new PR incoming... |
Didn't dare, because you might not consider it closed "the right way", so I just mentioned the issue. |
But only in the merge message, which GitHub doesn’t copy the merge commit. I do not mind a |
I try to avoid issue numbers in commits, because the commits can be expected to have a longer persistence than issue numbers and might be dangling at some time. |
What’s the downside? A possibly non-working URL? You click on it, and find out, it’s not working anymore. When our GitHub instance is taken down, we probably won’t be interested in the commits anymore. Advantage are many, one being that GitHub connects the different parts, and looking at a commit, one can quickly go to the issue. But, everybody to their liking. |
I've just explained, why I didn't do it myself. I don't really mind either. |
Update to latest LTR
All "linux" from bee.issues included:
linux remove CONFIG_RCU_CPU_STALL_TIMEOUT=60 : included since ever, no reason, default s 21
linux build watchdog drivers as modules #1821
linux Add CONFIG_IKHEADERS #1822
linux Build i2c-dev driver #1819
linux CONFIG_LOG_BUF_SHIFT=19 #1849
Tested on sigquit (nvidia) and claptrap (nfs server).