From: Miquel Raynal <miquel.raynal@bootlin.com>
To: <Tudor.Ambarus@microchip.com>
Cc: vigneshr@ti.com, richard@nod.at, michael@walle.cc,
broonie@kernel.org, linux-mtd@lists.infradead.org,
js07.lee@samsung.com
Subject: Re: [GIT PULL] mtd: spi-nor: Changes for 5.7
Date: Wed, 25 Mar 2020 22:14:06 +0100 [thread overview]
Message-ID: <20200325221406.6b93fa01@xps13> (raw)
In-Reply-To: <3920122.fqK6YPyDo2@192.168.0.120>
Hi Tudor.Ambarus@microchip.com,
<Tudor.Ambarus@microchip.com> wrote on Tue, 24 Mar 2020 14:02:41 +0000:
> Hi,
>
> Here is the SPI NOR PR for 5.7.
>
> I would like to thank Vignesh, Michael and Jungseung for their involvement in
> reviewing patches for this release cycle. You did a great job!
>
> Richard,
>
> Please note that I merged tag 'mtk-mtd-spi-move' into spi-nor/next, in order
> to spare Linus of solving conflicts during the merge window. The mtk-quadspi
> driver is replaced by the new spi-mem spi-mtk-nor driver, which was taken
> through Mark's tree. There was a conflict between this driver move and the
> move of all the SPI NOR controllers under drivers/mtd/spi-nor/controllers/.
>
> Cheers,
> ta
>
> The following changes since commit 11a48a5a18c63fd7621bb050228cebf13566e4d8:
>
> Linux 5.6-rc2 (2020-02-16 13:16:59 -0800)
>
> are available in the Git repository at:
>
> ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git tags/
> spi-nor/for-5.7
>
> for you to fetch changes up to f3f2b7eb2f1c5889b0a7162b6b5a69c0f357befd:
>
> mtd: spi-nor: Enable locking for n25q512ax3/n25q512a (2020-03-24 11:47:52
> +0200)
>
> ----------------------------------------------------------------
> SPI NOR core changes:
> - move all the manufacturer specific quirks/code out of the core,
> to make the core logic more readable and thus ease maintenance.
> - move the SFDP logic out of the core, it provides a better
> separation between the SFDP parsing and core logic.
> - trim what is exposed in spi-nor.h. The SPI NOR controllers drivers
> must not be able to use structures that are meant just for the
> SPI NOR core.
> - use the spi-mem direct mapping API to let advanced controllers
> optimize the read/write operations when they support direct mapping.
> - add generic formula for the Status Register block protection
> handling. It fixes some long standing locking limitations and eases
> the addition of the 4bit block protection support.
> - add block protection support for flashes with 4 block protection
> bits in the Status Register.
>
> SPI NOR controller drivers changes:
> - the mtk-quadspi driver is replaced by the new spi-mem
> spi-mtk-nor driver. Merge tag 'mtk-mtd-spi-move' into spi-nor/next
> to avoid conflicts.
>
> ----------------------------------------------------------------
Pulled into mtd/next.
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2020-03-25 21:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 14:02 [GIT PULL] mtd: spi-nor: Changes for 5.7 Tudor.Ambarus
2020-03-25 21:14 ` Miquel Raynal [this message]
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=20200325221406.6b93fa01@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=broonie@kernel.org \
--cc=js07.lee@samsung.com \
--cc=linux-mtd@lists.infradead.org \
--cc=michael@walle.cc \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
/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).