From: Conor Dooley <conor@kernel.org>
To: Lee Jones <lee@kernel.org>, jstrauss@mailbox.org
Cc: jstrauss <jstrauss@mailbox.org>,
christophe.jaillet@wanadoo.fr, jansimon.moeller@gmx.de,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
pavel@ucw.cz
Subject: Re: [PATCH RESEND] Add multicolor support to BlinkM LED driver
Date: Tue, 3 Jan 2023 17:58:13 +0000 [thread overview]
Message-ID: <Y7RstV9EEgGbR0oJ@spud> (raw)
In-Reply-To: <Y7Qe3Rx+9jzdK1g8@google.com>
[-- Attachment #1: Type: text/plain, Size: 602 bytes --]
On Tue, Jan 03, 2023 at 12:26:05PM +0000, Lee Jones wrote:
> On Tue, 27 Dec 2022, jstrauss wrote:
>
> > Hi Conor,
> >
> > Thanks for the insight, I suspected it was some silent Proton issue. I
> > have switched to Mailbox.org, so all of my future emails and patches
> > will originate from this address.
>
> Thanks.
>
> Although when replying to this message, I get:
>
> Reply to Y6slQLto568WfmfZ@spud? ([yes]/no/?):
Judging by the "spud", that's my message-id from the previous mail.
Joe, might wanna figure out why your mailer is adding a reply-to header
with that in it!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-01-03 17:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 22:31 [PATCH RESEND] Add multicolor support to BlinkM LED driver jstrauss
2023-01-03 12:26 ` Lee Jones
2023-01-03 17:08 ` jstrauss
2023-01-03 17:58 ` Conor Dooley [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-13 15:44 Joseph Strauss
2023-07-28 8:04 ` Lee Jones
2022-12-14 22:25 Joseph Strauss
2022-12-15 19:31 ` Christophe JAILLET
2022-12-27 1:18 ` Joseph Strauss
2022-12-23 12:15 ` Lee Jones
2022-12-27 16:47 ` Joseph Strauss
2022-12-27 17:02 ` Conor Dooley
2022-11-01 21:25 Joseph Strauss
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=Y7RstV9EEgGbR0oJ@spud \
--to=conor@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=jansimon.moeller@gmx.de \
--cc=jstrauss@mailbox.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
/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