All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Greg KH <greg@kroah.com>
Cc: linux-usb@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] USB: OTG: twl4030 build fix
Date: Tue, 16 Dec 2008 14:33:39 -0800	[thread overview]
Message-ID: <873agn698c.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20081216220155.GB3291@kroah.com> (Greg KH's message of "Tue\, 16 Dec 2008 14\:01\:55 -0800")

Greg KH <greg@kroah.com> writes:

> On Mon, Dec 15, 2008 at 04:00:03PM -0800, Kevin Hilman wrote:
>> Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
>> ---
>>  drivers/usb/otg/twl4030-usb.c |    2 +-
>>  1 files changed, 1 insertions(+), 1 deletions(-)
>> 
>> diff --git a/drivers/usb/otg/twl4030-usb.c b/drivers/usb/otg/twl4030-usb.c
>> index a000fb3..416e441 100644
>> --- a/drivers/usb/otg/twl4030-usb.c
>> +++ b/drivers/usb/otg/twl4030-usb.c
>> @@ -696,7 +696,7 @@ static int __exit twl4030_usb_remove(struct platform_device *pdev)
>>  
>>  static struct platform_driver twl4030_usb_driver = {
>>  	.probe		= twl4030_usb_probe,
>> -	.remove		= __exit_p(twl4030_remove),
>> +	.remove		= __exit_p(twl4030_usb_remove),
>>  	.driver		= {
>>  		.name	= "twl4030_usb",
>>  		.owner	= THIS_MODULE,
>
> This driver is not in the mainline, or my USB tree.  Where is it at?
>

Sorry for the confusion,

This driver is in the linux-omap tree, but I thought David Brownell
had it queued up for your tree already.

Kevin



  reply	other threads:[~2008-12-16 22:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-16  0:00 [PATCH] USB: OTG: twl4030 build fix Kevin Hilman
2008-12-16 22:01 ` Greg KH
2008-12-16 22:33   ` Kevin Hilman [this message]
     [not found]     ` <873agn698c.fsf-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
2008-12-17  4:25       ` David Brownell
2008-12-30  8:54         ` Tony Lindgren

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=873agn698c.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=greg@kroah.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /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.