Posts
308
Following
90
Followers
3331
gregkh
repeated
monsieuricon

K. Ryabitsev 🍁

Little known fact: first kernel releases were shipped via the postal service.
7
51
137
gregkh

Greg K-H

Reply to @oleksandr@natalenko.name
@oleksandr @kernellogger @vbabka You can't do that, as many many developers do not properly tag real bugfixes with cc: stable, which is why we now take anything with Fixes: on it, when they seem sane.

Again, the patch that caused you problems here was marked this way so that it did get some "soaking" in linux-next and and delayed the stable backport for a few weeks on purpose. It flowed into stable into the correct way, this is as designed.

Well, except for the breakage, but that's what normally happens with hardware, go blame the vendors for that :)
0
0
0
gregkh

Greg K-H

Reply to @oleksandr@natalenko.name
@oleksandr @kernellogger That commit was tagged that way so it would be properly backported, if it's buggy then please let the developers know about it!
0
0
0
gregkh

Greg K-H

Reply to @oleksandr@natalenko.name
@oleksandr What do you mean by "properly reviewed"? They have all passed the normal review process in that they are in Linus's tree. If they are good enough for the next release, why are they not good enough for the previous one?

And as always, reviews for things that you think should not be included are greatly appreciated, we can't do any of this without you!
0
0
0
gregkh
repeated
axboe@fosstodon.org

Jens Axboe

If you enjoy the hairiest of bug hunts with a thrilling conclusion, this one is for you. The hunt and hair pulling:

https://lore.kernel.org/regressions/480932026.45576726.1699374859845.JavaMail.zimbra@raptorengineeringinc.com/

and the conclusion:

https://lore.kernel.org/regressions/1105090647.48374193.1700351103830.JavaMail.zimbra@raptorengineeringinc.com/

Hats off to Timothy for seeing this one through to completion!

5
10
2
gregkh
repeated
monsieuricon

K. Ryabitsev 🍁

So, you want to read LKML with Gmail (experimental, testers needed)

https://lore.kernel.org/workflows/20231115-black-partridge-of-growth-54bf2e@nitro/
2
14
18
gregkh

Greg K-H

Reply to @exi@donotsta.re
@exi @kernellogger We will finally get to relax at that time. Or at least we can look forward to the potential to relax, providing us hope when buried neck-deep in stable backports...
0
1
3
gregkh

Greg K-H

Reply to @vegard@mastodon.social
@vegard @kernellogger Ah, so back in February we made it 4 years, not 2, so why did everyone freak out a month ago thinking it was going to be 2 years?

Math with dates is hard :)
1
0
1
gregkh

Greg K-H

Reply to @kernellogger@fosstodon.org
@kernellogger Yes, that's why the dates are like this.

And I just realized, we never publicly said anything about "2 years support for LTS", the kernel.org page has always had longer dates, all we said was "we will not be doing 6 years anymore".

So no one actually looks at the documentation we write (i.e. the web page), AND I didn't even remember that we had written that back in February of this year, this feels like a "write once, read never" type of file...
1
1
5
gregkh
repeated
monsieuricon

K. Ryabitsev 🍁

So many truths are hidden,
So many facts untold,
Queries left unbidden,
Concealed below the fold.

My head droops to the table,
But I must remain informed:
"Is the kernel stable?"
"How is babby formed?"
0
31
61
gregkh
repeated
kees@fosstodon.org

Kees Cook (old account)

RFC for the replacing the Linux kernel driver with a fully functional version:

https://lore.kernel.org/lkml/20231101-rust-binder-v1-0-08ba9197f637@google.com/

2
15
3
gregkh
repeated
embeddedrecipes@fosstodon.org

Embedded Recipes

All the talks from Embedded Recipes 2023 are now online, including "The TTY Layer: the Past, Present, and Future" by @gregkh https://www.youtube.com/watch?v=g4sZUBS57OQ&list=PLwnbCeeZfQ_Mi7gjUpLZxXGOcEBS_K8kH&index=5

0
8
3
gregkh

Greg K-H

Reply to @davidrevoy@framapiaf.org
@davidrevoy @standingpad Use email, that's how the kernel is developed and how bugs are reported, send it to the author of that commit and the mailing list listed in the MAINTAINERS file for the subsystem.

No need to file some ticket in some random web form with some odd account, email. It's simple, and easy (note, turn off HTML mode for it please.)

Good luck!
1
0
3
gregkh

Greg K-H

Reply to
@jani The DCO does cover it, it is just that people don't seem to actually understand where the information from these "AI" tools is coming from for some reason...
0
0
3
gregkh

Greg K-H

This came up in a private thread about a kernel patch review where the contents were created with an "AI" tool, so I figured I might as well put it somewhere a bit more public as people don't seem to really understand the issues involved:

My policy is that I do not take any output of any "AI" tools unless the providence of the data that was used to feed the AI tool can be proven to be under the proper copyright rules as to be compatible with the GPLv2 license.

So in other words, nothing from chatgpt at all, that's obviously full of copyrighted works that are not allowed to be reused in this manner.
6
67
95
gregkh

Greg K-H

Reply to @stefanct@chaos.social
@stefanct @kernellogger @LWN We'll figure it out eventually, give us some time :)
0
0
2
gregkh
repeated
kernellogger@fosstodon.org

Thorsten Leemhuis (acct. 1/4)

Edited 1 year ago

6.6 is out: https://lore.kernel.org/all/CAHk-=wiZuU984NWVgP4snp8sEt4Ux5Mp_pxAN5MNV9VpcGUo+A@mail.gmail.com/

"""So this last week has been pretty calm, and I have absolutely no excuses to delay the v6.6 release any more, so here it is. […] Linus"""

For an overview of new features, check out the two 6.6 merge window articles from @LWN or the Kernelnewbies summary:

https://lwn.net/Articles/942954/ and https://lwn.net/Articles/943245/

https://kernelnewbies.org/Linux_6.6

3
5
2
gregkh

Greg K-H

Reply to @kernellogger@fosstodon.org
@kernellogger @LWN It's on the front page now, took a bit for the signed tag to propagate due to timezone differences...
1
0
2
gregkh

Greg K-H

Reply to @jarkko
@jarkko @conor drivers/staging/ is for code that is abandoned by companies and the community needs others to clean/fix it up, it is not for "code just not ready to be merged yet" as it ends up taking more work to get code out of staging into the real part of the kernel than to just do the real work to start with out-of-tree and then submit it to the proper location.

In other words, drivers/staging/ is not a dumping ground for experiments :)

Just do it right, and get it merged upstream correctly.

And why 5.19? That's a long obsolete and insecure kernel version, no one should ever still be using that mess, especially anything purporting to have anything to do with "security" in any form.
1
0
0
gregkh
repeated
mdolan@fosstodon.org

Mike Dolan

Not a tragedy: "The greatest value that foundations bring is the creation of a neutral collaboration hub for everyone participating in, and taking a dependency on, a project."

https://www.linuxfoundation.org/blog/how-open-source-foundations-protect-the-licensing-integrity-of-open-source-projects

0
4
1
Show older
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: