From: Borislav Petkov <bp@alien8.de>
To: Greg KH <greg@kroah.com>
Cc: Sergey Shtylyov <s.shtylyov@omp.ru>,
stable <stable@vger.kernel.org>,
Dinh Nguyen <dinguyen@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Tony Luck <tony.luck@intel.com>,
James Morse <james.morse@arm.com>,
Robert Richter <rric@kernel.org>,
linux-edac@vger.kernel.org
Subject: Re: [PATCH 1/2] edac: altera: fix deferred probing
Date: Sat, 29 Jan 2022 11:33:35 +0100 [thread overview]
Message-ID: <YfUX/98NiydSGn9S@zn.tnic> (raw)
In-Reply-To: <YfTjQukS1ad9ZBmK@kroah.com>
On Sat, Jan 29, 2022 at 07:48:34AM +0100, Greg KH wrote:
> If you know you want a patch in the stable tree, add cc: stable.
>
> Because not all maintainers remember to do so, we do dig through all
> patches with just the fixes: tag, and try to backport them if needed,
> but it does not always happen, and there can be long lags as well.
>
> So again, if you know you want it in a stable kernel, add the cc:
> stable.
Thanks for clarifying. I already did so - I figured having cc:stable
won't hurt anyway. Besides, it is an explicit statement that "that patch
is stable material" because Fixes: doesn't always necessarily mean,
stable material.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-01-29 10:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 18:55 [PATCH 0/2] Fix deferred probing in the EDAC drivers Sergey Shtylyov
2022-01-24 18:55 ` [PATCH 1/2] edac: altera: fix deferred probing Sergey Shtylyov
2022-01-26 16:52 ` Dinh Nguyen
2022-01-28 18:36 ` Borislav Petkov
2022-01-28 18:53 ` Sergey Shtylyov
2022-01-28 19:02 ` Sergey Shtylyov
2022-01-28 19:16 ` Borislav Petkov
2022-01-28 19:17 ` Sergey Shtylyov
2022-01-28 19:20 ` Borislav Petkov
2022-01-28 19:35 ` Sergey Shtylyov
2022-01-28 19:47 ` Sergey Shtylyov
2022-01-29 6:48 ` Greg KH
2022-01-29 10:33 ` Borislav Petkov [this message]
2022-01-28 19:53 ` Sergey Shtylyov
2022-01-28 19:56 ` Sergey Shtylyov
2022-01-24 18:55 ` [PATCH 2/2] edac: xgene: " Sergey Shtylyov
2022-01-28 22:39 ` [PATCH 0/2] Fix deferred probing in the EDAC drivers Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YfUX/98NiydSGn9S@zn.tnic \
--to=bp@alien8.de \
--cc=dinguyen@kernel.org \
--cc=greg@kroah.com \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rric@kernel.org \
--cc=s.shtylyov@omp.ru \
--cc=stable@vger.kernel.org \
--cc=tony.luck@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox