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]
Date:	Thu, 4 Aug 2011 09:10:09 +0800
From:	huang ying <huang.ying.caritas@...il.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Len Brown <lenb@...nel.org>, linux-kernel@...r.kernel.org,
	linux-acpi@...r.kernel.org, Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [GIT PATCH] APEI patches for Linux 3.1

Hi, Linus,

On Thu, Aug 4, 2011 at 8:52 AM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
> On Wed, Aug 3, 2011 at 9:26 AM, Len Brown <lenb@...nel.org> wrote:
>>
>> Push went here:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git apei-release
>
> No it didn't.
>
> Apparently it went into linux-idle.
>
> Christ, Len. You send me *two* bogus pull requests, and all your pull
> requests  come in at the very end of the merge cycle, when I very
> clearly asked people to try hard to avoid that since I'm supposed to
> be on vacation.
>
> And several of those commits are from today, and cannot have had any testing.
>
> In short: even though Tony told me where to look, I'm not seeing any
> reason to pull this thing. The merge window is not for development,
> and you're simply not making me get the warm and fuzzies about this
> late pull request.

Most APEI patches have been in

git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git test

since July 13th, and have been in linux-next since then.  I think Len
just re-apply these patches in linux-idle tree.

Best Regards,
Huang Ying
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ