linux-kernel - Re: [PATCH v2 0/9] eeepc cleanup

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] [day] [month] [year] [list]

Date:	Fri, 19 Sep 2014 19:33:11 +0200
From:	Frans Klaver <fransklaver@...il.com>
To:	Darren Hart <dvhart@...radead.org>
CC:	Corentin Chary <corentin.chary@...il.com>,
	Rafael Wysocki <rafael.j.wysocki@...el.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	acpi4asus-user@...ts.sourceforge.net,
	platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/9] eeepc cleanup

On 19 September 2014 19:25:38 CEST, Darren Hart <dvhart@...radead.org> wrote:
>On Wed, Sep 17, 2014 at 11:47:18PM +0200, Frans Klaver wrote:
>> Here's the second installment cleaning up some things in the eeepc
>laptop
>> driver.
>> 
>> This depends on "eeepc-laptop: simplify parse_arg()".
>> 
>> For those interested, I keep a copy based on Darren's testing branch
>on
>> github:
>
>Please note, "testing" is strictly for use with Fengguang's 0day robot.
>It
>*will* rebase and be recreated willy nilly.
>
>If you want to base on something I've queued, I suggest the "for-next"
>branch as
>I expect that to be far more stable. Rabses should be *very* rare
>there.
>
>Feel free to use "testing" if you need to, just be aware it will
>rebase.
>

I'll keep that in mind for the next batch ;) 


>> 
>> 	https://github.com/fransklaver/linux.git tags/eeepc_cleanup_v2
>
>Queued for testing.
>
>Thanks Frans!

Thanks, 
Frans 


--
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/