Greg K-H
Posts
308Following
90Followers
3331
@kernellogger Now finished with the rest, it's been an "interesting" Saturday... Everyone go update!
1
3
10
Greg K-H
gregkh
@killyourfm Just a short note, your recent #mixtape playlists have been the soundtrack for my recent kernel development and release work for the past few weeks, great work! Many thanks for sharing them!
1
2
15
Greg K-H
gregkh
"The magic to remember is type [ESC]ZZ to save and exit."
"Yes that is an odd set of things to remember."
"I don't know, historical reasons."
"Yes, graphical editors are prettier, but sometimes you will have to use this."
Parents, don't forget to have the uncomfortable conversation with your children about vim _before_ they leave for college and are exposed to the siren-call of vscode.
"Yes that is an odd set of things to remember."
"I don't know, historical reasons."
"Yes, graphical editors are prettier, but sometimes you will have to use this."
Parents, don't forget to have the uncomfortable conversation with your children about vim _before_ they leave for college and are exposed to the siren-call of vscode.
1
9
21
@kees See https://social.kernel.org/notice/ARWvggnOvXny0CUCIa for more details.
0
1
5
@kernellogger Because we moved the date to be further away? So should that be "push back"? "move back"? I don't know, time is hard :)
2
2
2
Greg K-H
gregkh
Turns out almost no one uses extra-long LTS kernels, so let's slowly unwind from that interesting experiment:
https://git.kernel.org/pub/scm/docs/kernel/website.git/commit/?id=5cca06606a7dcb2a0a6b6a818072b81b21287b3b
https://git.kernel.org/pub/scm/docs/kernel/website.git/commit/?id=5cca06606a7dcb2a0a6b6a818072b81b21287b3b
3
13
23
0
0
2
@abergmeier @kernellogger
1) the only incompatibility is "do not send HTML email or modify the text of my message", which all email clients can be configured to disable except for Exchange. So don't use Exchange, even Microsoft kernel developers don't use it.
2) Run the tests on your end first, we provide them all for you to do so locally, don't wait for others to find problems that you could with the tools. To not do that yourself is a bit odd.
Realize that we get 200+ new kernel developers every 3 months, so these huge hurdles don't seem to be all that large to others, perhaps you need a better email client?
Have fun!
1) the only incompatibility is "do not send HTML email or modify the text of my message", which all email clients can be configured to disable except for Exchange. So don't use Exchange, even Microsoft kernel developers don't use it.
2) Run the tests on your end first, we provide them all for you to do so locally, don't wait for others to find problems that you could with the tools. To not do that yourself is a bit odd.
Realize that we get 200+ new kernel developers every 3 months, so these huge hurdles don't seem to be all that large to others, perhaps you need a better email client?
Have fun!
0
0
0
Greg K-H
repeated
repeated
K. Ryabitsev 🍁
monsieuricon
b4 0.12.0 is available
Everyone using "b4 send" must upgrade to stop hitting Python email module bugs.
https://lore.kernel.org/tools/20230120165712.rznwonw6nbfhc7fo@meerkat.local/
Everyone using "b4 send" must upgrade to stop hitting Python email module bugs.
https://lore.kernel.org/tools/20230120165712.rznwonw6nbfhc7fo@meerkat.local/
1
5
13
@Conan_Kudo @tylersaunders ChromeOS has that "rule" and it's regularly flaunted for some subsystems for various, good, reasons.
As you well know, a SoC is a few orders of magnitude more complex than your normal server/desktop so the amount of drivers and kernel code to control it is almost double, and the code sharing from common IP blocks is much less than ideal. So trying to get all code upstream is a task that no SoC vendor seems willing to attempt until much later in the device cycle.
Yes, it would be cheaper and faster to do the work up front to get the code upstream, but SoC vendors have code to burn (actual quote from a QCOM manager to me) and no individual project wants to take the time-hit to save future products time on their upstream work (i.e. short term vs. long term incentives.)
The only real solution is if vendors put in their contracts "code must be upstream" before they buy the chips, that's what fixed it in the Enterprise server space decades ago. But right now, due to an almost monopoly in the SoC market, no one can afford to add that to contracts when making a new phone.
So you have it all here, technical complexity, short-term product deadlines, too much money to care about the problem, and monopolistic markets. Something for everyone to complain about and no single way to solve it.
As you well know, a SoC is a few orders of magnitude more complex than your normal server/desktop so the amount of drivers and kernel code to control it is almost double, and the code sharing from common IP blocks is much less than ideal. So trying to get all code upstream is a task that no SoC vendor seems willing to attempt until much later in the device cycle.
Yes, it would be cheaper and faster to do the work up front to get the code upstream, but SoC vendors have code to burn (actual quote from a QCOM manager to me) and no individual project wants to take the time-hit to save future products time on their upstream work (i.e. short term vs. long term incentives.)
The only real solution is if vendors put in their contracts "code must be upstream" before they buy the chips, that's what fixed it in the Enterprise server space decades ago. But right now, due to an almost monopoly in the SoC market, no one can afford to add that to contracts when making a new phone.
So you have it all here, technical complexity, short-term product deadlines, too much money to care about the problem, and monopolistic markets. Something for everyone to complain about and no single way to solve it.
0
1
2
Greg K-H
gregkh
I've happy to see how well the Steam deck has turned out, and I'm glad to see them get good press for it as well. Long-term maintenance and updates are key and the Valve developers have been doing wonderful with this:
https://www.theverge.com/23513517/steam-deck-long-term-test-valve
Now if only they would switch to use the LTS kernel releases, I'd be totally satisfied.
https://www.theverge.com/23513517/steam-deck-long-term-test-valve
Now if only they would switch to use the LTS kernel releases, I'd be totally satisfied.
0
13
28
Greg K-H
gregkh
When you attempt to rebuild the Fairphone 3 kernel on a modern distro (i.e. Arch) and you get a very odd failure when building the kernel modules, install the `aur/ncurses5-compat-libs` package and then all will work properly.
Took me forever to try to figure out what was wrong with the kernel code itself, should have realized it was the host system issue instead. Hermetic Android builds must have come later in the Android release cycle.
Took me forever to try to figure out what was wrong with the kernel code itself, should have realized it was the host system issue instead. Hermetic Android builds must have come later in the Android release cycle.
0
1
7