[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1411718885.19443.2.camel@joe-AO725>
Date: Fri, 26 Sep 2014 01:08:05 -0700
From: Joe Perches <joe@...ches.com>
To: Julia Lawall <julia.lawall@...6.fr>
Cc: Eric Dumazet <eric.dumazet@...il.com>,
Eric Dumazet <edumazet@...gle.com>,
"David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org,
Yuchung Cheng <ycheng@...gle.com>,
Neal Cardwell <ncardwell@...gle.com>,
Christoph Paasch <christoph.paasch@...ouvain.be>
Subject: Re: [PATCH v3 net-next 1/3] ipv4: rename ip_options_echo to
__ip_options_echo()
On Fri, 2014-09-26 at 07:29 +0200, Julia Lawall wrote:
> On Thu, 25 Sep 2014, Joe Perches wrote:
> > On Thu, 2014-09-25 at 13:38 -0700, Eric Dumazet wrote:
> > > On Thu, 2014-09-25 at 13:30 -0700, Joe Perches wrote:
[]
> > > > I wonder how much effort, if any, should be made to convert
> > > > struct sk_buff * to const struct sk_buff * where appropriate.
> > > >
> > > > For instance:n
> > > >
> > > > This __ip_options_echo could use const struct sk_buff *skb
> > > > if fib_compute_spec_dst was changed to const struct sk_buff *skb.
> > >
> > > Well, this seems something certainly doable, as a follow up ;)
> >
> > It's doable, but it seems a non-trivial inspection task.
> >
> > I believe coccinelle does not have the ability to automate this.
>
> What are the exact conditions when the change is possible?
>
> I guess something like the value is only used for accessing its fields.
> and is not passed to any other function?
I expect the entire call tree needs to be known
and inspected for modification of fields.
--
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