netdev - Re: [patch 0/1][RFC] add a private field to the sock structure

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <20070830.224049.35665219.davem@davemloft.net>
Date:	Thu, 30 Aug 2007 22:40:49 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	acme@...stprotocols.net
Cc:	dlezcano@...ibm.com, netdev@...r.kernel.org, ralf@...ux-mips.org
Subject: Re: [patch 0/1][RFC] add a private field to the sock structure

From: Arnaldo Carvalho de Melo <acme@...stprotocols.net>
Date: Wed, 29 Aug 2007 16:18:31 -0300

> Nah, it still there, sk_protinfo, its just ax25 that uses it
> (nudge(Ralf)). How do we state that a struct field is deprecated and
> will be removed soon(tm)?

You get rid of all the in-tree users and then just kill it :)

More seriously, I don't think we need a deprecation schedule
for a struct member, either it's not used in-tree anymore or
it isn't.  We'll go crazy with any other policy and it's
difficult enough shrinking these things :-)
-
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