[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAG-2HqUM6OSM4-4eVO4KuY38KpKiKTM_H6mdb775VXP+YVuUHg@mail.gmail.com>
Date: Tue, 1 Jul 2014 14:45:56 +0200
From: Tom Gundersen <teg@...m.no>
To: Thadeu Lima de Souza Cascardo <cascardo@...ux.vnet.ibm.com>
Cc: Kay Sievers <kay@...y.org>, netdev <netdev@...r.kernel.org>
Subject: Re: [systemd-devel] [PATCH] Use dev_port for the ID of a network device.
On Tue, Jul 1, 2014 at 2:32 PM, Thadeu Lima de Souza Cascardo
<cascardo@...ux.vnet.ibm.com> wrote:
> On Tue, Jul 01, 2014 at 02:33:19AM +0200, Kay Sievers wrote:
>> On Mon, Jun 30, 2014 at 10:36 PM, Thadeu Lima de Souza Cascardo
>> <cascardo@...ux.vnet.ibm.com> wrote:
>> > For network devices on the same PCI function, dev_id should not be used,
>> > since its purpose is for IPv6 support on interfaces with the same MAC
>> > address.
>> >
>> > The new dev_port sysfs attribute should be used when it is found. When
>> > it is not, using dev_id might work.
>>
>> I don't see a problem switching this over, but why would we keep using
>> dev_id if it is not the right thing to use?
>>
>> Kay
>>
>
> Because dev_port has only been introduced into Linux 3.15, and some
> drivers used dev_id before Linux 3.10. It's not an ideal situation, so I
> think it's important to keep some compatibility for the time being. Or
> we could simply drop dev_id, and force everyone to do the right thing
> and backport dev_port support and fix their drivers.
If this fixes a real issue, I guess it would be nice to push the
dev_port stuff to -stable. If it is accepted it would solve the
backwards compatibility problem, and we could just drop dev_id from
udev.
Cheers,
Tom
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists