From: Kukjin Kim <kgene@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
arm@kernel.org, Kevin Hilman <khilman@linaro.org>,
Kukjin Kim <kgene@kernel.org>, 'Olof Johansson' <olof@lixom.net>,
Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Subject: Re: [GIT PULL] Samsung related to updating multi_v7_defconfig
Date: Sat, 23 May 2015 11:16:36 +0900 [thread overview]
Message-ID: <555FE304.5090706@kernel.org> (raw)
In-Reply-To: <2227456.dXyEpqfCYe@wuerfel>
On 05/23/15 00:15, Arnd Bergmann wrote:
> On Thursday 21 May 2015 12:07:33 Kukjin Kim wrote:
>>
>> Here is multi_v7_defconfig update and mostly including regarding exynos
>> stuff based on savedefconfig which could remove useless configs based on
>> checking of dependencies.
>>
>> This series is based on v4.1-rc1 and I can provide resolution of
>> conflicts with arm-soc/next/defconfig. See below.
>>
>> Note that, IMHO we need to check 'savedefconfig when defconfig is
>> updated so that we could remove useless lines and avoid to miss some
>> defconfigs because of dependency.
>>
>> Anyway please pull and if any concerns, please kindly let me know.
>>
Hi,
> The conflict got a little too wild for my taste, so I dropped your
> 'savedefconfig' commit and rebased the other ones on top of the
> branch I already had.
>
OK, no problem :-)
> Please check that the result is still ok for you.
>
When I checked, I didn't find any missing stuff from my side. Looks
good, thanks.
- Kukjin
WARNING: multiple messages have this Message-ID (diff)
From: kgene@kernel.org (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Samsung related to updating multi_v7_defconfig
Date: Sat, 23 May 2015 11:16:36 +0900 [thread overview]
Message-ID: <555FE304.5090706@kernel.org> (raw)
In-Reply-To: <2227456.dXyEpqfCYe@wuerfel>
On 05/23/15 00:15, Arnd Bergmann wrote:
> On Thursday 21 May 2015 12:07:33 Kukjin Kim wrote:
>>
>> Here is multi_v7_defconfig update and mostly including regarding exynos
>> stuff based on savedefconfig which could remove useless configs based on
>> checking of dependencies.
>>
>> This series is based on v4.1-rc1 and I can provide resolution of
>> conflicts with arm-soc/next/defconfig. See below.
>>
>> Note that, IMHO we need to check 'savedefconfig when defconfig is
>> updated so that we could remove useless lines and avoid to miss some
>> defconfigs because of dependency.
>>
>> Anyway please pull and if any concerns, please kindly let me know.
>>
Hi,
> The conflict got a little too wild for my taste, so I dropped your
> 'savedefconfig' commit and rebased the other ones on top of the
> branch I already had.
>
OK, no problem :-)
> Please check that the result is still ok for you.
>
When I checked, I didn't find any missing stuff from my side. Looks
good, thanks.
- Kukjin
next prev parent reply other threads:[~2015-05-23 2:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 3:07 [GIT PULL] Samsung related to updating multi_v7_defconfig Kukjin Kim
2015-05-21 3:07 ` Kukjin Kim
2015-05-22 15:15 ` Arnd Bergmann
2015-05-22 15:15 ` Arnd Bergmann
2015-05-23 2:16 ` Kukjin Kim [this message]
2015-05-23 2:16 ` Kukjin Kim
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=555FE304.5090706@kernel.org \
--to=kgene@kernel.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=javier.martinez@collabora.co.uk \
--cc=k.kozlowski@samsung.com \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--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 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.