public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Kennedy <richard@rsk.demon.co.uk>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>,
	jimdog@northern-indymedia.org
Cc: gregkh@suse.de, jmm@debian.org, mithlesh@linsyssoft.com,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: wlan-ng: Fix 80 character limit warnings Fixed 2  warnings identified by the checkpatch.pl tool which occured due to two lines  of code going over the 80 character limit. Fixed by wrapping the lines.  Signed-off-by: Jim Dog <jimdog@
Date: Tue, 23 Feb 2010 14:35:35 +0000	[thread overview]
Message-ID: <1266935735.2047.5.camel@localhost> (raw)
In-Reply-To: <69e28c911002210706k1a5ae686r76df74a743dcce1c@mail.gmail.com>

On Sun, 2010-02-21 at 16:06 +0100, Gábor Stefanik wrote:

> > +/*
> > +       {PRISM_USB_DEVICE(0x0ace, 0x1201, "ZyDAS ZD1201 Wireless USB Adapter")},
> > +*/
> 
> Why is this even included? We do have support for this in zd1201, and
> I'm pretty sure wlan-ng doesn't actually handle it.
> 
In that case, let's just remove it. It's only clutter and may cause
confusion.
JD do you want to update your patch to get rid of this?

regards
Richard 


  parent reply	other threads:[~2010-02-23 14:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-21 15:06 [PATCH] Staging: wlan-ng: Fix 80 character limit warnings Fixed 2 warnings identified by the checkpatch.pl tool which occured due to two lines of code going over the 80 character limit. Fixed by wrapping the lines. Signed-off-by: Jim Dog <jimdog@ Gábor Stefanik
2010-02-21 15:46 ` Jim Dog
2010-02-23 14:35 ` Richard Kennedy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-02-23 15:37 JimDog

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=1266935735.2047.5.camel@localhost \
    --to=richard@rsk.demon.co.uk \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=jimdog@northern-indymedia.org \
    --cc=jmm@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mithlesh@linsyssoft.com \
    --cc=netrolller.3d@gmail.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