All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Justin Swartz <justin.swartz@risingedge.co.za>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] spi: mt7621: allow GPIO chip select lines
Date: Sat, 16 Mar 2024 01:11:09 +0000	[thread overview]
Message-ID: <81c2c997-52f8-48a6-ace5-1bf503462f25@sirena.org.uk> (raw)
In-Reply-To: <182aa3a1fcd05a2e25b55442f58ced5b@risingedge.co.za>

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

On Sat, Mar 16, 2024 at 03:01:02AM +0200, Justin Swartz wrote:

> Please ignore this patch. It was accidentally sent without
> "v2" nor --in-reply-to=...

The --in-reply-to should be avoided:

Please don't send new patches in reply to old patches or serieses, this
makes it harder for both people and tools to understand what is going
on - it can bury things in mailboxes and make it difficult to keep track
of what current patches are, both for the new patches and the old ones.

[-- 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: Justin Swartz <justin.swartz@risingedge.co.za>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] spi: mt7621: allow GPIO chip select lines
Date: Sat, 16 Mar 2024 01:11:09 +0000	[thread overview]
Message-ID: <81c2c997-52f8-48a6-ace5-1bf503462f25@sirena.org.uk> (raw)
In-Reply-To: <182aa3a1fcd05a2e25b55442f58ced5b@risingedge.co.za>


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

On Sat, Mar 16, 2024 at 03:01:02AM +0200, Justin Swartz wrote:

> Please ignore this patch. It was accidentally sent without
> "v2" nor --in-reply-to=...

The --in-reply-to should be avoided:

Please don't send new patches in reply to old patches or serieses, this
makes it harder for both people and tools to understand what is going
on - it can bury things in mailboxes and make it difficult to keep track
of what current patches are, both for the new patches and the old ones.

[-- 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:[~2024-03-16  1:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-16  0:59 [PATCH] spi: mt7621: allow GPIO chip select lines Justin Swartz
2024-03-16  0:59 ` Justin Swartz
2024-03-16  1:01 ` Justin Swartz
2024-03-16  1:01   ` Justin Swartz
2024-03-16  1:11   ` Mark Brown [this message]
2024-03-16  1:11     ` Mark Brown
2024-03-16  1:15     ` Justin Swartz
2024-03-16  1:15       ` Justin Swartz
  -- strict thread matches above, loose matches on Subject: below --
2024-03-15  1:57 Justin Swartz
2024-03-15  1:57 ` Justin Swartz
2024-03-15 14:45 ` Mark Brown
2024-03-15 14:45   ` Mark Brown
2024-03-15 16:23   ` Justin Swartz
2024-03-15 16:23     ` Justin Swartz
2024-03-15 17:47     ` Mark Brown
2024-03-15 17:47       ` Mark Brown
2024-03-15 20:21       ` Justin Swartz
2024-03-15 20:21         ` Justin Swartz
2024-03-15 20:41         ` Mark Brown
2024-03-15 20:41           ` 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=81c2c997-52f8-48a6-ace5-1bf503462f25@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=justin.swartz@risingedge.co.za \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=matthias.bgg@gmail.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.