netdev - Re: [PATCH] Use dev_port for the ID of a network device.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140701122547.GA1204@oc0268524204.ibm.com>
Date:	Tue, 1 Jul 2014 09:25:47 -0300
From:	Thadeu Lima de Souza Cascardo <cascardo@...ux.vnet.ibm.com>
To:	Bjørn Mork <bjorn@...k.no>
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH] Use dev_port for the ID of a network device.

On Tue, Jul 01, 2014 at 09:40:57AM +0200, Bjørn Mork wrote:
> FYI: I just got this back from systemd-devel-owner@...ts.freedesktop.org :
> 
>  Please subscribe to this mailing list, all non-subscriber emails are
>  automatically rejected by the server.
>  
>  If you actually don't want to receive the mails, stay subscribed but
>  just disable the delivery in the mailman web interface. You will still
>  be able to send messages that way.
>  
>  We were unable to cope with the amount of SPAM, and the moderation
>  queue was not actually moderated by anybody, so rejection seemed more
>  appropriate than no answer and no delivery to the list.
>  
>  Thanks for understanding.
> 
> 
> Please do not crosspost between netdev and closed mailing lists.  It
> splits the followup threads between those who are inside the closed
> community and those who are not.
> 
> I've removed systemd-devel from the CC list of this email.
> 
> Thanks for understanding.
> 
> 
> Bjørn
> 

Not sure how, but my patch got through, and I don't recall being
subscribed, so I thought it was a an open list. Anyway, it's something
that I considered important to be considered by the two communities.

Kay raises up the matter of still using dev_id. Since we had drivers
that used that in the past, should we use it as a fallback for older
kernels where dev_port is not there?

Regards.
Cascardo.

--
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