linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
	Brian Norris <computersforpeace@gmail.com>,
	David Woodhouse <dwmw2@infradead.org>
Subject: [GIT PULL] MTD updates for 4.4-rc2
Date: Fri, 20 Nov 2015 19:00:26 -0800	[thread overview]
Message-ID: <20151121030026.GA28964@localhost> (raw)

Hi Linus,

The following changes since commit 8005c49d9aea74d382f474ce11afbbc7d7130bec:

  Linux 4.4-rc1 (2015-11-15 17:00:27 -0800)

are available in the git repository at:

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

for you to fetch changes up to 1ddaa021b000220b5f2ad023e4f15ed44990974b:

  MAINTAINERS: brcmnand: Add co-maintainer for Broadcom SoCs (2015-11-18 13:16:58 -0800)

----------------------------------------------------------------
MTD fixes for 4.4-rc2:

 * MAINTAINERS updates for brcmnand driver

 * Fix reboot hangs seen when multiple NAND flash chips are registered with the
   same controller

 * Fix build issues on jz4740 NAND driver; the error was introduced in 4.3, so
   I guess nobody really cared, but we might as well fix it

----------------------------------------------------------------
Brian Norris (2):
      mtd: jz4740_nand: fix build on jz4740 after removing gpio.h
      mtd: nand: fix shutdown/reboot for multi-chip systems

Florian Fainelli (1):
      MAINTAINERS: brcmnand: Add Broadcom internal mailing-list

Kamal Dasu (1):
      MAINTAINERS: brcmnand: Add co-maintainer for Broadcom SoCs

 MAINTAINERS                    |    2 ++
 drivers/mtd/nand/jz4740_nand.c |    1 +
 drivers/mtd/nand/nand_base.c   |    2 +-
 3 files changed, 4 insertions(+), 1 deletion(-)

                 reply	other threads:[~2015-11-21  3:00 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=20151121030026.GA28964@localhost \
    --to=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --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).