public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: MyungJoo Ham <myungjoo.ham@samsung.com>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Donggeun Kim <dg77.kim@samsung.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] extcon: Add EXTCON_MECHANICAL cable type for physical presence
Date: Wed, 2 May 2012 13:13:21 -0700	[thread overview]
Message-ID: <20120502201321.GA26275@kroah.com> (raw)
In-Reply-To: <1335951531-5967-1-git-send-email-broonie@opensource.wolfsonmicro.com>

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@opensource.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

  reply	other threads:[~2012-05-02 20:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-02  9:38 [PATCH] extcon: Add EXTCON_MECHANICAL cable type for physical presence Mark Brown
2012-05-02 20:13 ` Greg Kroah-Hartman [this message]
2012-05-02 23:03   ` Mark Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120502201321.GA26275@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=dg77.kim@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox