All of lore.kernel.org
 help / color / mirror / Atom feed
From: anish singh <anish198519851985@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
	anish kumar <anish.singh@samsung.com>,
	MyungJoo Ham <myungjoo.ham@samsung.com>
Subject: Re: [PATCH] [PATCH V6]Extcon: adc_jack: adc-jack driver to support 3.5 pi or simliar devices
Date: Fri, 17 Aug 2012 08:59:04 +0530	[thread overview]
Message-ID: <CAK7N6vpskT=nhBcvdBKopX_oySdH-j_7c62aB1Q5FxGxfjE3cg@mail.gmail.com> (raw)
In-Reply-To: <20120816174019.GA10918@kroah.com>

On Thu, Aug 16, 2012 at 11:10 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> On Fri, Aug 10, 2012 at 12:29:43AM -0700, anish kumar wrote:
>> From: anish kumar <anish198519851985@gmail.com>
>>
>> External connector devices that decides connection information based on
>> ADC values may use adc-jack device driver. The user simply needs to
>> provide a table of adc range and connection states. Then, extcon
>> framework will automatically notify others.
>
> This patch breaks the build:
>         ERROR: "extcon_cable_name" [drivers/extcon/extcon-adc-jack.ko] undefined!
>
> And, if you read the comment about extcon_cable_name, it says to not use
> it like you are trying to use it.
>
> So, care to fix this up?
Sorry Greg,I was on travel so couldn't fix it up.However soon I will be sending
a patch for this.Looks like we can remove the extcon_cable_name altogether
as it we are anyway getting it from platform data.
>
> thanks,
>
> greg k-h

      reply	other threads:[~2012-08-17  3:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-10  7:29 [PATCH] [PATCH V6]Extcon: adc_jack: adc-jack driver to support 3.5 pi or simliar devices anish kumar
2012-08-16 17:40 ` Greg KH
2012-08-17  3:29   ` anish singh [this message]

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='CAK7N6vpskT=nhBcvdBKopX_oySdH-j_7c62aB1Q5FxGxfjE3cg@mail.gmail.com' \
    --to=anish198519851985@gmail.com \
    --cc=anish.singh@samsung.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-iio@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.