From: Greg KH <gregkh@linuxfoundation.org>
To: Rene Buergel <rene.buergel@sohard.de>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [Patch v5] ezusb: move ezusb.c from drivers/usb/serial to drivers/usb/misc
Date: Wed, 26 Sep 2012 13:28:12 -0700 [thread overview]
Message-ID: <20120926202812.GA9728@kroah.com> (raw)
In-Reply-To: <47b117b0-5776-41c4-8b49-e3a21e80a6a4@shmail0>
On Wed, Sep 26, 2012 at 10:20:19PM +0200, Rene Buergel wrote:
> This patch
> - moves drivers/usb/serial/ezusb.c to drivers/usb/misc/
> - renamed CONFIG_USB_EZUSB to CONFIG_USB_EZUSB_FX2 to avoid build errors
Ah, does this solve the error I was seeing? Nice job figuring that one
out.
greg k-h
next prev parent reply other threads:[~2012-09-26 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c28594f9-45a3-4232-82fc-2f7c65cfb30c@shmail0>
2012-09-26 20:20 ` [Patch v5] ezusb: move ezusb.c from drivers/usb/serial to drivers/usb/misc Rene Buergel
2012-09-26 20:28 ` Greg KH [this message]
2012-09-26 21:27 ` Peter Stuge
2012-09-26 22:08 ` Greg KH
2012-09-26 22:36 ` Rene Buergel
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=20120926202812.GA9728@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rene.buergel@sohard.de \
/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