From: Chris Largret <largret@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.33 staging rt2870 += Belkin F5D8055 Wireless-N USB Dongle
Date: Wed, 3 Mar 2010 05:24:26 -0600 [thread overview]
Message-ID: <d426fb281003030324v6dc6216ch53bdb30ffc18a9be@mail.gmail.com> (raw)
In-Reply-To: <20100302232738.GA314@kroah.com>
On Tue, Mar 2, 2010 at 5:27 PM, Greg KH <greg@kroah.com> wrote:
> Next time, please cc: me with any staging patches.
>
> Can you resend this with a "Signed-off-by:" line so that I can apply it?
> The kernel file, Documentation/SubmittingPatches describes what this
> entails.
Thanks, I'll try to use checkpatch.pl next time.
Description: Adds Belkin F5D8055 Wireless-N USB support to the rt2870
staging driver.
Signed-off-by: Chris Largret <largret@gmail.com>
diff -upr linux-2.6.33-orig/drivers/staging/rt2860/usb_main_dev.c
linux-2.6.33/drivers/staging/rt2860/usb_main_dev.c
--- linux-2.6.33-orig/drivers/staging/rt2860/usb_main_dev.c 2010-02-24
12:52:17.000000000 -0600
+++ linux-2.6.33/drivers/staging/rt2860/usb_main_dev.c 2010-03-02
12:13:05.000000000 -0600
@@ -63,6 +63,7 @@ struct usb_device_id rtusb_usb_id[] = {
{USB_DEVICE(0x07D1, 0x3C11)}, /* D-Link */
{USB_DEVICE(0x14B2, 0x3C07)}, /* AL */
{USB_DEVICE(0x050D, 0x8053)}, /* Belkin */
+ {USB_DEVICE(0x050D, 0x825B)}, /* Belkin */
{USB_DEVICE(0x14B2, 0x3C23)}, /* Airlink */
{USB_DEVICE(0x14B2, 0x3C27)}, /* Airlink */
{USB_DEVICE(0x07AA, 0x002F)}, /* Corega */
Chris
next prev parent reply other threads:[~2010-03-03 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 22:22 Chris Largret
2010-03-02 23:27 ` Greg KH
2010-03-03 11:24 ` Chris Largret [this message]
2010-04-27 18:54 ` patch staging-rt2860-add-belkin-f5d8055-wireless-n-usb-dongle-device-id.patch added to gregkh-2.6 tree gregkh
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=d426fb281003030324v6dc6216ch53bdb30ffc18a9be@mail.gmail.com \
--to=largret@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®