From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Len Brown <lenb@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: [git pull request] ACPI patches for 2.6.35-merge
Date: Sat, 29 May 2010 00:36:34 +0200 [thread overview]
Message-ID: <201005290036.34495.rjw@sisk.pl> (raw)
In-Reply-To: <alpine.LFD.2.00.1005281641080.4045@localhost.localdomain>
On Friday 28 May 2010, Len Brown wrote:
> Hi Linus,
>
> please pull from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git release
>
> This will update the files shown below.
Hmm, it looks like you omitted these two:
https://patchwork.kernel.org/patch/91560/
https://patchwork.kernel.org/patch/91558/
Was that intentional or were they simply forgotten?
Rafael
next prev parent reply other threads:[~2010-05-28 22:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 20:42 [git pull request] ACPI patches for 2.6.35-merge Len Brown
2010-05-28 22:36 ` Rafael J. Wysocki [this message]
2010-05-29 3:40 ` Len Brown
2010-05-29 20:27 ` Rafael J. Wysocki
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=201005290036.34495.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).