netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gerard DeRose <jason@system76.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, benpope81@gmail.com
Subject: Re: [PATCH] ethernet/atheros/alx: add Killer E2400 device ID
Date: Wed, 18 Nov 2015 14:48:41 -0700	[thread overview]
Message-ID: <564CF239.9030309@system76.com> (raw)
In-Reply-To: <20151118.150642.1281703908211053053.davem@davemloft.net>

On 11/18/2015 01:06 PM, David Miller wrote:
> From: Jason Gerard DeRose <jason@system76.com>
> Date: Tue, 17 Nov 2015 18:21:07 -0700
>
>> From: Ben Pope <benpope81@gmail.com>
>>
>> This patch adds the PCI device ID (0xe0a1) and alx_pci_tbl entry for the
>> Killer E2400 Ethernet controller, modeled after the Killer E2200
>> controller support (0xe091) already present in the alx driver.
>>
>> This patch was originally authored by Ben Pope, but it got held up by
>> issues in the commit message, so I'm resubmitting it on his behalf.
>>
>> I've extensively used a kernel with this patch on a System76 serw9
>> laptop and am quite confident it works well (at least on the hardware I
>> have available for testing).
>>
>> Note that as a favor to System76, Ubuntu has been carrying this as a
>> sauce patch in their 4.2 based Wily kernel, which presumably has given
>> it real-world testing on other E2400 equipped hardware (I don't know of
>> any Ubuntu kernel bugs filed about it):
>>
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1498633
>>
>> Signed-off-by: Jason Gerard DeRose <jason@system76.com>
>
> Applied.

Much thanks!

      reply	other threads:[~2015-11-18 21:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-18  1:21 [PATCH] ethernet/atheros/alx: add Killer E2400 device ID Jason Gerard DeRose
2015-11-18 14:01 ` Sergei Shtylyov
2015-11-18 14:52   ` Jason Gerard DeRose
2015-11-18 17:47     ` Sergei Shtylyov
2015-11-18 18:15       ` Jason Gerard DeRose
2015-11-18 14:28 ` Ben Pope
2015-11-18 20:06 ` David Miller
2015-11-18 21:48   ` Jason Gerard DeRose [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=564CF239.9030309@system76.com \
    --to=jason@system76.com \
    --cc=benpope81@gmail.com \
    --cc=davem@davemloft.net \
    --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 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).