From: Tony Lindgren <tony@atomide.com>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: Ben Dooks <ben@fluff.org.uk>,
Samuel Ortiz <sameo@linux.intel.com>,
Kevin Hilman <khilman@deeprootsystems.com>,
Paul Walmsley <paul@pwsan.com>,
"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 0/24] omap4 for 2.6.34
Date: Tue, 16 Feb 2010 11:02:57 -0800 [thread overview]
Message-ID: <20100216190257.GP21755@atomide.com> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB02C3CF80C3@dbde02.ent.ti.com>
Hi,
* Shilimkar, Santosh <santosh.shilimkar@ti.com> [100216 07:33]:
> Tony,
> Here are some patches towards upcoming 34 merge window. They are generated against
> linux-omap master as you suggested.
>
> I am also copying Ben, Samuel, Liam, Paul and Kevin since some of the changes
> are in mfd, regulator, i2c and clocks.
Thanks. Can you please split this into several smaller sets?
1. Core omap changes done against linux-omap master branch
Send to linux-omap list with linux-arm-kernel Cc'd.
2. Clock framework dummy_ck changes done against linux-omap master branch.
This should leave out most of the driver changes in your series.
Send to linux-omap list with linux-arm-kernel Cc'd.
3. I2C changes against done against 2.6.33-rc8 + "Add support for 16-bit registers"
Send to Ben and i2c list with linux-omap list Cc'd.
4. MFD changes done against 2.6.33-rc8
Send to Samuel with linux-omap list Cc'd.
Regards,
Tony
next prev parent reply other threads:[~2010-02-16 19:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 15:36 [PATCH 0/24] omap4 for 2.6.34 Shilimkar, Santosh
2010-02-16 15:43 ` Shilimkar, Santosh
2010-02-16 19:02 ` Tony Lindgren [this message]
2010-02-17 5:16 ` Shilimkar, Santosh
2010-02-17 17:19 ` Tony Lindgren
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=20100216190257.GP21755@atomide.com \
--to=tony@atomide.com \
--cc=ben@fluff.org.uk \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=paul@pwsan.com \
--cc=sameo@linux.intel.com \
--cc=santosh.shilimkar@ti.com \
/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