linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] p54usb: Drop duplicate USBID 0xcde:0x0006
Date: Sat, 19 Jun 2010 00:20:45 +0300	[thread overview]
Message-ID: <4C1BE32D.4090403@pardus.org.tr> (raw)
In-Reply-To: <20100618185713.GG6282@tuxdriver.com>

John W. Linville wrote:
> On Thu, Jun 17, 2010 at 01:37:29PM +0300, Ozan Çağlayan wrote:
>> Drop the duplicate USB ID 0xcde:0x0006 which is written at two
>> different places in p54usb.c
>>
>> Signed-off-by: Ozan Çağlayan <ozan@pardus.org.tr>
> 
> Someone beat you to it already...

Ah, no problem ;)

Regards,
Ozan Caglayan

      reply	other threads:[~2010-06-18 21:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-17 10:37 [PATCH] p54usb: Drop duplicate USBID 0xcde:0x0006 Ozan Çağlayan
2010-06-18 18:57 ` John W. Linville
2010-06-18 21:20   ` Ozan Çağlayan [this message]

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=4C1BE32D.4090403@pardus.org.tr \
    --to=ozan@pardus.org.tr \
    --cc=linux-kernel@vger.kernel.org \
    --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).