From: Olof Johansson <olof@lixom.net>
To: Tony Lindgren <tony@atomide.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Arnd Bergmann <arnd@arndb.de>,
Russell King <linux@armlinux.org.uk>,
arm@kernel.org, Thierry Reding <thierry.reding@gmail.com>,
Simon Horman <horms+renesas@verge.net.au>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] defconfig refresh for multi_v7_defconfig for v5.1
Date: Sun, 28 Apr 2019 23:17:14 -0700 [thread overview]
Message-ID: <20190429061714.3qcj72efkblqhjw3@localhost> (raw)
In-Reply-To: <pull-1555425463-418342@atomide.com>
On Tue, Apr 16, 2019 at 09:13:37AM -0700, Tony Lindgren wrote:
> From: "Tony Lindgren" <tony@atomide.com>
>
> The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
>
> Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/multi-v7-defconfig-for-v5.2-signed
>
> for you to fetch changes up to 35f8e2e29e74bb7197419d7cd80df5584e2a6311:
>
> ARM: multi_v7_defconfig: Update for moved options (2019-04-16 07:05:07 -0700)
>
> ----------------------------------------------------------------
> Update multi_v7_defconfig for dropped and moved options
>
> This series of two patches first updates multi_v7_defconfig for
> dropped options, and then updates it for moved options. We want to
> do this on regular basis to make it easier to patch multi_v7_defconfig
> without introducing errors and merge conflicts. We update the defconfig
> in two patches to make sure we're not accidentally losing any needed
> options.
>
> After this, updating multi_v7_defconfig will become trivial, and most
> likely only a small follow-up patches are needed after the merge window
> to update it again for moved options.
Merged, thanks.
-Olof
_______________________________________________
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:[~2019-04-29 7:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 16:13 [GIT PULL] defconfig refresh for multi_v7_defconfig for v5.1 Tony Lindgren
2019-04-29 6:17 ` Olof Johansson [this message]
2019-04-29 7:59 ` Simon Horman
2019-04-29 8:44 ` Simon Horman
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=20190429061714.3qcj72efkblqhjw3@localhost \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=geert+renesas@glider.be \
--cc=horms+renesas@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=thierry.reding@gmail.com \
--cc=tony@atomide.com \
/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