From: gregory.clement@bootlin.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: arm for v4.18 (#1)
Date: Mon, 28 May 2018 17:13:35 +0200 [thread overview]
Message-ID: <87wovnx17k.fsf@bootlin.com> (raw)
In-Reply-To: <20180525115718.o426ixt6bilonjnx@localhost> (Olof Johansson's message of "Fri, 25 May 2018 04:57:18 -0700")
Hi Olof,
On ven., mai 25 2018, Olof Johansson <olof@lixom.net> wrote:
> On Thu, May 17, 2018 at 02:59:42PM +0200, Gregory CLEMENT wrote:
>> Hi,
>>
>> Here is the first pull request for arm for mvebu for v4.18.
>>
>> As I feared, there were (trivial) merge issues due to the defconfig
>> update in linux-next. The best place to solve them is in your tree, so
>> as soon as you will pull this, I will remove from my mvebu/for-next
>> branch.
>
> Hmm. Yeah, this is because you took upon yourself to run 'make savedefconfig'
> for all platforms on this shared defconfig. This will of course conflict with
> everything everywhere, and it doesn't seem like a good idea to do this way.
>
> What you're really doing here is turning on one single option? Just do that.
>
> We can run savedefconfig at the end of a merge window here instead of having
> one of the platform maintainers do it.
Great, so could you do it for this release (I mean 4.18)? Indeed the
multi_v7_defconfig had not been sync since a long time.
>
> So, feel free to send just the NAND patch, and I can fix it up when I apply it
> if needed.
OK I am going to send you this patch rebased on a clean v4.17-rc1.
Gregory
>
> Thanks!
>
>
> -Olof
>
--
Gregory Clement, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
prev parent reply other threads:[~2018-05-28 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 12:59 [GIT PULL] ARM: mvebu: arm for v4.18 (#1) Gregory CLEMENT
2018-05-25 11:57 ` Olof Johansson
2018-05-28 15:13 ` Gregory CLEMENT [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=87wovnx17k.fsf@bootlin.com \
--to=gregory.clement@bootlin.com \
--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 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.