From: David Miller <davem@davemloft.net>
To: jpirko@redhat.com
Cc: christopher.leech@intel.com, jeffrey.t.kirsher@intel.com,
netdev@vger.kernel.org, gospo@redhat.com,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] netdev: storage address support
Date: Tue, 28 Apr 2009 02:12:49 -0700 (PDT) [thread overview]
Message-ID: <20090428.021249.247190041.davem@davemloft.net> (raw)
In-Reply-To: <20090428083048.GB27798@psychotron.englab.brq.redhat.com>
From: Jiri Pirko <jpirko@redhat.com>
Date: Tue, 28 Apr 2009 10:30:48 +0200
> Tue, Apr 28, 2009 at 03:48:54AM CEST, davem@davemloft.net wrote:
>>From: Chris Leech <christopher.leech@intel.com>
>>Date: Mon, 27 Apr 2009 15:28:00 -0700
>>
>>> Ignoring the issue of intended use for the moment, if an ethernet driver
>>> wanted to advertise several MAC addresses to the system how should it go
>>> about that?
>>
>>Now that's a more interesting question.
>>
>>It seems better to formalize this. It can be an ethtool
>>callback or whatever, but what it should do is return
>>an array of addresses, types, and perhaps even indexes
>>with types.
>
> Well the list of device addresses from my patch can pretty much solve this.
> There can be additional field in struct netdev_hw_addr to store flags to
> identify the mac address type (like primary, lan, san, slave, etc).
>
> I think it would be better to do this in general (in struct net_device) then
> inside each driver exported by ethtool or whatever.
Agreed, can you update your patch to provide such a 'type' tag?
Thanks!
next prev parent reply other threads:[~2009-04-28 9:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 8:03 [PATCH] netdev: storage address support Jeff Kirsher
2009-04-27 10:01 ` David Miller
2009-04-27 22:28 ` Chris Leech
2009-04-28 1:48 ` David Miller
2009-04-28 8:30 ` Jiri Pirko
2009-04-28 9:12 ` David Miller [this message]
2009-04-28 10:18 ` Jiri Pirko
2009-04-28 11:25 ` David Miller
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=20090428.021249.247190041.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=christopher.leech@intel.com \
--cc=gospo@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jpirko@redhat.com \
--cc=linux-scsi@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