linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: <Tudor.Ambarus@microchip.com>
To: <Ashish.Kumar@nxp.com>, <marek.vasut@gmail.com>,
	<dwmw2@infradead.org>, <computersforpeace@gmail.com>,
	<miquel.raynal@bootlin.com>, <richard@nod.at>,  <vigneshr@ti.com>,
	<linux-mtd@lists.infradead.org>
Cc: kuldeep.singh@nxp.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] mtd: spi-nor: Rename n25q512a to mt25qu512a(n25q512a)
Date: Fri, 30 Aug 2019 07:16:10 +0000	[thread overview]
Message-ID: <f8e546e3-c175-33e8-f691-963a75fae2f4@microchip.com> (raw)
In-Reply-To: <1567080445-32695-2-git-send-email-Ashish.Kumar@nxp.com>



On 08/29/2019 03:07 PM, Ashish Kumar wrote:
> External E-Mail
> 
> 
> mt25qu512a is rebranded after its spinoff from STM, so it is
> different only in term of operating frequency, JEDEC id
> is same as that of n25q512a.
> SPI_NOR_4B_OPCODES is appended to flash property.
> This flash is tested for Single I/O and QUAD I/O mode on LS1046FRWY.
> 
> Signed-off-by: Kuldeep Singh <kuldeep.singh@nxp.com>
> Signed-off-by: Ashish Kumar <Ashish.Kumar@nxp.com>
> Reviewed-by: Vignesh Raghavendra <vigneshr@ti.com>
> 

Renamed entry to "mt25qu512a (n25q512a)", reworded commit message, ordered entry
by size, dropped comment as it looked redundant and
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git,
spi-nor/next branch.

Thanks,
ta

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

  reply	other threads:[~2019-08-30  7:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-29 12:07 [PATCH v4] mtd: spi-nor: Add flash property for mt35xu02g Ashish Kumar
2019-08-29 12:07 ` [PATCH v4] mtd: spi-nor: Rename n25q512a to mt25qu512a(n25q512a) Ashish Kumar
2019-08-30  7:16   ` Tudor.Ambarus [this message]
2019-08-30  7:16 ` [PATCH v4] mtd: spi-nor: Add flash property for mt35xu02g Tudor.Ambarus

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=f8e546e3-c175-33e8-f691-963a75fae2f4@microchip.com \
    --to=tudor.ambarus@microchip.com \
    --cc=Ashish.Kumar@nxp.com \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=kuldeep.singh@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marek.vasut@gmail.com \
    --cc=miquel.raynal@bootlin.com \
    --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).