From: dwalker@codeaurora.org (Daniel Walker)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Samsung S5P updates for 2.6.36 merge window
Date: Tue, 10 Aug 2010 10:55:11 -0700 [thread overview]
Message-ID: <1281462911.9400.10.camel@c-dwalke-linux.qualcomm.com> (raw)
In-Reply-To: <1281462308.9400.7.camel@c-dwalke-linux.qualcomm.com>
On Tue, 2010-08-10 at 10:45 -0700, Daniel Walker wrote:
> On Mon, 2010-08-09 at 19:21 +0900, Kukjin Kim wrote:
> > arch/arm/Kconfig | 37 +-
> > arch/arm/Makefile | 1 +
Sorry, just realized this is going to Russell .. The reason I commented
on it is because this code has been in -next for a long time, and it
sitting in -next will just cause conflicts when Russell accepts other
mods to Kconfig .. So if you don't care about the conflict I guess it
doesn't matter ..
Daniel
--
Sent by an consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
prev parent reply other threads:[~2010-08-10 17:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 10:21 [GIT PULL] Samsung S5P updates for 2.6.36 merge window Kukjin Kim
2010-08-09 10:33 ` Russell King - ARM Linux
2010-08-09 10:43 ` Kukjin Kim
2010-08-10 17:45 ` Daniel Walker
2010-08-10 17:55 ` Daniel Walker [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=1281462911.9400.10.camel@c-dwalke-linux.qualcomm.com \
--to=dwalker@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).