From: Julia Lawall <julia.lawall@lip6.fr>
To: SIMRAN SINGHAL <singhalsimran0@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [Outreachy kernel] Re: [PATCH] iio: adc: max1363: constify attribute_group structures
Date: Wed, 29 Mar 2017 23:31:51 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1703292331160.2146@hadrien> (raw)
In-Reply-To: <CALrZqyOPVDA+4n56d3c+jZRsiaQ52vYEjA+Or1j8Z2LNgi58OQ@mail.gmail.com>
On Thu, 30 Mar 2017, SIMRAN SINGHAL wrote:
> On Thu, Mar 30, 2017 at 2:41 AM, Jonathan Cameron <jic23@kernel.org> wrote:
> > On 28/03/17 21:15, simran singhal wrote:
> >> Check for attribute_group structures that are only stored in the
> >> event_attrs filed of iio_info structure. As the event_attrs field of
> >> iio_info structures is constant, so these attribute_group structures can
> >> also be declared constant. Done using coccinelle:
> >>
> >> @r1 disable optional_qualifier @
> >> identifier i;
> >> position p;
> >> @@
> >> static struct attribute_group i@p = {...};
> >>
> >> @ok1@
> >> identifier r1.i;
> >> position p;
> >> struct iio_info x;
> >> @@
> >> x.event_attrs=&i@p;
> >>
> >> @bad@
> >> position p!={r1.p,ok1.p};
> >> identifier r1.i;
> >> @@
> >> i@p
> >>
> >> @depends on !bad disable optional_qualifier@
> >> identifier r1.i;
> >> @@
> >> static
> >> +const
> >> struct attribute_group i={...};
> >>
> >> @depends on !bad disable optional_qualifier@
> >> identifier r1.i;
> >> @@
> >> +const
> >> struct attribute_group i;
> >>
> >> File size before:
> >> text data bss dec hex filename
> >> 36951 448 0 37399 9217 drivers/iio/adc/max1363.o
> >>
> >> File size after:
> >> text data bss dec hex filename
> >> 37015 384 0 37399 9217 drivers/iio/adc/max1363.o
> >>
> >> Signed-off-by: simran singhal <singhalsimran0@gmail.com>
> > Applied to the togreg branch of iio.git and pushed out as testing for
> > the autobuilders to play with it.
> >
>
> But my tree is up-to-date and I also test it before sending.
One never knows...
julia
>
> > Thanks,
> >
> > Jonathan
> >> ---
> >> drivers/iio/adc/max1363.c | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/drivers/iio/adc/max1363.c b/drivers/iio/adc/max1363.c
> >> index c6c12fe..80eada4 100644
> >> --- a/drivers/iio/adc/max1363.c
> >> +++ b/drivers/iio/adc/max1363.c
> >> @@ -1007,7 +1007,7 @@ static struct attribute *max1363_event_attributes[] = {
> >> NULL,
> >> };
> >>
> >> -static struct attribute_group max1363_event_attribute_group = {
> >> +static const struct attribute_group max1363_event_attribute_group = {
> >> .attrs = max1363_event_attributes,
> >> };
> >>
> >>
> >
>
> --
> You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> To post to this group, send email to outreachy-kernel@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/CALrZqyOPVDA%2B4n56d3c%2BjZRsiaQ52vYEjA%2BOr1j8Z2LNgi58OQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>
prev parent reply other threads:[~2017-03-29 21:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 20:15 [PATCH] iio: adc: max1363: constify attribute_group structures simran singhal
2017-03-29 21:11 ` Jonathan Cameron
2017-03-29 21:28 ` SIMRAN SINGHAL
2017-03-29 21:31 ` Julia Lawall [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=alpine.DEB.2.20.1703292331160.2146@hadrien \
--to=julia.lawall@lip6.fr \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=pmeerw@pmeerw.net \
--cc=singhalsimran0@gmail.com \
/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