From: Len Brown <lenb@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-pm@lists.linux-foundation.org
Subject: Re: [GIT PULL] idle patches for Linux 3.1
Date: Thu, 04 Aug 2011 01:03:40 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.02.1108040030550.29492@x980> (raw)
In-Reply-To: <CA+55aFxikiro4cEwGEOMCGUswyPsaAwyspP1cFUviJ5OUKOZJw@mail.gmail.com>
> On Wed, Aug 3, 2011 at 10:54 AM, Len Brown <lenb@kernel.org> wrote:
> >
> > please pull from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-idle-2.6.git idle-release
>
> As with the APEI tree, the commits are all recent and cannot have been
> in -next. It's the last day before the merge window closes, please
> tell me why I should take this in this cycle at all?
I re-based this branch immediately before pushing
in order to add "Acked-by" annotations.
The cpuidle patches were in linux-next back in April.
But they were on a branch with other patches that got
deferred till 2012 b/c some folks were uneasy with
me deleting so much code so suddenly. I cherry-picked
some simple ones here b/c IBM asked me to in order to
make their upcoming p-series cpuidle patches cleaner.
The mrst pmu.c driver is new. MRST doesn't work without it.
Of course, if you don't have CONFIG_X86_MRST=y, you don't care.
Yes, this pull request is late, and if you skip it,
life will still go on. You'll simply see the same
patches wating for you in 10 weeks. On the other hand,
some developers will have a happier summer if these get upstream now,
and I'm here to support them if anything goes wrong.
thanks,
-Len
next prev parent reply other threads:[~2011-08-04 5:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 20:54 Len Brown
2011-08-04 0:55 ` Linus Torvalds
2011-08-04 5:03 ` Len Brown [this message]
2011-08-04 22:57 ` [linux-pm] " Kevin Hilman
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=alpine.LFD.2.02.1108040030550.29492@x980 \
--to=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.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
all inboxes | Powered by JetHome®