From: "Diederik de Haas" <didi.debian@cknow.org>
To: "Mark Brown" <broonie@kernel.org>, <linux-spi@vger.kernel.org>,
<linux-rockchip@lists.infradead.org>,
"Dragan Simic" <dsimic@manjaro.org>
Cc: <heiko@sntech.de>, <oss@helene.moe>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: (subset) [PATCH 0/5] Improve error handling in Rockchip SPI drivers
Date: Tue, 01 Oct 2024 02:05:48 +0200 [thread overview]
Message-ID: <D4K14E2EOSC6.1VYBGSQKSIRW1@cknow.org> (raw)
In-Reply-To: <172774028424.2264837.4595727034314147956.b4-ty@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1458 bytes --]
On Tue Oct 1, 2024 at 1:51 AM CEST, Mark Brown wrote:
> On Thu, 26 Sep 2024 10:38:11 +0200, Dragan Simic wrote:
> > This is a small series that improves error handling in the probe path
> > of the Rockchip SPI drivers, by using dev_err_probe() properly in multiple
> > places. It also removes one unnecessary check of a function return value,
> > and performs a bunch of small, rather trivial code cleanups, to make the
> > code neater and a bit easier to read.
> >
> > Dragan Simic (5):
> > spi: rockchip: Perform trivial code cleanups
> > spi: rockchip-sfc: Perform trivial code cleanups
> > spi: rockchip: Don't check for failed get_fifo_len()
> > spi: rockchip: Use dev_err_probe() in the probe path
> > spi: rockchip-sfc: Use dev_err_probe() in the probe path
> >
> > [...]
>
> Applied to
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
>
> Thanks!
>
> [1/5] spi: rockchip: Perform trivial code cleanups
> commit: d87ec94e48dd2da27fbe948f2dc6c8fedc98fff4
> [2/5] spi: rockchip-sfc: Perform trivial code cleanups
> commit: 6c510eac1528d8939bad8b6df72c7b23ffec8c25
> [5/5] spi: rockchip-sfc: Use dev_err_probe() in the probe path
> commit: 1482c40b440fa58f956bc3e1ef3426e0cdbc09e0
It looks like you applied some patches from v1 of this series while the
current version is v3.
https://lore.kernel.org/linux-rockchip/cover.1727601608.git.dsimic@manjaro.org/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-10-01 0:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 8:38 [PATCH 0/5] Improve error handling in Rockchip SPI drivers Dragan Simic
2024-09-26 8:38 ` [PATCH 1/5] spi: rockchip: Perform trivial code cleanups Dragan Simic
2024-09-26 8:52 ` Heiko Stuebner
2024-09-26 8:38 ` [PATCH 2/5] spi: rockchip-sfc: " Dragan Simic
2024-09-26 8:53 ` Heiko Stuebner
2024-09-26 8:38 ` [PATCH 3/5] spi: rockchip: Don't check for failed get_fifo_len() Dragan Simic
2024-09-26 8:55 ` Heiko Stuebner
2024-09-26 9:10 ` Dragan Simic
2024-09-26 9:17 ` Mark Brown
2024-09-26 10:14 ` Dragan Simic
2024-09-26 8:38 ` [PATCH 4/5] spi: rockchip: Use dev_err_probe() in the probe path Dragan Simic
2024-09-26 9:00 ` Heiko Stuebner
2024-09-26 9:21 ` Dragan Simic
2024-09-26 8:38 ` [PATCH 5/5] spi: rockchip-sfc: " Dragan Simic
2024-09-26 9:01 ` Heiko Stuebner
2024-09-30 23:51 ` (subset) [PATCH 0/5] Improve error handling in Rockchip SPI drivers Mark Brown
2024-10-01 0:05 ` Diederik de Haas [this message]
2024-10-01 2:30 ` Dragan Simic
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=D4K14E2EOSC6.1VYBGSQKSIRW1@cknow.org \
--to=didi.debian@cknow.org \
--cc=broonie@kernel.org \
--cc=dsimic@manjaro.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=oss@helene.moe \
/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