linux-kernel - Re: [GIT PULL] idle patches for Linux 3.1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-id: <alpine.LFD.2.02.1108040030550.29492@x980>
Date:	Thu, 04 Aug 2011 01:03:40 -0400 (EDT)
From:	Len Brown <lenb@...nel.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, linux-pm@...ts.linux-foundation.org
Subject: Re: [GIT PULL] idle patches for Linux 3.1

> On Wed, Aug 3, 2011 at 10:54 AM, Len Brown <lenb@...nel.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/