linux-kernel - Re: [PATCH] extcon: Add EXTCON_MECHANICAL cable type for physical presence

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: <20120502201321.GA26275@kroah.com>
Date:	Wed, 2 May 2012 13:13:21 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	MyungJoo Ham <myungjoo.ham@...sung.com>,
	Kyungmin Park <kyungmin.park@...sung.com>,
	Donggeun Kim <dg77.kim@...sung.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] extcon: Add EXTCON_MECHANICAL cable type for physical
 presence

On Wed, May 02, 2012 at 10:38:51AM +0100, Mark Brown wrote:
> Some accessory detection mechanisms are able to detect that something is
> physically present in the socket separately to identifying what is present
> in the socket. This information can be useful to applications, for example
> allowing them to indicate that a potentially broken accessory is present,
> so provide a standard way to report it to userspace.
> 
> Signed-off-by: Mark Brown <broonie@...nsource.wolfsonmicro.com>
> ---
>  drivers/extcon/extcon_class.c |    1 +
>  include/linux/extcon.h        |    1 +
>  2 files changed, 2 insertions(+)

Ok, but where is the in-kernel user of this new interface?  Why are we
adding it now before someone actually needs it?

And shouldn't this also update some documentation somewhere as well?

thanks,

greg k-h
--
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/