From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: David Miller <davem@davemloft.net>
Cc: dlezcano@fr.ibm.com, netdev@vger.kernel.org, ralf@linux-mips.org
Subject: Re: [patch 0/1][RFC] add a private field to the sock structure
Date: Fri, 31 Aug 2007 08:26:20 -0300 [thread overview]
Message-ID: <20070831112620.GA2532@ghostprotocols.net> (raw)
In-Reply-To: <20070830.224049.35665219.davem@davemloft.net>
Em Thu, Aug 30, 2007 at 10:40:49PM -0700, David Miller escreveu:
> From: Arnaldo Carvalho de Melo <acme@ghostprotocols.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 :-)
OK, I think its enough to say to dlezcano that he should avoid using
sk_protinfo, as soon as we do the work on AX.25 sk_protinfo will be
removed.
- Arnaldo
prev parent reply other threads:[~2007-08-31 11:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 16:41 [patch 0/1][RFC] add a private field to the sock structure dlezcano
2007-08-29 16:41 ` [patch 1/1][RFC] " dlezcano
2007-08-29 18:09 ` Christoph Hellwig
2007-08-29 18:23 ` [patch 0/1][RFC] " David Miller
2007-08-29 19:18 ` Arnaldo Carvalho de Melo
2007-08-29 21:15 ` Daniel Lezcano
2007-08-31 5:40 ` David Miller
2007-08-31 11:26 ` Arnaldo Carvalho de Melo [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=20070831112620.GA2532@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=davem@davemloft.net \
--cc=dlezcano@fr.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.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).