From: Len Brown <lenb@kernel.org>
To: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
toshi.kani@hp.com, liuj97@gmail.com,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [PATCH v5] create sun sysfs file
Date: Mon, 05 Nov 2012 20:27:28 -0500 [thread overview]
Message-ID: <50986780.9030503@kernel.org> (raw)
In-Reply-To: <50763485.1080607@kernel.org>
Yasuaki,
Please refresh this patch on top of linux-next and re-send to Rafael.
I've dropped it from my tree.
thanks,
-Len
On 10/10/2012 10:52 PM, Len Brown wrote:
> v5 applied (with typo fixed).
> In the future, it would be better if your patches apply to the latest
> upstream kernel. (_STR made changes in same place as _SUN)
>
> thanks,
> Len Brown, Intel Open Source Technology Center
>
prev parent reply other threads:[~2012-11-06 1:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 6:49 [PATCH v5] create sun sysfs file Yasuaki Ishimatsu
2012-10-10 8:31 ` Yasuaki Ishimatsu
2012-10-11 2:52 ` Len Brown
2012-11-06 1:27 ` Len Brown [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=50986780.9030503@kernel.org \
--to=lenb@kernel.org \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuj97@gmail.com \
--cc=rjw@sisk.pl \
--cc=toshi.kani@hp.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;
as well as URLs for NNTP newsgroup(s).