public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
	linux-mmc@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, kyungmin.park@samsung.com,
	kgene.kim@samsung.com, ben-linux@fluff.org,
	w.sang@pengutronix.de
Subject: Re: [PATCH] sdhci-s3c: fix NULL ptr access in sdhci_s3c_remove
Date: Sat, 25 Sep 2010 23:53:24 +0100	[thread overview]
Message-ID: <20100925225324.GA30732@void.printf.net> (raw)
In-Reply-To: <20100923120803.832975f6.akpm@linux-foundation.org>

On Thu, Sep 23, 2010 at 12:08:03PM -0700, Andrew Morton wrote:
> The patch applies OK to 2.6.35.  Is the bug present there as well?  If
> so, should we fix it in earlier kernels?  If so then the way in which
> we indicate this is by adding
> 
> 	Cc: <stable@kernel.org>
> 
> to the changelog.

Marek, Kyungmin, what do you think?

Andrew, I've been waiting for an ACK from Ben Dooks, since he's listed
in MAINTAINERS for this driver, but he hasn't replied yet (I've tried 
pinging privately).  I'll plan on sending Marek's two s3c fixes to
Linus tomorrow regardless (this one with Cc: <stable@kernel.org>)
along with my MAINTAINERS update for MMC unless anyone objects.

Thanks,

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

  reply	other threads:[~2010-09-25 22:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-23 14:22 [PATCH] sdhci-s3c: fix NULL ptr access in sdhci_s3c_remove Marek Szyprowski
2010-09-23 19:08 ` Andrew Morton
2010-09-25 22:53   ` Chris Ball [this message]
2010-09-26 10:53     ` Kyungmin Park
2010-09-26 15:25       ` Chris Ball
2010-09-27  6:09     ` Marek Szyprowski
2010-09-23 19:12 ` 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=20100925225324.GA30732@void.printf.net \
    --to=cjb@laptop.org \
    --cc=akpm@linux-foundation.org \
    --cc=ben-linux@fluff.org \
    --cc=kgene.kim@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=w.sang@pengutronix.de \
    /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