linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Scott Branden <sbranden@broadcom.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Stable <stable@vger.kernel.org>, Andrew Kurn <kurn@sfu.ca>
Subject: New USB ID 2001:3c25
Date: Tue, 02 Jun 2015 21:01:36 -0500	[thread overview]
Message-ID: <556E6000.90402@lwfinger.net> (raw)

Scott,

I see that you added the USB ID in the subject for the DWA-130 device in commit 
ea345c145ff23197eab34d0c4d0c8a93d7bea8c6.

Is there any reason that the new ID should not have been sent to Stable as well, 
or was that an oversight?

Thanks,

Larry

             reply	other threads:[~2015-06-03  2:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03  2:01 Larry Finger [this message]
2015-06-03 17:50 ` New USB ID 2001:3c25 Scott Branden
2015-06-03 17:54   ` Willy Tarreau
2015-06-03 19:01     ` Bjørn Mork
2015-06-03 21:52       ` Willy Tarreau
2015-06-03 17:58   ` Larry Finger
2015-06-04 10:38 ` Luis Henriques

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=556E6000.90402@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=kurn@sfu.ca \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sbranden@broadcom.com \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).