linux-kernel - Re: [PATCH 0/2] rfkill sysfs ABI

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:	Fri, 12 Mar 2010 14:52:57 -0500
From:	"John W. Linville" <linville@...driver.com>
To:	Florian Mickler <florian@...kler.org>
Cc:	Marcel Holtmann <marcel@...tmann.org>,
	Henrique de Moraes Holschuh <hmh@....eng.br>,
	Johannes Berg <johannes@...solutions.net>,
	linux-wireless@...r.kernel.org,
	Randy Dunlap <rdunlap@...otime.net>,
	Alan Jenkins <alan-jenkins@...fmail.co.uk>,
	linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org
Subject: Re: [PATCH 0/2]  rfkill sysfs ABI

On Fri, Mar 12, 2010 at 07:18:19PM +0100, Florian Mickler wrote:

> sorry! I just realised that you already have the blocked_sw / blocked_hw one's
> queued. 
> 
> This just changes the name of blocked_sw and blocked_hw to "soft" and
> "hard". 
> 
> I don't know what you wanna do. I'm fine with blocked_hw and
> blocked_sw as it's referenced as such (hw/sw) in the code, but Marcel
> wanted to get away from the "hard blocked by hardware" notation, as it
> suggests that the transmitter could only be blocked by hardware...

Could you just submit a third patch that makes the requested name changes?

Thanks!

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@...driver.com			might be all we have.  Be ready.
--
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/