From: Lorenzo Bianconi <lorenzo@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Ray Liu <ray.liu@airoha.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Andy Shevchenko <andy@kernel.org>,
Christian Marangi <ansuelsmth@gmail.com>,
linux-arm-kernel@lists.infradead.org, linux-spi@vger.kernel.org,
upstream@airoha.com
Subject: Re: (subset) [PATCH 0/4] spi: airoha: Fix errors reported by mtd_test kernel modules
Date: Thu, 19 Sep 2024 10:59:20 +0200 [thread overview]
Message-ID: <Zuvn6H9wmb7PQLac@lore-desk> (raw)
In-Reply-To: <172673459965.1807523.13398242599346549903.b4-ty@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1505 bytes --]
> On Fri, 13 Sep 2024 23:07:12 +0200, Lorenzo Bianconi wrote:
> > Fix errors detected running mtd_test kernel test modules.
> >
>
> Applied to
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
>
> Thanks!
>
> [1/4] spi: airoha: fix dirmap_{read,write} operations
> commit: 2e6bbfe7b0c0607001b784082c2685b134174fac
> [2/4] spi: airoha: fix airoha_snand_{write,read}_data data_len estimation
> commit: 0e58637eb968c636725dcd6c7055249b4e5326fb
>
> 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
>
Hi Mark,
I think we should include even patch 3/4 since it fixes some errors in
mtd_oobtest kernel test module (and even some ubifs reported errors).
Regards,
Lorenzo
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-09-19 9:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 21:07 [PATCH 0/4] spi: airoha: Fix errors reported by mtd_test kernel modules Lorenzo Bianconi
2024-09-13 21:07 ` [PATCH 1/4] spi: airoha: fix dirmap_{read,write} operations Lorenzo Bianconi
2024-09-13 21:07 ` [PATCH 2/4] spi: airoha: fix airoha_snand_{write,read}_data data_len estimation Lorenzo Bianconi
2024-09-13 21:07 ` [PATCH 3/4] spi: airoha: remove read cache in airoha_snand_dirmap_read Lorenzo Bianconi
2024-09-13 21:07 ` [PATCH 4/4] spi: airoha: do not keep {tx,rx} dma buffer always mapped Lorenzo Bianconi
2024-09-19 8:29 ` (subset) [PATCH 0/4] spi: airoha: Fix errors reported by mtd_test kernel modules Mark Brown
2024-09-19 8:59 ` Lorenzo Bianconi [this message]
2024-09-19 9:05 ` Mark Brown
2024-09-19 9:16 ` Lorenzo Bianconi
2024-09-19 10:44 ` Mark Brown
2024-09-19 11:18 ` Lorenzo Bianconi
2024-09-19 12:29 ` Mark Brown
2024-09-19 12:36 ` Lorenzo Bianconi
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=Zuvn6H9wmb7PQLac@lore-desk \
--to=lorenzo@kernel.org \
--cc=andy@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=ansuelsmth@gmail.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=ray.liu@airoha.com \
--cc=upstream@airoha.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).