From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: 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: Sat, 5 Nov 2011 00:56:51 +0100 [thread overview]
Message-ID: <201111050056.51554.arnd@arndb.de> (raw)
In-Reply-To: <02d901cc9b4a$15a127f0$40e377d0$%kim@samsung.com>
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.
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:56:51 +0100 [thread overview]
Message-ID: <201111050056.51554.arnd@arndb.de> (raw)
In-Reply-To: <02d901cc9b4a$15a127f0$40e377d0$%kim@samsung.com>
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.
Arnd
next prev parent reply other threads:[~2011-11-04 23:56 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
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 [this message]
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=201111050056.51554.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.