From: Kukjin Kim <kgene.kim@samsung.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Kukjin Kim <kgene.kim@samsung.com>,
'Olof Johansson' <olof@lixom.net>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] Samsung SoC EXYNOS5250 arch for v3.4
Date: Fri, 16 Mar 2012 13:30:22 -0700 [thread overview]
Message-ID: <4F63A2DE.7070705@samsung.com> (raw)
In-Reply-To: <201203161250.11353.arnd@arndb.de>
Arnd Bergmann wrote:
[...]
>
> As you may have noticed from Stephen's notification about the merge
> conflict, I have put this into the next/soc2 branch now.
>
Yes, thanks.
> I'm not too happy with the resolution of my comments, but in the
Hmm, sorry about that.
> end I think it's better to have it in the tree than not have it.
> While you did reply with explanations for why some of the patches
> were necessary, you did not actually put the explanations into
> the changeset descriptions but only sent a reply to my emails.
Oh, I see. If similar case will happen next time, let me expand its
descritpions.
>
> I don't think that the merge conflict is problematic, especially
> since Linus won't see the same thing that Stephen did, but as I
> wrote in the other mail, please check that my resolution was correct.
>
Yes, as I replied, I think your resolution and Stehpehn's one, both are
correct to me and just different postion of 'int ret'. As a note, I just
fixed it up with yours.
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
WARNING: multiple messages have this Message-ID (diff)
From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Samsung SoC EXYNOS5250 arch for v3.4
Date: Fri, 16 Mar 2012 13:30:22 -0700 [thread overview]
Message-ID: <4F63A2DE.7070705@samsung.com> (raw)
In-Reply-To: <201203161250.11353.arnd@arndb.de>
Arnd Bergmann wrote:
[...]
>
> As you may have noticed from Stephen's notification about the merge
> conflict, I have put this into the next/soc2 branch now.
>
Yes, thanks.
> I'm not too happy with the resolution of my comments, but in the
Hmm, sorry about that.
> end I think it's better to have it in the tree than not have it.
> While you did reply with explanations for why some of the patches
> were necessary, you did not actually put the explanations into
> the changeset descriptions but only sent a reply to my emails.
Oh, I see. If similar case will happen next time, let me expand its
descritpions.
>
> I don't think that the merge conflict is problematic, especially
> since Linus won't see the same thing that Stephen did, but as I
> wrote in the other mail, please check that my resolution was correct.
>
Yes, as I replied, I think your resolution and Stehpehn's one, both are
correct to me and just different postion of 'int ret'. As a note, I just
fixed it up with yours.
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
next prev parent reply other threads:[~2012-03-16 20:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 14:17 [GIT PULL] Samsung SoC EXYNOS5250 arch for v3.4 Kukjin Kim
2012-03-15 14:17 ` Kukjin Kim
2012-03-16 12:50 ` Arnd Bergmann
2012-03-16 12:50 ` Arnd Bergmann
2012-03-16 20:30 ` Kukjin Kim [this message]
2012-03-16 20:30 ` 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=4F63A2DE.7070705@samsung.com \
--to=kgene.kim@samsung.com \
--cc=arnd@arndb.de \
--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.