linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-mmc@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH] mmc: sh_mmcif: fix use after free
Date: Tue, 30 Oct 2012 22:37:19 +0000	[thread overview]
Message-ID: <878vanio2o.fsf@octavius.laptop.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1210302306190.29432@axis700.grange> (Guennadi Liakhovetski's message of "Tue, 30 Oct 2012 23:08:57 +0100 (CET)")

Hi Guennadi,

On Tue, Oct 30 2012, Guennadi Liakhovetski wrote:
>> In future, feel free to note the
>> stable@ situation by adding:
>> 
>>    Cc: stable@vger.kernel.org [3.6]
>
> Hm, a bit confused. I seem to remember, that one of subsystem maintainers, 
> to whom I also submitted a patch, that should also have been forwarded to 
> stable, told me, that adding this "Cc: stable@..." tag was a task of 
> subsystem maintainers, in that case his task, and not of individual 
> submitters, which might only indicate their opinion in this respect. Am I 
> wrong?

Oh, interesting; I haven't seen that complaint myself.  I don't think
there's a kernel-wide rule about this, but I might be wrong.

Personally, I'm happy with receiving the stable@ tag because I like it
when patch authors think about -stable and I want to encourage them to
do so.  (Often they know whether a patch is needed in -stable better
than I do.)

Of course, the stable@ team isn't going to do anything until the patch
enters mainline, and the patch is only going to enter mainline through
my tree after I've had a chance to change the stable@ tag if necessary,
so there's no problem for me there.

Sorry to leave you in the middle of conflicting advice. :-)  The stable@
hint is appreciated in either form; I was just trying to save you some
typing.

Thanks!

- Chris.
-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

      reply	other threads:[~2012-10-30 22:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-23 12:08 [PATCH] mmc: sh_mmcif: fix use after free Guennadi Liakhovetski
2012-10-29 21:23 ` Chris Ball
2012-10-30 22:08   ` Guennadi Liakhovetski
2012-10-30 22:37     ` Chris Ball [this message]

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=878vanio2o.fsf@octavius.laptop.org \
    --to=cjb@laptop.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).