From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: defconfig: Update Gemini defconfig
Date: Mon, 30 Apr 2018 09:13:52 +0200 [thread overview]
Message-ID: <CACRpkdZM1sTC47htB4dP_PgLuzd57C2n==6g=8H_UgzuMrWzfA@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a1X_hKLo3o1YmkxayncUGbTuTR+HKftmvbCtwQegO7zHw@mail.gmail.com>
On Thu, Apr 26, 2018 at 4:57 PM, Arnd Bergmann <arnd@arndb.de> wrote:
>> ARM SoC folks: please apply this for fixes.
>
> I've applied it to the fixes branch now, but I don't see why I didn't
> get the patch before the merge window when you already
> had a version for the v4.16 window.
It's because of my ways of working: I work on a target and then right after
the merge window at -rc1 I usually check what new drivers I managed
to get upstream and then for those that made it I send a patch enabling
them in in the defconfig in the target system.
After sending the defconfig patch for v4.16-rc1 I simply forgot about
it until the next -rc1...
Yours,
Linus Walleij
prev parent reply other threads:[~2018-04-30 7:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 9:00 [PATCH v2] ARM: defconfig: Update Gemini defconfig Linus Walleij
2018-04-26 14:57 ` Arnd Bergmann
2018-04-30 7:13 ` Linus Walleij [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='CACRpkdZM1sTC47htB4dP_PgLuzd57C2n==6g=8H_UgzuMrWzfA@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).