From: Kukjin Kim <kgene.kim@samsung.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org,
Kukjin Kim <kgene.kim@samsung.com>,
'Russell King' <rmk+kernel@arm.linux.org.uk>,
linux-samsung-soc@vger.kernel.org, ben-linux@fluff.org
Subject: Re: [GIT PULL] Samsung devel-4 for v3.2
Date: Sun, 06 Nov 2011 14:04:15 +0900 [thread overview]
Message-ID: <4EB6154F.2050501@samsung.com> (raw)
In-Reply-To: <201111050056.51554.arnd@arndb.de>
On 11/05/11 08:56, Arnd Bergmann wrote:
> On Saturday 05 November 2011, Kukjin Kim wrote:
>> Arnd Bergmann wrote:
>
>>> Please send the contents split up into separate branches (dt, spi, clkdev,
>>> rename, devel) for 3.3. I think it's ok if you want to send just the
>>> rename patch for 3.2 the way we had discussed earlier, because this kind
>>> of patch really makes sense at the end of the merge window.
>>>
>> Hi Arnd,
>>
>> OK, I will send the rename branch in a half an hour and make separate
>> branches for others which will be merged next time.
>
> Ok, very good. I'm sending the pull requests for the other two branches
> right now, I assume Linus will take them quickly (or not at all if he
> has unexpected objections), so you could base your pull request on top
> of his merge.
>
Hi Arnd,
I remade 'next-samsung-exynos' branch based on latest mainline which
includes arm-soc/next/cleanup3 and arm-soc/next/devel2 just now so that
you can send it to Linus easily :)
If any problems, please let me know.
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
prev parent reply other threads:[~2011-11-06 5:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 5:53 [GIT PULL] Samsung devel-4 for v3.2 Kukjin Kim
2011-11-04 23:20 ` Arnd Bergmann
2011-11-04 23:32 ` Kukjin Kim
2011-11-04 23:56 ` Arnd Bergmann
2011-11-06 5:04 ` Kukjin Kim [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=4EB6154F.2050501@samsung.com \
--to=kgene.kim@samsung.com \
--cc=arnd@arndb.de \
--cc=ben-linux@fluff.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
/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