From: David Miller <davem@davemloft.net>
To: bhutchings@solarflare.com
Cc: netdev@vger.kernel.org, linux-net-drivers@solarflare.com
Subject: Re: [PATCH] sfc: Store port number in net_device::dev_id
Date: Thu, 03 Jun 2010 03:29:47 -0700 (PDT) [thread overview]
Message-ID: <20100603.032947.10563469.davem@davemloft.net> (raw)
In-Reply-To: <1275511200.2115.23.camel@achroite.uk.solarflarecom.com>
From: Ben Hutchings <bhutchings@solarflare.com>
Date: Wed, 02 Jun 2010 21:39:56 +0100
> This exposes the port number to userland through sysfs.
>
> Signed-off-by: Ben Hutchings <bhutchings@solarflare.com>
> ---
> Following on from the earlier discussion of dev_id, here's the necessary
> change for sfc. This depends on commit dd8f61d "sfc: Get port number
> from CS_PORT_NUM, not PCI function number". Please consider including
> both of these in net-2.6.
Both added to net-2.6
prev parent reply other threads:[~2010-06-03 10:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 20:39 [PATCH] sfc: Store port number in net_device::dev_id Ben Hutchings
2010-06-03 2:42 ` David Miller
2010-06-03 10:29 ` David Miller [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=20100603.032947.10563469.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=linux-net-drivers@solarflare.com \
--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).