All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>
Cc: Simon Horman <horms+renesas@verge.net.au>,
	Thierry Reding <thierry.reding@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Russell King <linux@armlinux.org.uk>
Subject: Re: [PATCHv2 0/2] Update multi_v7_defconfig for dropped and moved options
Date: Tue, 16 Apr 2019 07:35:16 -0700	[thread overview]
Message-ID: <20190416143516.GE2839@atomide.com> (raw)
In-Reply-To: <20190220190215.29412-1-tony@atomide.com>

Hi,

* Tony Lindgren <tony@atomide.com> [190220 11:02]:
> Hi Arnd & Olof,
> 
> Here is an update of these two patches as we seem to have all the pending
> multi_v7_defconfig changes pulled in now.
> 
> Arnd & Olof, care to apply these two patches directly when suitable?

A change of plan :) I've pushed out multi-v7-defconfig-for-v5.2-signed
tag against v5.1-rc1 with just these two patches in it.

I'll send out a pull request for it shortly, and then folks can merge
it in as needed. Currently the only known merge conflict is a trivial
merge conflict with Thierry's patch for CONFIG_TRUSTED_FOUNDATIONS=y,
and Trierry can then merge it as we've discussed.

> If you prefer me to set up a branch for these let me know. However that
> might cause some issues with the timing, so patches are probably easier
> from that point of view :) And because of this, I have not added any branch
> into Linux next to avoid pointless merge conflicts.

So far it looks like only a minimal follow-up patch is needed
after the merge window to move few options.

> Also let me know if these patches need updating. I've kept the acks for the
> Renesas related changes from v1, other than that we've had few more options
> dropped and moved around as described in the patches.

And I'll be doing a small follow-up patch at the end of the merge
window.

Regards,

Tony

> Tony Lindgren (2):
>   ARM: multi_v7_defconfig: Update for dropped options
>   ARM: multi_v7_defconfig: Update for moved options
> 
>  arch/arm/configs/multi_v7_defconfig | 130 +++++++++++++---------------
>  1 file changed, 62 insertions(+), 68 deletions(-)
> 
> -- 
> 2.20.1
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> 

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      parent reply	other threads:[~2019-04-16 14:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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
2019-02-20 19:02 ` [PATCH 2/2] ARM: multi_v7_defconfig: Update for moved options Tony Lindgren
2019-04-16 14:35 ` Tony Lindgren [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=20190416143516.GE2839@atomide.com \
    --to=tony@atomide.com \
    --cc=arnd@arndb.de \
    --cc=geert+renesas@glider.be \
    --cc=horms+renesas@verge.net.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=olof@lixom.net \
    --cc=thierry.reding@gmail.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 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.