linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@collabora.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	Richard Weinberger <richard@nod.at>, Marek Vasut <marex@denx.de>,
	David Woodhouse <dwmw2@infradead.org>,
	Brian Norris <computersforpeace@gmail.com>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Tudor Ambarus <Tudor.Ambarus@microchip.com>
Subject: [GIT PULL] mtd: Fixes for 5.0/5.0-rc8
Date: Wed, 20 Feb 2019 08:56:53 +0100	[thread overview]
Message-ID: <20190220085653.182aa2c6@collabora.com> (raw)

Hello Linus,

Here are 2 fixes for 5.0 (or -rc8 if you end up delaying the release).

Regards,

Boris

The following changes since commit d13937116f1e82bf508a6325111b322c30c85eb9:

  Linux 5.0-rc6 (2019-02-10 14:42:20 -0800)

are available in the Git repository at:

  git://git.infradead.org/linux-mtd.git tags/mtd/fixes-for-5.0-rc8

for you to fetch changes up to 3e35730dd7540bad2d4e002703996391d9be49a0:

  mtd: powernv_flash: Fix device registration error (2019-02-13 14:19:40 +0100)

----------------------------------------------------------------
- Don't add a digit to MTD-backed nvmem device names
- Make sure powernv flash names are unique

----------------------------------------------------------------
Aneesh Kumar K.V (2):
      mtd: Use mtd->name when registering nvmem device
      mtd: powernv_flash: Fix device registration error

 drivers/mtd/devices/powernv_flash.c | 2 +-
 drivers/mtd/mtdcore.c               | 1 +
 2 files changed, 2 insertions(+), 1 deletion(-)

             reply	other threads:[~2019-02-20  7:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20  7:56 Boris Brezillon [this message]
2019-02-20 17:50 ` [GIT PULL] mtd: Fixes for 5.0/5.0-rc8 pr-tracker-bot

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=20190220085653.182aa2c6@collabora.com \
    --to=boris.brezillon@collabora.com \
    --cc=Tudor.Ambarus@microchip.com \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marex@denx.de \
    --cc=miquel.raynal@bootlin.com \
    --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).