Re: [PATCH 2/9] EDAC/versalnet: Add NULL check for mci in remove_one_mc()
Borislav Petkov <[email protected]> Sun, 2 Aug 2026 11:52:11 -0700
| Newsgroups | org.kernel.vger.linux-edac,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <20260802185211.GBam-R2waQcPgti5EO@fat_crate.local> |
On Mon, Jul 27, 2026 at 01:41:52PM +0530, Pandey, Radhey Shyam wrote: > Confirm on fixes tag. The bug likely goes back to the original driver. > > Cc: [email protected] > > There is no CC to stable kernel in email. Ok, before you state something like that about kernel process rules, just go to the source and confirm it: Documentation/process/stable-kernel-rules.rst: "Option 1 ******** To have a patch you submit for mainline inclusion later automatically picked up for stable trees, add this tag in the sign-off area:: Cc: [email protected]" So yes, you should very much cc stable. The additional reason being that the stable team will pick up the patch faster instead of them running it through AI, it finding the Fixes tag and determining whether it is backportable material or not. Oh, and if you want that to happen, you better write a good commit message explaining what is happening and under which circumstances and why it needs to be fixed. :-) HTH. -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette