From: Andrew Morton <akpm@linux-foundation.org>
To: David Brownell <david-b@pacbell.net>
Cc: lenb@kernel.org, linux-acpi@vger.kernel.org,
bjorn.helgaas@hp.com, len.brown@intel.com
Subject: Re: [patch 06/13] ACPI: updates rtc-cmos device platform_data
Date: Mon, 5 Feb 2007 17:11:43 -0800 [thread overview]
Message-ID: <20070205171143.b1f1be43.akpm@linux-foundation.org> (raw)
In-Reply-To: <200702051707.35256.david-b@pacbell.net>
On Mon, 5 Feb 2007 17:07:34 -0800
David Brownell <david-b@pacbell.net> wrote:
> By the way ... in case I was unclear about this, this does need to _follow_ the
> patch defining the rtc-cmos driver and its platform data. Which I'm sure it
> does in the MM tree, as it does in my own patchsets. :)
>
Oh. Len, please drop.
And, ideally, ack it - then I'll send both patches to Linus at the same time.
Thanks.
next prev parent reply other threads:[~2007-02-06 1:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 0:09 [patch 06/13] ACPI: updates rtc-cmos device platform_data akpm
2007-02-06 1:07 ` David Brownell
2007-02-06 1:11 ` Andrew Morton [this message]
2007-02-09 5:56 ` Len Brown
2007-02-09 6:02 ` Andrew Morton
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=20070205171143.b1f1be43.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bjorn.helgaas@hp.com \
--cc=david-b@pacbell.net \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.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