All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
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:04:49 +0100	[thread overview]
Message-ID: <78d84425-a8ac-42a4-946f-9906a7a4e875@sirena.org.uk> (raw)
In-Reply-To: <20230822144555d15b0dcd@mail.local>

[-- Attachment #1: Type: text/plain, Size: 628 bytes --]

On Tue, Aug 22, 2023 at 04:45:55PM +0200, Alexandre Belloni wrote:
> On 22/08/2023 15:15:13+0100, Mark Brown wrote:

> > 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.

Well, a bunch of them are going to be manually written by someone based
on fixing warnings that some checker is generating rather than actually
automatically generated.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
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:04:49 +0100	[thread overview]
Message-ID: <78d84425-a8ac-42a4-946f-9906a7a4e875@sirena.org.uk> (raw)
In-Reply-To: <20230822144555d15b0dcd@mail.local>


[-- Attachment #1.1: Type: text/plain, Size: 628 bytes --]

On Tue, Aug 22, 2023 at 04:45:55PM +0200, Alexandre Belloni wrote:
> On 22/08/2023 15:15:13+0100, Mark Brown wrote:

> > 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.

Well, a bunch of them are going to be manually written by someone based
on fixing warnings that some checker is generating rather than actually
automatically generated.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-08-22 15:04 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
2023-08-22 14:45       ` Alexandre Belloni
2023-08-22 15:04       ` Mark Brown [this message]
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=78d84425-a8ac-42a4-946f-9906a7a4e875@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --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.