public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@bootlin.com>
To: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Cc: Marek Vasut <marex@denx.de>,
	Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>
Subject: [GIT PULL v2] mtd: spi-nor: Changes for 4.17
Date: Fri, 30 Mar 2018 10:20:34 +0200	[thread overview]
Message-ID: <20180330102034.7db0a4e4@bbrezillon> (raw)

Hello,

Nothing new compared to the v1 expect I added my SoB on Fabio's patch
because I amended my own patch to fix the subject prefix and became
commiter of the 2 other patches during the process.

Regards,

Boris

The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2:

  Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)

are available in the git repository at:

  git://git.infradead.org/linux-mtd.git tags/spi-nor/for-4.17

for you to fetch changes up to e8de85d5a107352ff428f735b0afc8133bcbc3e5:

  dt-bindings: fsl-quadspi: Add the example of two SPI NOR (2018-03-30 10:05:08 +0200)

----------------------------------------------------------------
* Make fsl-quaspi assign different names to MTD devices connected
  to the same QSPI controller
* Remove an unneeded driver.bus assigned in the fsl-qspi driver

----------------------------------------------------------------
Boris Brezillon (1):
      mtd: fsl-quadspi: Remove unneeded driver.bus assignment

Fabio Estevam (2):
      mtd: fsl-quadspi: Distinguish the mtd device names
      dt-bindings: fsl-quadspi: Add the example of two SPI NOR

 Documentation/devicetree/bindings/mtd/fsl-quadspi.txt | 24 ++++++++++++++++++++++++
 drivers/mtd/spi-nor/fsl-quadspi.c                     | 19 ++++++++++++++++++-
 2 files changed, 42 insertions(+), 1 deletion(-)

             reply	other threads:[~2018-03-30  8:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-30  8:20 Boris Brezillon [this message]
2018-04-06  6:58 ` [GIT PULL v2] mtd: spi-nor: Changes for 4.17 Boris Brezillon

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=20180330102034.7db0a4e4@bbrezillon \
    --to=boris.brezillon@bootlin.com \
    --cc=cyrille.pitchen@wedev4u.fr \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marex@denx.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