From: Greg KH <gregkh@suse.de>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: Forest Bond <forest@alittletooquiet.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Staging: vt6656 ?
Date: Tue, 9 Jun 2009 03:51:01 -0700 [thread overview]
Message-ID: <20090609105101.GB15378@suse.de> (raw)
In-Reply-To: <a4423d670906090331o6363fe56g34374967f21552e8@mail.gmail.com>
On Tue, Jun 09, 2009 at 02:31:30PM +0400, Alexander Beregalov wrote:
> Hi Greg, Forest
>
> Are you going to merge driver for VT6656 also?
If someone sends me some patches for it, sure, I will.
thanks,
greg k-h
next prev parent reply other threads:[~2009-06-09 10:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 10:31 Staging: vt6656 ? Alexander Beregalov
2009-06-09 10:51 ` Greg KH [this message]
2009-06-09 11:33 ` Forest Bond
2009-06-28 13:43 ` Bartlomiej Zolnierkiewicz
2009-06-28 13:57 ` Forest Bond
2009-06-28 15:59 ` Bartlomiej Zolnierkiewicz
2009-06-28 16:47 ` Forest Bond
2009-07-02 17:45 ` Bartlomiej Zolnierkiewicz
2009-07-02 18:22 ` Forest Bond
2009-07-06 15:33 ` Bartlomiej Zolnierkiewicz
2009-06-28 17:02 ` [PATCH 1/8] Add pristine upstream vt6656 driver sources to drivers/staging/vt6656 Forest Bond
2009-06-28 17:02 ` [PATCH 2/8] Add includes " Forest Bond
2009-06-28 17:03 ` [PATCH 3/8] Build vt6656.ko, not vntwusb.ko Forest Bond
2009-06-28 17:03 ` [PATCH 4/8] drivers/staging/vt6656/main_usb.c: Drop obsolete fsuid/fsgid accesses Forest Bond
2009-06-28 17:03 ` [PATCH 5/8] vt6656: Replace net_device->priv accesses with netdev_priv calls Forest Bond
2009-06-28 17:03 ` [PATCH 6/8] vt6656: use net_device_ops for management functions Forest Bond
2009-06-28 17:03 ` [PATCH 7/8] vt6656: replace call to info with printk call Forest Bond
2009-06-28 17:03 ` [PATCH 8/8] Integrate drivers/staging/vt6656 into build system Forest Bond
2009-06-28 16:29 ` Staging: vt6656 ? Greg KH
2009-06-28 16:40 ` Forest Bond
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=20090609105101.GB15378@suse.de \
--to=gregkh@suse.de \
--cc=a.beregalov@gmail.com \
--cc=forest@alittletooquiet.net \
--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