From: Michal Marek <mmarek@suse.cz>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: linux-kbuild@vger.kernel.org,
Greg KH <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, Andi Kleen <andi@firstfloor.org>
Subject: Re: [PATCH] scripts/config: properly report and set string options
Date: Tue, 10 Apr 2012 10:57:22 +0200 [thread overview]
Message-ID: <4F83F5F2.1090305@suse.cz> (raw)
In-Reply-To: <201204091802.29839.yann.morin.1998@free.fr>
On 9.4.2012 18:02, Yann E. MORIN wrote:
> Greg, All,
>> How does this fit the Documentation/stable_kernel_rules.txt
>
> Sorry, I was not aware of this list... My bad...
> I'll know for next time. Thanks!
>
>> qualification for a patch to be added to the stable releases?
>
> I believe it qualifies because:
> - it is rather trivial
> - it breaks the build for users that tweak the kernel configuration from
> an upper-layer (aka 'integrated') build-system, using this script which
> is bundled with the kernel in the first place.
> - I am a 'real people', and 'it bothers' me ;-)
>
> OTOH, it does not qualify because:
> - there is no Tested-by:
> - I forgot to specify which version it should be applied to
> - obviously, this fix is not yet in Linus' tree
Of course it's not in Linus' tree. But the point of the Cc: stable line
is that you submit your patch to mainline and don't need to follow up
with an extra submission to stable.
> If you think that the first item, above, warrants a -stable fix, then I'll
> properly re-submit once the patch is in Linus' tree.
>
> Michal, should I re-send an updated patch whithout the CC:stable?
If Greg does not want this for stable, I will drop the line myself.
Michal
next prev parent reply other threads:[~2012-04-10 8:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 12:49 [PATCH] scripts/config: properly report and set string options Yann E. MORIN
2012-04-09 13:22 ` Yann E. MORIN
2012-04-09 14:04 ` Andi Kleen
2012-04-09 15:30 ` Greg KH
2012-04-09 16:02 ` Yann E. MORIN
2012-04-10 8:57 ` Michal Marek [this message]
2012-04-10 13:57 ` Jonathan Nieder
2012-04-10 23:07 ` Yann E. MORIN
2012-04-11 1:33 ` Jonathan Nieder
2012-04-19 21:07 ` Yann E. MORIN
2012-05-15 22:14 ` Michal Marek
2012-05-09 21:27 ` Yann E. MORIN
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=4F83F5F2.1090305@suse.cz \
--to=mmarek@suse.cz \
--cc=andi@firstfloor.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=yann.morin.1998@free.fr \
/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