linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Tudor Ambarus <tudor.ambarus@microchip.com>
To: <Takahiro.Kuwano@infineon.com>, <tkuw584924@gmail.com>,
	<tudor.ambarus@microchip.com>, <michael@walle.cc>,
	<p.yadav@ti.com>
Cc: <linux-mtd@lists.infradead.org>, <miquel.raynal@bootlin.com>,
	<Bacem.Daassi@infineon.com>, <richard@nod.at>, <vigneshr@ti.com>
Subject: Re: [PATCH 0/2] mtd: spi-nor: manufacturers: Replace hardcoded values for addr_nbytes/addr_mode_nbytes
Date: Tue, 25 Oct 2022 05:33:01 +0300	[thread overview]
Message-ID: <166666517334.181018.11114689980548340488.b4-ty@microchip.com> (raw)
In-Reply-To: <20220728041451.85559-1-tudor.ambarus@microchip.com>

On Thu, 28 Jul 2022 07:14:49 +0300, Tudor Ambarus wrote:
> We track in the core the internal address mode of the flash. Stop using
> hardcoded values for the number of bytes of address and use
> nor->addr_nbytes and nor->params->addr_mode_nbytes instead.
> 
> I don't have those flashes to test the changes, so I'll need some
> Tested-by tags.
> 
> [...]

Applied to spi-nor/next, thanks!

[1/2] mtd: spi-nor: spansion: Replace hardcoded values for addr_nbytes/addr_mode_nbytes
      https://git.kernel.org/mtd/c/05ebc1ccb8af
[2/2] mtd: spi-nor: micron-st.c: Replace hardcoded values for addr_nbytes/addr_mode_nbytes
      https://git.kernel.org/mtd/c/2fe99a867050

Best regards,
-- 
Tudor Ambarus <tudor.ambarus@microchip.com>

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

  parent reply	other threads:[~2022-10-25  2:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28  4:14 [PATCH 0/2] mtd: spi-nor: manufacturers: Replace hardcoded values for addr_nbytes/addr_mode_nbytes Tudor Ambarus
2022-07-28  4:14 ` [PATCH 1/2] mtd: spi-nor: spansion: " Tudor Ambarus
2022-07-28  4:27   ` Tudor.Ambarus
2022-07-29  2:35     ` Takahiro Kuwano
2022-07-29  5:32       ` Tudor.Ambarus
2022-07-28  4:14 ` [PATCH 2/2] mtd: spi-nor: micron-st.c: " Tudor Ambarus
2022-10-25  2:33 ` Tudor Ambarus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-07-28  4:13 [PATCH 0/2] mtd: spi-nor: manufacturers: " 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=166666517334.181018.11114689980548340488.b4-ty@microchip.com \
    --to=tudor.ambarus@microchip.com \
    --cc=Bacem.Daassi@infineon.com \
    --cc=Takahiro.Kuwano@infineon.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=michael@walle.cc \
    --cc=miquel.raynal@bootlin.com \
    --cc=p.yadav@ti.com \
    --cc=richard@nod.at \
    --cc=tkuw584924@gmail.com \
    --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).