From: Ian Molton <ian@mnementh.co.uk>
To: Chris Ball <cjb@laptop.org>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Axel Lin <axel.lin@gmail.com>,
linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: tmio: eliminate unused variable 'mmc' warning
Date: Sat, 27 Aug 2011 20:02:51 +0100 [thread overview]
Message-ID: <1314471775.2138.28.camel@drake> (raw)
In-Reply-To: <m2liva7ize.fsf@bob.laptop.org>
On Wed, 2011-08-03 at 08:55 -0400, Chris Ball wrote:
> > Good for 3.1, do we also push such "harmless" compiler warning fixes
> to
> > stable?
> >
> > Acked-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
>
> Pushed for 3.1, thanks. I don't think this is appropriate for stable.
Why on earth not? its obviously correct...
next prev parent reply other threads:[~2011-08-27 19:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 6:48 [PATCH] mmc: tmio: eliminate unused variable 'mmc' warning Axel Lin
2011-08-03 7:26 ` Guennadi Liakhovetski
2011-08-03 12:55 ` Chris Ball
2011-08-27 19:02 ` Ian Molton [this message]
2011-08-28 18:20 ` Chris Ball
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=1314471775.2138.28.camel@drake \
--to=ian@mnementh.co.uk \
--cc=axel.lin@gmail.com \
--cc=cjb@laptop.org \
--cc=g.liakhovetski@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@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