linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Vignesh Raghavendra <vigneshr@ti.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>,
	Richard Weinberger <richard@nod.at>
Cc: linux-mtd@lists.infradead.org
Subject: [GIT PULL] CFI and HyperFlash changes for v5.7-rc1
Date: Tue, 24 Mar 2020 15:25:12 +0530	[thread overview]
Message-ID: <9f7fe986-bba8-e7d8-889b-2fff4a2e9a76@ti.com> (raw)

Hi Miquel Richard,

Here is the CFI and HyperFlash related PR for v5.7-rc1

Regards
Vignesh


The following changes since commit 11a48a5a18c63fd7621bb050228cebf13566e4d8:

  Linux 5.6-rc2 (2020-02-16 13:16:59 -0800)

are available in the Git repository at:

  git@gitolite.kernel.org:pub/scm/linux/kernel/git/mtd/linux.git tags/cfi/for-5.7

for you to fetch changes up to b6fe8bc67d2d33a9eff1b0785482bccd14979115:

  mtd: hyperbus: move direct mapping setup to AM654 HBMC driver (2020-03-03 10:13:11 +0530)

----------------------------------------------------------------
HyperBus changes

* Print err msg when compatible is wrong or missing
* Move mapping of direct access window from core to individual drivers

----------------------------------------------------------------
Dirk Behme (1):
      mtd: hyperbus: Add proper error message for missing compatible

Sergei Shtylyov (1):
      mtd: hyperbus: move direct mapping setup to AM654 HBMC driver

 drivers/mtd/hyperbus/hbmc-am654.c    | 12 ++++++++
 drivers/mtd/hyperbus/hyperbus-core.c | 15 ++--------
 2 files changed, 15 insertions(+), 12 deletions(-)
	

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

             reply	other threads:[~2020-03-24  9:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-24  9:55 Vignesh Raghavendra [this message]
2020-03-25 21:13 ` [GIT PULL] CFI and HyperFlash changes for v5.7-rc1 Miquel Raynal

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=9f7fe986-bba8-e7d8-889b-2fff4a2e9a76@ti.com \
    --to=vigneshr@ti.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard@nod.at \
    /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).