From: Julia Lawall <julia.lawall@lip6.fr>
To: Luca Coelho <luca@coelho.fi>
Cc: cocci@systeme.lip6.fr, backports@vger.kernel.org
Subject: Re: [Cocci] Finding and replacing a struct inside another struct
Date: Wed, 22 Aug 2018 06:54:16 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.21.1808220653240.2365@hadrien> (raw)
In-Reply-To: <040d643bff98456efb34f1c4987a5e9e6ed0b93a.camel@coelho.fi>
On Wed, 22 Aug 2018, Luca Coelho wrote:
> On Wed, 2018-08-22 at 12:38 +0300, Luca Coelho wrote:
> > On Wed, 2018-08-22 at 12:30 +0300, Luca Coelho wrote:
> > > Hi,
> > >
> > > I need some help again. :)
> > >
> > > I have a struct (cfg80211_crypto_settings) that contains a new
> > > element
> > > that I want to substitute for a function call
> > > (cfg_control_port_over_nl80211). But this struct appears inside
> > > another struct.
> > >
> > > So I tried this:
> > >
> > > First I try to find a struct that contains the struct I want (with
> > > the
> > > @parent_child@ rule):
> > >
> > > @parent_child@
> > > identifier child;
> > > identifier parent_type;
> > > @@
> > > struct parent_type
> > > {
> > > ...
> > > struct cfg80211_crypto_settings child;
> > > ...
> > > }
>
> Unfortunately it seems that the parent struct doesn't really match with
> this. I guess I'll have to hardcode the parent struct as well.
Is this a Coccinelle problem, or is the code just not organized as you
would like. If it is a Coccinelle problem, please send the source code as
well.
thanks,
julia
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2018-08-22 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 9:30 Finding and replacing a struct inside another struct Luca Coelho
2018-08-22 9:38 ` Luca Coelho
2018-08-22 10:20 ` Luca Coelho
2018-08-22 10:54 ` Julia Lawall [this message]
2018-08-22 10:52 ` [Cocci] " Julia Lawall
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=alpine.DEB.2.21.1808220653240.2365@hadrien \
--to=julia.lawall@lip6.fr \
--cc=backports@vger.kernel.org \
--cc=cocci@systeme.lip6.fr \
--cc=luca@coelho.fi \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).