From: Linus Torvalds <torvalds@linux-foundation.org>
To: Marc Gonzalez <marc.w.gonzalez@free.fr>
Cc: Linus Walleij <linus.walleij@linaro.org>,
arm-soc <arm@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL 1/4] ARM: SoC platform updates
Date: Thu, 16 May 2019 09:34:28 -0700 [thread overview]
Message-ID: <CAHk-=wgZFNMJCgs5a2hG=6gZxs0+xc_A7jXsS+EJfAi8h9W6Rw@mail.gmail.com> (raw)
In-Reply-To: <aad06de6-b85c-b549-5653-45f9c4ebb384@free.fr>
On Thu, May 16, 2019 at 9:00 AM Marc Gonzalez <marc.w.gonzalez@free.fr> wrote:
>
> Your email client did something strange by changing
>
> linux-arm-kernel@lists.infradead.org
> to
> "linux-alpha@vger.kernel.org" <linux-arm-kernel@lists.infradead.org>
>
> which is odd ;-)
Heh. Indeed.
What seems to have happened is that somebody long ago sent an email
with a missing comma (so "linux-alpha@vger.kernel.org
<linux-arm-kernel@lists.infradead.org>" - *intending* to send to both,
but ending up with the linux-alpha list being the "name" for the
linux-arm one).
And then I replied to that email, and it got picked up as my automatic
contact. So when I replied to linux-arm-kernel@lists.infradead.org,
and it had no name, my automatic contacts helpfully filled in that
bogus name for that list ;)
I will fix.
I note that because *you* had added the right name for the list, this
reply didn't even try to use that bogus contact name.
Linus
next prev parent reply other threads:[~2019-05-16 16:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 6:43 [GIT PULL 0/4] ARM: SoC contents for 5.2 merge window Olof Johansson
2019-05-16 6:43 ` [GIT PULL 1/4] ARM: SoC platform updates Olof Johansson
2019-05-16 15:33 ` Linus Torvalds
2019-05-16 15:53 ` Arnd Bergmann
2019-05-16 17:10 ` Olof Johansson
2019-05-20 21:56 ` Linus Walleij
2019-05-16 15:59 ` Marc Gonzalez
2019-05-16 16:34 ` Linus Torvalds [this message]
2019-05-16 16:40 ` pr-tracker-bot
2019-05-16 6:43 ` [GIT PULL 2/4] ARM: Device-tree updates Olof Johansson
2019-05-16 16:40 ` pr-tracker-bot
2019-05-16 6:43 ` [GIT PULL 3/4] ARM: SoC-related driver updates Olof Johansson
2019-05-16 16:26 ` Linus Torvalds
2019-05-16 16:35 ` Patrick Venture
2019-05-16 17:39 ` Olof Johansson
2019-05-16 16:40 ` pr-tracker-bot
2019-05-16 6:43 ` [GIT PULL 4/4] ARM: SoC defconfig updates Olof Johansson
2019-05-16 16:40 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2019-12-05 18:04 [GIT PULL 1/4] ARM: SoC platform updates Olof Johansson
2019-12-05 20:45 ` pr-tracker-bot
2019-07-19 23:54 [GIT PULL 0/4] ARM: SoC contents for 5.3 merge window Olof Johansson
2019-07-19 23:54 ` [GIT PULL 1/4] ARM: SoC platform updates Olof Johansson
2019-07-20 0:30 ` pr-tracker-bot
2018-12-31 21:46 [GIT PULL 0/4] ARM: SoC changes for v4.21 Olof Johansson
2018-12-31 21:46 ` [GIT PULL 1/4] ARM: SoC platform updates Olof Johansson
2019-01-01 1:45 ` pr-tracker-bot
2018-06-12 0:01 [GIT PULL 0/4] ARM: SoC updates Olof Johansson
2018-06-12 0:01 ` [GIT PULL 1/4] ARM: SoC platform updates Olof Johansson
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='CAHk-=wgZFNMJCgs5a2hG=6gZxs0+xc_A7jXsS+EJfAi8h9W6Rw@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=arm@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.w.gonzalez@free.fr \
/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;
as well as URLs for NNTP newsgroup(s).