From: patchwork-bot+linux-riscv@kernel.org
To: Xichao Zhao <zhao.xichao@vivo.com>
Cc: linux-riscv@lists.infradead.org, Raju.Rangoju@amd.com,
broonie@kernel.org, sunny.luo@amlogic.com,
xianwei.zhao@amlogic.com, conor.dooley@microchip.com,
daire.mcnamara@microchip.com, matthias.bgg@gmail.com,
angelogioacchino.delregno@collabora.com, daniel@zonque.org,
haojian.zhuang@gmail.com, robert.jarzmik@free.fr,
andi.shyti@kernel.org, tudor.ambarus@linaro.org, krzk@kernel.org,
alim.akhtar@samsung.com, linux-spi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH v1 0/6] spi: Remove the use of dev_err_probe()
Date: Thu, 09 Oct 2025 01:07:10 +0000 [thread overview]
Message-ID: <175997203075.3661959.13983624116098440178.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250819092044.549464-1-zhao.xichao@vivo.com>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Mark Brown <broonie@kernel.org>:
On Tue, 19 Aug 2025 17:20:37 +0800 you wrote:
> The dev_err_probe() doesn't do anything when error is '-ENOMEM'. Therefore,
> remove the useless call to dev_err_probe(), and just return the value instead.
>
> Xichao Zhao (6):
> spi: spi_amd: Remove the use of dev_err_probe()
> spi: SPISG: Remove the use of dev_err_probe()
> spi: Remove the use of dev_err_probe()
> spi: mt65xx: Remove the use of dev_err_probe()
> spi: pxa2xx: Remove the use of dev_err_probe()
> spi: s3c64xx: Remove the use of dev_err_probe()
>
> [...]
Here is the summary with links:
- [v1,3/6] spi: Remove the use of dev_err_probe()
https://git.kernel.org/riscv/c/2aade32d1ffc
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-10-09 1:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 9:20 [PATCH v1 0/6] spi: Remove the use of dev_err_probe() Xichao Zhao
2025-08-19 9:20 ` [PATCH v1 4/6] spi: mt65xx: " Xichao Zhao
2025-08-19 9:20 ` [PATCH v1 5/6] spi: pxa2xx: " Xichao Zhao
2025-08-19 9:20 ` [PATCH v1 6/6] spi: s3c64xx: " Xichao Zhao
2025-08-19 10:00 ` Tudor Ambarus
2025-08-19 18:52 ` [PATCH v1 0/6] spi: " Mark Brown
2025-10-09 1:07 ` patchwork-bot+linux-riscv [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=175997203075.3661959.13983624116098440178.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=Raju.Rangoju@amd.com \
--cc=alim.akhtar@samsung.com \
--cc=andi.shyti@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=daniel@zonque.org \
--cc=haojian.zhuang@gmail.com \
--cc=krzk@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=robert.jarzmik@free.fr \
--cc=sunny.luo@amlogic.com \
--cc=tudor.ambarus@linaro.org \
--cc=xianwei.zhao@amlogic.com \
--cc=zhao.xichao@vivo.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).