linux-kernel - Re: [PATCH 15/15] rfkill: document rw rfkill switches and clarify input subsystem interactions (v2)

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: <200805291919.04384.IvDoorn@gmail.com>
Date:	Thu, 29 May 2008 19:19:04 +0200
From:	Ivo van Doorn <ivdoorn@...il.com>
To:	Henrique de Moraes Holschuh <hmh@....eng.br>
Cc:	linux-kernel@...r.kernel.org, Thomas Renninger <trenn@...e.de>,
	Dmitry Torokhov <dtor@...l.ru>
Subject: Re: [PATCH 15/15] rfkill: document rw rfkill switches and clarify input subsystem interactions (v2)

On Thursday 29 May 2008, Henrique de Moraes Holschuh wrote:
> On Thu, 29 May 2008, Ivo van Doorn wrote:
> > > This version better documents *_RFKILL_ALL.  Is it good enough for an
> > > ACK for patch 14 of 15?
> > 
> > Yes, you can put my ack on patch 14.
> > Thanks for the documentation update. :)
> 
> Then, this entire batch is ready for merging.  Now, if only Len would
> come back from wherever he disappeared to, in order to merge the two
> thinkpad-acpi patches, I could send it to netdev for merge.

Actually,  I believe the correct merge order would through wireless-dev,
which means the patches should go to John Linville and linux-wireless in the CC.

> I will at least publish the entire stack as a thinkpad-acpi pre-release
> version, to get some testing on the real world with some power users.
> 
> I am thinking about how to best handle the global states.  Doing it
> through the rfkill class is ready, but the result was *UGLY*.  More on
> this later.

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