linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: computersforpeace@gmail.com (Brian Norris)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mxc_nand: fix copy_spare
Date: Sun, 27 Sep 2015 17:21:15 -0700	[thread overview]
Message-ID: <20150928002115.GC34421@google.com> (raw)
In-Reply-To: <1443020848-28813-1-git-send-email-eric@eukrea.com>

On Wed, Sep 23, 2015 at 05:07:28PM +0200, Eric B?nard wrote:
> it was broken by 35d5d20efad8a04c8c002c7f31241dff973977a6
> "mtd: mxc_nand: cleanup copy_spare function"
> 
[...]
> 
> Signed-off-by: Eric B?nard <eric@eukrea.com>
> Cc: Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>

Added Fixes and -stable tags and pushed to linux-mtd.git. Thanks!

Brian

      parent reply	other threads:[~2015-09-28  0:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-23 15:07 [PATCH] mxc_nand: fix copy_spare Eric Bénard
2015-09-23 18:33 ` Uwe Kleine-König
2015-09-24  4:25 ` Baruch Siach
2015-09-28  0:21 ` Brian Norris [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=20150928002115.GC34421@google.com \
    --to=computersforpeace@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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).