From: Linus Torvalds <torvalds@linux-foundation.org>
To: Joel Stanley <joel@jms.id.au>
Cc: Arnd Bergmann <arnd@arndb.de>, SoC Team <soc@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [GIT PULL 3/5] ARM: SoC changes for v5.9
Date: Tue, 4 Aug 2020 11:38:09 -0700 [thread overview]
Message-ID: <CAHk-=wiUg-S20ywzUv7nB+5AQc1tDh9DZ3wL4oLNpT3sW=iFvw@mail.gmail.com> (raw)
In-Reply-To: <CACPK8Xd++ZQx9hh21dV6qn73aoWvoFsOHq8Pmgbtpi-GD3ShmA@mail.gmail.com>
On Tue, Aug 4, 2020 at 12:02 AM Joel Stanley <joel@jms.id.au> wrote:
>
> for_each_requested_gpio isn't in Linus (Torvalds) tree yet. It will be
> fixed when he pulls Linus Walleij's GPIO tree which has the commit:
There are too many Linuses in kernel development.
For the next in-person kernel summit, I suggest a Highlander-style
"There can be only one" deathmatch.
I will start training immediately.
Linus
WARNING: multiple messages have this Message-ID (diff)
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Joel Stanley <joel@jms.id.au>
Cc: Arnd Bergmann <arnd@arndb.de>,
Linus Walleij <linus.walleij@linaro.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
SoC Team <soc@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL 3/5] ARM: SoC changes for v5.9
Date: Tue, 4 Aug 2020 11:38:09 -0700 [thread overview]
Message-ID: <CAHk-=wiUg-S20ywzUv7nB+5AQc1tDh9DZ3wL4oLNpT3sW=iFvw@mail.gmail.com> (raw)
In-Reply-To: <CACPK8Xd++ZQx9hh21dV6qn73aoWvoFsOHq8Pmgbtpi-GD3ShmA@mail.gmail.com>
On Tue, Aug 4, 2020 at 12:02 AM Joel Stanley <joel@jms.id.au> wrote:
>
> for_each_requested_gpio isn't in Linus (Torvalds) tree yet. It will be
> fixed when he pulls Linus Walleij's GPIO tree which has the commit:
There are too many Linuses in kernel development.
For the next in-person kernel summit, I suggest a Highlander-style
"There can be only one" deathmatch.
I will start training immediately.
Linus
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-08-04 18:38 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 21:34 [GIT PULL 0/5] ARM: SoC: changes for v5.9 Arnd Bergmann
2020-08-03 21:34 ` Arnd Bergmann
2020-08-03 21:36 ` [GIT PULL 1/5] ARM: defconfig updates " Arnd Bergmann
2020-08-03 21:36 ` Arnd Bergmann
2020-08-04 2:45 ` pr-tracker-bot
2020-08-03 21:44 ` [GIT PULL 2/5] ARM: SoC: DT changes " Arnd Bergmann
2020-08-03 21:44 ` Arnd Bergmann
2020-08-04 2:45 ` pr-tracker-bot
2020-08-03 21:47 ` [GIT PULL 3/5] ARM: SoC " Arnd Bergmann
2020-08-03 21:47 ` Arnd Bergmann
2020-08-04 2:45 ` pr-tracker-bot
2020-08-04 7:02 ` Joel Stanley
2020-08-04 7:02 ` Joel Stanley
2020-08-04 7:33 ` Andy Shevchenko
2020-08-04 7:33 ` Andy Shevchenko
2020-08-04 7:39 ` Andy Shevchenko
2020-08-04 7:39 ` Andy Shevchenko
2020-08-04 7:55 ` Linus Walleij
2020-08-04 7:55 ` Linus Walleij
2020-08-04 18:38 ` Linus Torvalds [this message]
2020-08-04 18:38 ` Linus Torvalds
2020-08-03 21:49 ` [GIT PULL 4/5] ARM: SoC driver updates " Arnd Bergmann
2020-08-03 21:49 ` Arnd Bergmann
2020-08-04 2:45 ` pr-tracker-bot
2020-08-03 21:50 ` [GIT PULL 5/5] ARM: new SoC support " Arnd Bergmann
2020-08-03 21:50 ` Arnd Bergmann
2020-08-04 2:45 ` pr-tracker-bot
2020-08-05 17:27 ` [GIT PULL 0/5] ARM: SoC: changes " Pavel Machek
2020-08-05 17:27 ` Pavel Machek
2020-08-05 19:06 ` Arnd Bergmann
2020-08-05 19:06 ` Arnd Bergmann
2020-08-05 19:28 ` Konrad Dybcio
2020-08-05 19:28 ` Konrad Dybcio
2020-08-05 19:45 ` Pavel Machek
2020-08-05 19:45 ` Pavel Machek
2020-08-05 19:58 ` Konrad Dybcio
2020-08-05 19:58 ` Konrad Dybcio
2020-08-05 22:12 ` Konrad Dybcio
2020-08-05 22:12 ` Konrad Dybcio
2020-08-05 19:32 ` Pavel Machek
2020-08-05 19:32 ` Pavel Machek
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-=wiUg-S20ywzUv7nB+5AQc1tDh9DZ3wL4oLNpT3sW=iFvw@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@arndb.de \
--cc=joel@jms.id.au \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=soc@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 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.