From: Arnd Bergmann <arnd@arndb.de>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
'Russell King' <rmk+kernel@arm.linux.org.uk>,
ben-linux@fluff.org
Subject: Re: [GIT PULL] Samsung devel-4 for v3.2
Date: Sat, 5 Nov 2011 00:20:54 +0100 [thread overview]
Message-ID: <201111050020.55071.arnd@arndb.de> (raw)
In-Reply-To: <027f01cc9ab6$2086eae0$6194c0a0$%kim@samsung.com>
On Friday 04 November 2011, Kukjin Kim wrote:
> As we talked in Prague, I'm sending 'pull request for v3.2' Samsung-devel4
> which includes supporting EXYNOS4 DT, SPI clkdev and reorganization
> arch/arm/mach-exynos and small things.
>
> Please pull from:
> git://github.com/kgene/linux-samsung.git next-samsung-devel-4
>
> As a note, the branch includes arm-soc/next/cleanup3 and arm-soc/next/devel2
> based on mainline commit 994c0e99 ("Merge branch 'next/soc' of
> git://git.linaro.org/people/arnd/arm-soc") because it is needed for this and
> they include all of Samsung stuff for v3.2.
>
> And I will be back to kernel.org after this merge window.
>
> If any problems, please let me know.
I've looked through it, and I think I'll hold off for this merge window,
especially given that I had enough trouble with the the other commits
and that the submission is really late. Please realize that I have to
push back on stuff that comes during the merge window.
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.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Samsung devel-4 for v3.2
Date: Sat, 5 Nov 2011 00:20:54 +0100 [thread overview]
Message-ID: <201111050020.55071.arnd@arndb.de> (raw)
In-Reply-To: <027f01cc9ab6$2086eae0$6194c0a0$%kim@samsung.com>
On Friday 04 November 2011, Kukjin Kim wrote:
> As we talked in Prague, I'm sending 'pull request for v3.2' Samsung-devel4
> which includes supporting EXYNOS4 DT, SPI clkdev and reorganization
> arch/arm/mach-exynos and small things.
>
> Please pull from:
> git://github.com/kgene/linux-samsung.git next-samsung-devel-4
>
> As a note, the branch includes arm-soc/next/cleanup3 and arm-soc/next/devel2
> based on mainline commit 994c0e99 ("Merge branch 'next/soc' of
> git://git.linaro.org/people/arnd/arm-soc") because it is needed for this and
> they include all of Samsung stuff for v3.2.
>
> And I will be back to kernel.org after this merge window.
>
> If any problems, please let me know.
I've looked through it, and I think I'll hold off for this merge window,
especially given that I had enough trouble with the the other commits
and that the submission is really late. Please realize that I have to
push back on stuff that comes during the merge window.
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.
Arnd
next prev parent reply other threads:[~2011-11-04 23:21 UTC|newest]
Thread overview: 10+ 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 5:53 ` Kukjin Kim
2011-11-04 23:20 ` Arnd Bergmann [this message]
2011-11-04 23:20 ` Arnd Bergmann
2011-11-04 23:32 ` Kukjin Kim
2011-11-04 23:32 ` Kukjin Kim
2011-11-04 23:56 ` Arnd Bergmann
2011-11-04 23:56 ` Arnd Bergmann
2011-11-06 5:04 ` Kukjin Kim
2011-11-06 5:04 ` 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=201111050020.55071.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=ben-linux@fluff.org \
--cc=kgene.kim@samsung.com \
--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 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.