Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965328Ab0BZQcm (ORCPT ); Fri, 26 Feb 2010 11:32:42 -0500 Received: from ist.d-labs.de ([213.239.218.44]:44834 "EHLO mx01.d-labs.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965288Ab0BZQck (ORCPT ); Fri, 26 Feb 2010 11:32:40 -0500 Date: Fri, 26 Feb 2010 17:32:30 +0100 From: Florian Mickler To: Marcel Holtmann Cc: Henrique de Moraes Holschuh , Johannes Berg , "John W. Linville" , linux-wireless@vger.kernel.org, Randy Dunlap , Alan Jenkins , linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, Greg Kroah-Hartman Subject: Re: [PATCH v2 2/2] enhance sysfs rfkill interface Message-ID: <20100226173230.0479bf94@schatten.dmk.lab> In-Reply-To: <1267189882.18491.63.camel@violet> References: <20100225233516.GD5218@khazad-dum.debian.net> <1267182094-15469-1-git-send-email-florian@mickler.org> <1267189882.18491.63.camel@violet> X-Mailer: Claws Mail 3.7.2 (GTK+ 2.16.6; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 895 Lines: 30 On Fri, 26 Feb 2010 14:11:22 +0100 Marcel Holtmann wrote: > Hi Florian, > > blocked_[hs]w -> 0/1 makes IMO kind of sense. > > the kernel and /dev/rfkill just talks about "hard" and "soft" blocks. > > Don't confuse this with hardware and software. It seems were are keeping > to make this stupid semantical error over and over again. So everything > that says hardware, software, hw or sw in the API is bluntly wrong. > > Regards > > Marcel > Yes, ok. I agree that 'hardware block' for something 'out of the control of the driver' seems to be too narrow... Alright. How about blocked_soft and blocked_hard? cheers, Flo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/