From: Kevin Hilman <khilman@kernel.org>
To: Kukjin Kim <kgene@kernel.org>
Cc: arm@kernel.org, Arnd Bergmann <arnd@arndb.de>,
'Olof Johansson' <olof@lixom.net>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>
Subject: Re: [GIT PULL 2/5] Samsung 2nd defconfig for v4.2
Date: Thu, 11 Jun 2015 14:30:48 -0700 [thread overview]
Message-ID: <7hwpzac4qf.fsf@deeprootsystems.com> (raw)
In-Reply-To: <5571E4B0.5090001@kernel.org> (Kukjin Kim's message of "Sat, 06 Jun 2015 03:04:32 +0900")
Kukjin Kim <kgene@kernel.org> writes:
> Hi,
>
> Here is 2nd defconfig updates for v4.2 but actually just one patch for
> Samsung updates for multi_v7_defconfig. Please pull or apply the patch
> directly, anyway I'm fine either way.
>
> Note that this is based on arm-soc/next/defconfig to avoid useless merge
> conflicts and I've merged previous tags/samsung-defconfig-2.
We don't mind the simple conflicts like this.
It's better if you just send an updated pull that's based on your
previous pull.
Anyways, I cherry-picked this patch into next/defconfig.
Thanks,
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@kernel.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/5] Samsung 2nd defconfig for v4.2
Date: Thu, 11 Jun 2015 14:30:48 -0700 [thread overview]
Message-ID: <7hwpzac4qf.fsf@deeprootsystems.com> (raw)
In-Reply-To: <5571E4B0.5090001@kernel.org> (Kukjin Kim's message of "Sat, 06 Jun 2015 03:04:32 +0900")
Kukjin Kim <kgene@kernel.org> writes:
> Hi,
>
> Here is 2nd defconfig updates for v4.2 but actually just one patch for
> Samsung updates for multi_v7_defconfig. Please pull or apply the patch
> directly, anyway I'm fine either way.
>
> Note that this is based on arm-soc/next/defconfig to avoid useless merge
> conflicts and I've merged previous tags/samsung-defconfig-2.
We don't mind the simple conflicts like this.
It's better if you just send an updated pull that's based on your
previous pull.
Anyways, I cherry-picked this patch into next/defconfig.
Thanks,
Kevin
next prev parent reply other threads:[~2015-06-11 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 18:04 [GIT PULL 2/5] Samsung 2nd defconfig for v4.2 Kukjin Kim
2015-06-05 18:04 ` Kukjin Kim
2015-06-11 21:30 ` Kevin Hilman [this message]
2015-06-11 21:30 ` Kevin Hilman
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=7hwpzac4qf.fsf@deeprootsystems.com \
--to=khilman@kernel.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.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.