All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bjørn Mork" <bjorn@mork.no>
To: David Miller <davem@davemloft.net>
Cc: freddy@asix.com.tw, netdev@vger.kernel.org,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	Keith Packard <keithp@keithp.com>
Subject: Re: [PATCH 1/1] AX88179_178A: Add VID:DID for Lenovo OneLinkDock Gigabit LAN
Date: Wed, 26 Feb 2014 22:44:18 +0100	[thread overview]
Message-ID: <87fvn57dn1.fsf@nemi.mork.no> (raw)
In-Reply-To: <20140226.161659.2024676575146527914.davem@davemloft.net> (David Miller's message of "Wed, 26 Feb 2014 16:16:59 -0500 (EST)")

David Miller <davem@davemloft.net> writes:
> From: Bjørn Mork <bjorn@mork.no>
>
>> No, sorry for being confusing.  The patch is fine.  But Keith sent it
>> first...
>
> Did I apply Keith's patch?

No, you didn't.  And when I went looking at it now, I see why: It was
posted to linux-usb and linux-kernel but not to netdev:
http://www.kernelhub.org/?msg=420289&p=2

> If not, should I apply it instead?

The patches are identical except for the author and a minor difference
in the device description string. 

It doesn't matter to me which patch you apply, and I absolutely don't
think it's my place to tell you which patches to apply or not :-)



Bjørn

  reply	other threads:[~2014-02-26 21:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26  8:54 [PATCH 1/1] AX88179_178A: Add VID:DID for Lenovo OneLinkDock Gigabit LAN freddy
2014-02-26 12:13 ` Bjørn Mork
2014-02-26 20:48   ` David Miller
2014-02-26 21:14     ` Bjørn Mork
2014-02-26 21:16       ` David Miller
2014-02-26 21:44         ` Bjørn Mork [this message]
2014-02-26 22:02           ` David Miller
2014-02-26 22:23           ` Keith Packard
2014-02-26 22:37             ` Joe Perches
2014-02-26 23:04               ` Keith Packard

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=87fvn57dn1.fsf@nemi.mork.no \
    --to=bjorn@mork.no \
    --cc=davem@davemloft.net \
    --cc=freddy@asix.com.tw \
    --cc=keithp@keithp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.