[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1267189882.18491.63.camel@violet>
Date: Fri, 26 Feb 2010 14:11:22 +0100
From: Marcel Holtmann <marcel@...tmann.org>
To: florian@...kler.org
Cc: Henrique de Moraes Holschuh <hmh@....eng.br>,
Johannes Berg <johannes@...solutions.net>,
"John W. Linville" <linville@...driver.com>,
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,
Greg Kroah-Hartman <gregkh@...e.de>
Subject: Re: [PATCH v2 2/2] enhance sysfs rfkill interface
Hi Florian,
> > > I am not shure about those names.
> >
> > I don't like them. IMHO, you don't gain anything by being this terse, and
> > it is difficult to understand what they mean at first glance.
> >
> > > Other alternatives:
> > > [hs]w_block
> > > block_[hs]w
> >
>
> I made that blocked_sw and blocked_hw, so that they are
> lexicographically nearby and that they also give more information about
> their content.
>
> 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
--
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