mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Varadarajan Narayanan <quic_varada@quicinc.com>,
	 Md Sadre Alam <quic_mdalam@quicinc.com>,
	 Sricharan Ramabadhran <quic_srichara@quicinc.com>,
	 Gabor Juhos <j4g8y7@gmail.com>
Cc: linux-spi@vger.kernel.org, linux-mtd@lists.infradead.org,
	 linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH next] spi: spi-qpic-snand: validate user/chip specific ECC properties
Date: Thu, 15 May 2025 09:35:39 +0200	[thread overview]
Message-ID: <174729453999.272648.10698524382095396308.b4-ty@kernel.org> (raw)
In-Reply-To: <20250501-qpic-snand-validate-ecc-v1-1-532776581a66@gmail.com>

On Thu, 01 May 2025 18:19:16 +0200, Gabor Juhos wrote:
> The driver only supports 512 bytes ECC step size and 4 bit ECC strength
> at the moment, however it does not reject unsupported step/strength
> configurations. Due to this, whenever the driver is used with a flash
> chip which needs stronger ECC protection, the following warning is shown
> in the kernel log:
> 
>   [    0.574648] spi-nand spi0.0: GigaDevice SPI NAND was found.
>   [    0.635748] spi-nand spi0.0: 256 MiB, block size: 128 KiB, page size: 2048, OOB size: 128
>   [    0.649079] nand: WARNING: (null): the ECC used on your system is too weak compared to the one required by the NAND chip
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/1] spi: spi-qpic-snand: validate user/chip specific ECC properties
      commit: 65cb56d49f6edea409600a3c61effc70ee5d43d8

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark


      reply	other threads:[~2025-05-15  7:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-01 16:19 Gabor Juhos
2025-05-15  7:35 ` Mark Brown [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=174729453999.272648.10698524382095396308.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=j4g8y7@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=quic_mdalam@quicinc.com \
    --cc=quic_srichara@quicinc.com \
    --cc=quic_varada@quicinc.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

all inboxes | Powered by JetHome®