From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Owen Lin <olin@rivetnetworks.com>,
"johannes@sipsolutions.net" <johannes@sipsolutions.net>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH 1/1] net: add killer e2400 device id
Date: Tue, 24 Nov 2015 15:49:14 +0300 [thread overview]
Message-ID: <56545CCA.9000606@cogentembedded.com> (raw)
In-Reply-To: <BN3PR0401MB14572E9C2572B4C1FFFF881DC0060@BN3PR0401MB1457.namprd04.prod.outlook.com>
Hello.
On 11/24/2015 4:18 AM, Owen Lin wrote:
> Add Killer E2400 device ID in alx driver.
>
> Signed-off-by: Owen Lin olin@rivetnetworks.com
>
> --------------------------------------------------------------------------------
> diff -uprN alx_orig/main.c alx/main.c
The patch should be applicable with the -p1 option.
> --- alx_orig/main.c Mon Sep 7 13:00:58 2015
> +++ alx/main.c Mon Sep 7 14:47:03 2015
> @@ -1537,6 +1537,7 @@ static const struct pci_device_id alx_pc
> { PCI_VDEVICE(ATTANSIC, ALX_DEV_ID_AR8162),
> .driver_data = ALX_DEV_QUIRK_MSI_INTX_DISABLE_BUG },
> { PCI_VDEVICE(ATTANSIC, ALX_DEV_ID_AR8171) },
> + { PCI_VDEVICE(ATTANSIC, ALX_DEV_ID_E2400) },
> { PCI_VDEVICE(ATTANSIC, ALX_DEV_ID_AR8172) },
> {}
> };
> diff -uprN alx_orig/reg.h alx/reg.h
> --- alx_orig/reg.h Mon Sep 7 13:00:58 2015
> +++ alx/reg.h Mon Sep 7 14:46:16 2015
> @@ -39,6 +39,7 @@
> #define ALX_DEV_ID_E2200 0xe091
> #define ALX_DEV_ID_AR8162 0x1090
> #define ALX_DEV_ID_AR8171 0x10A1
> +#define ALX_DEV_ID_E2400 0xe0A1
Either all upper case (which seem to follow what the other IDs have) or
all lower case.
> #define ALX_DEV_ID_AR8172 0x10A0
>
> /* rev definition,
MBR, Sergei
next prev parent reply other threads:[~2015-11-24 12:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 1:18 [PATCH 1/1] net: add killer e2400 device id Owen Lin
2015-11-24 12:49 ` Sergei Shtylyov [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-25 0:20 Owen Lin
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=56545CCA.9000606@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=johannes@sipsolutions.net \
--cc=netdev@vger.kernel.org \
--cc=olin@rivetnetworks.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 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.