From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Mark Brown <broonie@kernel.org>
Cc: Nicolas Ferre <nicolas.ferre@microchip.com>,
Jinjie Ruan <ruanjinjie@huawei.com>,
linux-spi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Radu Pirea <radu_nicolae.pirea@upb.ro>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Russell King - ARM Linux <linux@arm.linux.org.uk>
Subject: Re: [PATCH -next] spi: at91-usart: Use PTR_ERR_OR_ZERO() to simplify code
Date: Tue, 22 Aug 2023 16:45:55 +0200 [thread overview]
Message-ID: <20230822144555d15b0dcd@mail.local> (raw)
In-Reply-To: <b11438ee-e05e-473b-a95b-433444fc77e0@sirena.org.uk>
On 22/08/2023 15:15:13+0100, Mark Brown wrote:
> On Tue, Aug 22, 2023 at 03:11:01PM +0200, Nicolas Ferre wrote:
>
> > Do we really need these changes?... oh well, no strong opinion but is it
> > worth the effort?
>
> I tend to go on the basis that for this sort of thing that's recognised
> by pattern matching other people will end up sending versions of it no
> matter what.
And I'd love for people to explicitly write this has been automatically
generated in their commit log so we know that probably no though has
been given to the patch.
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
WARNING: multiple messages have this Message-ID (diff)
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Mark Brown <broonie@kernel.org>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Radu Pirea <radu_nicolae.pirea@upb.ro>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
linux-spi@vger.kernel.org, Jinjie Ruan <ruanjinjie@huawei.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH -next] spi: at91-usart: Use PTR_ERR_OR_ZERO() to simplify code
Date: Tue, 22 Aug 2023 16:45:55 +0200 [thread overview]
Message-ID: <20230822144555d15b0dcd@mail.local> (raw)
In-Reply-To: <b11438ee-e05e-473b-a95b-433444fc77e0@sirena.org.uk>
On 22/08/2023 15:15:13+0100, Mark Brown wrote:
> On Tue, Aug 22, 2023 at 03:11:01PM +0200, Nicolas Ferre wrote:
>
> > Do we really need these changes?... oh well, no strong opinion but is it
> > worth the effort?
>
> I tend to go on the basis that for this sort of thing that's recognised
> by pattern matching other people will end up sending versions of it no
> matter what.
And I'd love for people to explicitly write this has been automatically
generated in their commit log so we know that probably no though has
been given to the patch.
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-22 14:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 12:46 [PATCH -next] spi: at91-usart: Use PTR_ERR_OR_ZERO() to simplify code Jinjie Ruan
2023-08-22 12:46 ` Jinjie Ruan
2023-08-22 13:11 ` Nicolas Ferre
2023-08-22 13:11 ` Nicolas Ferre
2023-08-22 14:15 ` Mark Brown
2023-08-22 14:15 ` Mark Brown
2023-08-22 14:45 ` Alexandre Belloni [this message]
2023-08-22 14:45 ` Alexandre Belloni
2023-08-22 15:04 ` Mark Brown
2023-08-22 15:04 ` Mark Brown
2023-08-22 16:33 ` Mark Brown
2023-08-22 16:33 ` Mark Brown
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=20230822144555d15b0dcd@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=broonie@kernel.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nicolas.ferre@microchip.com \
--cc=radu_nicolae.pirea@upb.ro \
--cc=ruanjinjie@huawei.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.