From: Tony Lindgren <tony@atomide.com>
To: Simon Horman <horms@verge.net.au>
Cc: Arnd Bergmann <arnd@arndb.de>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Russell King <linux@armlinux.org.uk>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Olof Johansson <olof@lixom.net>,
"open list:TI ETHERNET SWITCH DRIVER \(CPSW\)"
<linux-omap@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/2] ARM: multi_v7_defconfig: Update for dropped options
Date: Tue, 5 Feb 2019 08:11:53 -0800 [thread overview]
Message-ID: <20190205161153.GR5720@atomide.com> (raw)
In-Reply-To: <20190205105801.3eysznz63x3na4ui@verge.net.au>
* Simon Horman <horms@verge.net.au> [190205 10:58]:
> On Tue, Feb 05, 2019 at 09:07:38AM +0100, Geert Uytterhoeven wrote:
> > Hi Tony,
> >
> > On Mon, Feb 4, 2019 at 9:37 PM Tony Lindgren <tony@atomide.com> wrote:
> > > These are automatically selected with make multi_v7_defconfig,
> > > except for SH_DMAE which is selected only by sound/soc/sh/Kconfig.
> > >
> > > Cc: Arnd Bergmann <arnd@arndb.de>
> > > Cc: Geert Uytterhoeven <geert+renesas@glider.be>
> > > Cc: Olof Johansson <olof@lixom.net>
> > > Cc: Russell King <linux@armlinux.org.uk>
> > > Cc: Simon Horman <horms+renesas@verge.net.au>
> > > Signed-off-by: Tony Lindgren <tony@atomide.com>
> >
> > Thanks, this matches similar changes to shmobile_defconfig in commit
> > 4162325afd0d553c ("ARM: shmobile: defconfig: Refresh for v5.0-rc1")
> > in next.
> >
> > Acked-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
> Acked-by: Simon Horman <horms+renesas@verge.net.au>
>
> >
> > I didn't update multi_v7_defconfig to avoid conflicts.
> > IMHO the arm-soc maintainers should handle the refresh of the common
> > config on a regular basis[*].
> >
> > [*] When is the right time? I'd say it should be the last commit just
> > before the release of rc1 (so all arm-soc submaintainers' trees will
> > have the new base in their for-next branches for the next merge
> > window), but that may be difficult to implement.
> >
> > What do you think? Thanks!
Yeah I agree we should do it on regular basis just before -rc1
for multi_v7_defconfig.
The reasoning being that make savedefconfig is pretty much useless
otherwise for generating defconfig patches and the chances of
pointless merge conflicts and errors keep increasing until
something breaks :)
I can attempt to do a late branch of the dropped and moved options
refreshed against arm-soc defconfig branch if that helps.
Regards,
Tony
_______________________________________________
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-02-05 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 20:37 [PATCH 1/2] ARM: multi_v7_defconfig: Update for dropped options Tony Lindgren
2019-02-04 20:37 ` [PATCH 2/2] ARM: multi_v7_defconfig: Update for moved options Tony Lindgren
2019-02-05 8:09 ` Geert Uytterhoeven
2019-02-05 10:58 ` Simon Horman
2019-02-05 8:07 ` [PATCH 1/2] ARM: multi_v7_defconfig: Update for dropped options Geert Uytterhoeven
2019-02-05 10:58 ` Simon Horman
2019-02-05 16:11 ` Tony Lindgren [this message]
2019-02-05 19:47 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2019-02-20 19:02 [PATCHv2 0/2] Update multi_v7_defconfig for dropped and moved options Tony Lindgren
2019-02-20 19:02 ` [PATCH 1/2] ARM: multi_v7_defconfig: Update for dropped options Tony Lindgren
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=20190205161153.GR5720@atomide.com \
--to=tony@atomide.com \
--cc=arnd@arndb.de \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=olof@lixom.net \
/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).