All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pratyush Yadav <pratyush@kernel.org>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	 Richard Weinberger <richard@nod.at>,
	 Tudor Ambarus <Tudor.Ambarus@linaro.org>,
	 Vignesh Raghavendra <vigneshr@ti.com>,
	 Frieder Schrempf <frieder.schrempf@kontron.de>,
	 Michael Walle <michael@walle.cc>,
	Pratyush Yadav <pratyush@kernel.org>,
	 linux-mtd@lists.infradead.org
Subject: Re: [GIT PULL] mtd: Changes for 6.17
Date: Fri, 01 Aug 2025 16:47:13 +0200	[thread overview]
Message-ID: <mafs0v7n7cd5a.fsf@kernel.org> (raw)
In-Reply-To: <87o6t08fen.fsf@bootlin.com>

Hi Miquel,

On Thu, Jul 31 2025, Miquel Raynal wrote:

[...]
> * MTD changes:
>
> Apart from a binding conversion to yaml, only minor changes/small fixes
> have been merged.
>
> * Raw NAND changes:
>
> Various controller drivers received minor fixes like DMA mapping checks,
> better timing derivations or bitflip statistics.
> It has also been discovered that some Hynix NAND flashes were not
> supporting read-retries, which is not properly supported.
>
> * SPI NAND changes:
>
> In order to support high-speed modes, certain chips need extra
> configuration like adding more dummy cycles. This is now possible,
> especially on Winbond chips.
>
> Aside from that, Gigadevice gets support for a new chip (GD5F1GM9).
>
> * SPI NOR changes:
>
> A notable changes is the fix for exiting 4-byte addressing on Infineon
> SEMPER flashes. These flashes do not support the standard EX4B
> opcode (E9h), and use a vendor-specific opcode (B8h) instead.
>
> There is also a fix for unlocking flashes that are write-protected at
> power-on. This was caused by using an uninitialized mtd_info in
> spi_nor_try_unlock_all().

I personally think bullet points are a bit easier to read for changelogs
compared to paragraphs since there is less filler text needed. For
example, my original merge message didn't the "there is also a fix for".
It just said "Fix unlocking of...".

Anyway, if you still prefer paragraphs then do let me know and I'll use
those next time around and save you some editing.

[...]

-- 
Regards,
Pratyush Yadav

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

  parent reply	other threads:[~2025-08-01 14:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-31 16:59 [GIT PULL] mtd: Changes for 6.17 Miquel Raynal
2025-07-31 20:51 ` pr-tracker-bot
2025-08-01 14:47 ` Pratyush Yadav [this message]
2025-08-01 15:01   ` Miquel Raynal
2025-08-04 14:40     ` Pratyush Yadav
2025-08-04 15:53       ` Linus Torvalds
2025-08-05  7:47         ` 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=mafs0v7n7cd5a.fsf@kernel.org \
    --to=pratyush@kernel.org \
    --cc=Tudor.Ambarus@linaro.org \
    --cc=frieder.schrempf@kontron.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=michael@walle.cc \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard@nod.at \
    --cc=torvalds@linux-foundation.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.