From: Ben Hutchings <bhutchings@solarflare.com>
To: Kevin Curtis <Kevin.Curtis@farsite.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"Dermot Smith" <dermot.smith@farsite.com>
Subject: Re: [PATCH 001/007] WAN Drivers: Update farsync driver and introduce fsflex driver
Date: Wed, 18 Sep 2013 16:23:48 +0100 [thread overview]
Message-ID: <1379517828.1522.10.camel@bwh-desktop.uk.level5networks.com> (raw)
In-Reply-To: <E603DC592C92B54A89CEF6B0919A0B1CAAAA787DA0@SOLO.hq.farsitecommunications.com>
Don't use the same subject line for all your patches. This will be the
summary of the change in git and it needs to say what the individual
change does.
On Wed, 2013-09-18 at 11:11 +0100, Kevin Curtis wrote:
> Farsite Communications FarSync driver update
>
> Patch 1 of 7
>
> Add new FarSite PCI ID's to the pci_ids.h file
This is unnecessary unless they will be used in multiple drivers.
Ben.
> Signed-off-by: Kevin Curtis <kevin.curtis@farsite.com>
>
> ---
>
> diff -uprN -X linux-3.10.1/Documentation/dontdiff linux-3.10.1/include/linux/pci_ids.h linux-3.10.1_new/include/linux/pci_ids.h
> --- linux-3.10.1/include/linux/pci_ids.h 2013-07-13 19:42:41.000000000 +0100
> +++ linux-3.10.1_new/include/linux/pci_ids.h 2013-07-26 11:18:39.821065185 +0100
> @@ -2284,6 +2284,14 @@
> #define PCI_DEVICE_ID_FARSITE_T4U 0x0640
> #define PCI_DEVICE_ID_FARSITE_TE1 0x1610
> #define PCI_DEVICE_ID_FARSITE_TE1C 0x1612
> +#define PCI_DEVICE_ID_FARSITE_DSL_S1 0x2610
> +#define PCI_DEVICE_ID_FARSITE_T4E 0x3640
> +#define PCI_DEVICE_ID_FARSITE_T4UE 0x4640
> +#define PCI_DEVICE_ID_FARSITE_T2UE 0x4620
> +#define PCI_DEVICE_ID_FARSITE_T2U_PMC 0x6620
> +#define PCI_DEVICE_ID_FARSITE_T2Ee 0x5621
> +#define PCI_DEVICE_ID_FARSITE_T4Ee 0x5641
> +
>
> #define PCI_VENDOR_ID_ARIMA 0x161f
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
prev parent reply other threads:[~2013-09-18 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 10:11 [PATCH 001/007] WAN Drivers: Update farsync driver and introduce fsflex driver Kevin Curtis
2013-09-18 15:23 ` Ben Hutchings [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=1379517828.1522.10.camel@bwh-desktop.uk.level5networks.com \
--to=bhutchings@solarflare.com \
--cc=Kevin.Curtis@farsite.com \
--cc=dermot.smith@farsite.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox