Linux GPIO subsystem development
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: linux-gpio@vger.kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
	Conor Dooley <conor.dooley@microchip.com>,
	Daire McNamara <daire.mcnamara@microchip.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH v1 0/2] polarfire gpio driver follow-ups
Date: Mon, 11 Nov 2024 09:24:59 +0000	[thread overview]
Message-ID: <20241111-antennae-gab-2866754984ad@spud> (raw)
In-Reply-To: <173126574727.7785.4094963648273280544.b4-ty@linaro.org>

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

On Sun, Nov 10, 2024 at 08:10:31PM +0100, Bartosz Golaszewski wrote:
 
> I must admit I like your b4 topic names. :)

Heh, no credit to me - they're not b4 topic names. The branch was
actually called "gpio-noirq-core". It's a sendemail-validate hook in
git that generates it using diceware that came out of a conversation
between Brauner/Greg/Konstantin. Beats the usual send-email message-ids
given it is more human readable.

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

      reply	other threads:[~2024-11-11  9:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07 10:33 [PATCH v1 0/2] polarfire gpio driver follow-ups Conor Dooley
2024-11-07 10:33 ` [PATCH v1 1/2] gpio: mpfs: add CoreGPIO support Conor Dooley
2024-11-10 19:08   ` Bartosz Golaszewski
2024-11-07 10:33 ` [PATCH v1 2/2] MAINTAINERS: add gpio driver to PolarFire entry Conor Dooley
2024-11-10 19:10 ` (subset) [PATCH v1 0/2] polarfire gpio driver follow-ups Bartosz Golaszewski
2024-11-11  9:24   ` Conor Dooley [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=20241111-antennae-gab-2866754984ad@spud \
    --to=conor@kernel.org \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=conor.dooley@microchip.com \
    --cc=daire.mcnamara@microchip.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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