linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Forest Bond <forest@alittletooquiet.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Greg KH <greg@kroah.com>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	"John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org, Dan Williams <dcbw@redhat.com>
Subject: Re: [PATCH] Add vt6656 driver to drivers/staging.
Date: Tue, 14 Apr 2009 07:39:28 -0400	[thread overview]
Message-ID: <20090414113928.GA20470@storm.local.network> (raw)
In-Reply-To: <1239707258.4778.3.camel@johannes.local>

[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]

Hi,

On Tue, Apr 14, 2009 at 01:07:38PM +0200, Johannes Berg wrote:
> On Tue, 2009-04-14 at 06:52 -0400, Forest Bond wrote:
> > This patch adds the vt6656 driver to drivers/staging.  This code was literally
> > copied from the upstream source archive, available here:
> > 
> >   http://www.viaarena.com/Driver/VT6656_Linux_src_v1.19_12_x86.zip
> > 
> > Copyright: VIA Networking Technologies, Inc.
> > License: GPL
> > Authors: Jerry Chen, Kyle Hsu, Lucas Lin, Lyndon Chen, Tevin Chen, Warren Hsu,
> >          Yiching Chen
> > Signed-off-by: Forest Bond <forest@alittletooquiet.net>
> > 
> > Patch: http://www.alittletooquiet.net/media/code/0002-Add-vt6656-driver-to-drivers-staging.patch.gz
> > Signature: http://www.alittletooquiet.net/media/code/0002-Add-vt6656-driver-to-drivers-staging.patch.gz.sig
> 
> Can we also please add files here saying to not bother the
> linux-wireless list about this crap?

I would assume this is somewhat implied for any code in drivers/staging.  Is
that not the case?

Thanks,
Forest
-- 
Forest Bond
http://www.alittletooquiet.net
http://www.pytagsfs.org

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2009-04-14 11:45 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-14 10:52 [PATCH] Add vt6656 driver to drivers/staging Forest Bond
2009-04-14 11:07 ` Johannes Berg
2009-04-14 11:39   ` Forest Bond [this message]
2009-04-14 11:48     ` Johannes Berg
2009-04-14 12:28       ` Marcel Holtmann
2009-04-14 12:43         ` Johannes Berg
2009-04-14 13:02           ` John W. Linville
2009-04-14 14:19             ` Forest Bond
2009-04-15  1:10               ` Greg KH
2009-04-15  1:51                 ` Forest Bond
2009-04-19 17:09                   ` Forest Bond
2009-04-19 19:52                     ` Larry Finger
2009-04-19 20:01                       ` Forest Bond
2009-04-19 22:32                         ` Greg KH
2009-04-24 11:03                           ` Forest Bond
2009-04-24 14:44                             ` Larry Finger
2009-04-24 14:54                               ` Forest Bond
2009-04-24 22:58                             ` Greg KH
2009-04-25  0:08                               ` Forest Bond
2009-04-25  0:14                                 ` Greg KH
2009-04-25 14:31                                   ` [PATCH 2/8] Add includes to drivers/staging/vt6655 Forest Bond
2009-04-25 14:31                                   ` [PATCH 3/8] Integrate drivers/staging/vt6655 into build system Forest Bond
2009-04-25 14:32                                   ` [PATCH 4/8] Add necessary EXTRA_CFLAGS to drivers/staging/vt6655/Makefile Forest Bond
2009-04-25 14:32                                   ` [PATCH 5/8] Build vt6655.ko, not viawget.ko Forest Bond
2009-04-25 14:32                                   ` [PATCH 6/8] drivers/staging/vt6655/device_main.c: Drop obsolete fsuid/fsgid accesses Forest Bond
2009-04-25 14:32                                   ` [PATCH 7/8] vt6655: Replace net_device->priv accesses with netdev_priv calls Forest Bond
2009-05-01  0:03                                     ` Forest Bond
2009-04-25 14:32                                   ` [PATCH 8/8] vt6655: Remove LINUX_VERSION_CODE preprocessor conditionals Forest Bond
2009-04-15 15:43                 ` [PATCH] Add vt6656 driver to drivers/staging Dan Williams
2009-04-16  2:51                   ` Greg KH
2009-04-15 13:19               ` John W. Linville
2009-04-14 14:52             ` Forest Bond
     [not found]             ` <18916.37868.64939.574249@gargle.gargle.HOWL>
2009-04-14 15:26               ` John W. Linville
2009-06-01 16:35 ` Gábor Stefanik
2009-06-01 16:52   ` Forest Bond
2009-06-08 17:08     ` Olivier Blin
2009-06-08 17:45       ` Forest Bond
2009-06-08 18:01         ` Olivier Blin
  -- strict thread matches above, loose matches on Subject: below --
2009-04-15 19:16 Xose Vazquez Perez
2009-04-15 21:21 ` Greg KH
2009-04-16  5:58   ` Kalle Valo
2009-04-16  8:39     ` Max Filippov
2009-04-16  8:47       ` Kalle Valo
2009-04-16  9:14         ` Max Filippov
2009-04-16  9:52           ` Kalle Valo
2009-04-18 21:18   ` Ivo van Doorn
2009-04-20 13:59     ` John W. Linville
2009-04-21 10:30       ` Ivo Van Doorn
2009-04-21 12:42         ` Ivo Van Doorn
2009-04-21 13:53           ` John W. Linville
2009-04-21 13:52         ` John W. Linville
     [not found] <20090414024610.GA3924@storm.local.network>
2009-04-14  2:53 ` Greg KH

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=20090414113928.GA20470@storm.local.network \
    --to=forest@alittletooquiet.net \
    --cc=Larry.Finger@lwfinger.net \
    --cc=dcbw@redhat.com \
    --cc=greg@kroah.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).