linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
	David Woodhouse <dwmw2@infradead.org>,
	Richard Weinberger <richard@nod.at>,
	Boris Brezillon <boris.brezillon@free-electrons.com>,
	Artem Bityutskiy <dedekind1@gmail.com>
Subject: [GIT PULL] Late MTD fix for v4.5
Date: Fri, 11 Mar 2016 16:01:21 -0800	[thread overview]
Message-ID: <20160312000121.GF2545@google.com> (raw)

Hi Linus,

I have 2 small, late updates for MTD. The fix is trivial and tested.
Both low reward (it's just a test) and even lower risk.

And some suckers^Wlovely people offered to help out maintaining and
reviewing "officially," so we might as well get them in now.

The following changes since commit 44248affb5d82d32cdb58a92a94ce191d4ddee60:

  MAINTAINERS: add maintainer entry for FREESCALE GPMI NAND driver (2016-02-25 11:22:37 -0800)

are available in the git repository at:

  git://git.infradead.org/linux-mtd.git tags/for-linus-20160311

for you to fetch changes up to 9df4f913eb39046fa57c4217bb3429a63e164000:

  MAINTAINERS: add a maintainer for the NAND subsystem (2016-03-10 10:48:04 -0800)

----------------------------------------------------------------
Late MTD fix for v4.5:

 * A simple error code handling fix for the NAND ECC test; this was a
   regression in v4.5-rc1

 * A MAINTAINERS update, which might as well go in ASAP

----------------------------------------------------------------
Boris BREZILLON (1):
      MAINTAINERS: add a maintainer for the NAND subsystem

Jorge Ramirez-Ortiz (1):
      mtd: nand: tests: fix regression introduced in mtd_nandectest

 MAINTAINERS                         | 11 +++++++++++
 drivers/mtd/tests/mtd_nandecctest.c |  2 +-
 2 files changed, 12 insertions(+), 1 deletion(-)

                 reply	other threads:[~2016-03-12  0:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20160312000121.GF2545@google.com \
    --to=computersforpeace@gmail.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=dedekind1@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    --cc=torvalds@linux-foundation.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).