From: kgene@kernel.org (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: manual merge of the samsung tree with the arm-soc andat91 trees
Date: Thu, 21 May 2015 12:29:03 +0900 [thread overview]
Message-ID: <555D50FF.9060700@kernel.org> (raw)
In-Reply-To: <CAJKOXPeQEvcUF1NcnSEAMGf5JE2ySftFtP9DHij6siDfzTjPtA@mail.gmail.com>
On 05/21/15 10:20, Krzysztof Kozlowski wrote:
> 2015-05-20 18:47 GMT+09:00 Geert Uytterhoeven <geert@linux-m68k.org>:
>> On Wed, May 20, 2015 at 11:16 AM, Alexandre Belloni
>> <alexandre.belloni@free-electrons.com> wrote:
>>> On 20/05/2015 at 09:35:36 +0900, Krzysztof Kozlowski wrote :
>>>> 2015-05-20 9:27 GMT+09:00 Stephen Rothwell <sfr@canb.auug.org.au>:
>>>>> Today's linux-next merge of the samsung tree got a conflict in
>>>>> arch/arm/configs/multi_v7_defconfig between various commits from the
>>>>> arm-soc and at91 trees and various commits from the samsung tree.
>>>>>
>>>>> I fixed it up (see below) and can carry the fix as necessary (no action
>>>>> is required).
>>>>
>>>> Hi,
>>>>
>>>> Thanks for the merge.
>>>>
>>>> The parts coming from samsung-soc related to manually toggling stuff
>>>> (by me and Javier) look fine. The rest (coming from Kukjin's
>>>> savedefconfig) I don't know - too much of them.
>>>>
>>>
>>> Hum, last time I asked, we were not supposed to do a savedefconfig on
>>> multi_v7...
>>
>> Yeah, IMHO it's something the arm-soc maintainers should do only right
>> after rc1.
>>
>> Doing it at any other point in time may remove options that have just been
>> added to multi_v7_defconfig by an arm-soc submaintainer, and that depend on
>> a Kconfig change queued in another maintainer's for-next branch.
>
> It also depends on which tree and branch the savedefconfig was
> performed. If on Linus' master then probably it is not a good idea at
> any time.
>
>> Personally, I think no arm-soc submaintainer should touch multi_v7_defconfig,
>> and all changes should be applied by the arm-soc maintainers.
>
> Actually Arnd suggested this:
> https://lkml.org/lkml/2015/5/15/303
> [PATCH 0/9] multi_v7_defconfig: Enable options for Exynos Chromebooks
>
Thanks you guys.
I've sent a pull-request for the update of multi_v7_defconfig just now.
And IMHO need to keep it with savedefconfig from now on...
- Kukjin
next prev parent reply other threads:[~2015-05-21 3:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 0:27 linux-next: manual merge of the samsung tree with the arm-soc and at91 trees Stephen Rothwell
2015-05-20 0:35 ` Krzysztof Kozlowski
2015-05-20 9:16 ` Alexandre Belloni
2015-05-20 9:47 ` Geert Uytterhoeven
2015-05-21 1:20 ` Krzysztof Kozlowski
2015-05-21 3:29 ` Kukjin Kim [this message]
2015-05-20 7:45 ` Nicolas Ferre
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=555D50FF.9060700@kernel.org \
--to=kgene@kernel.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).