From: Julia Lawall <julia.lawall@lip6.fr>
To: SIMRAN SINGHAL <singhalsimran0@gmail.com>
Cc: Julia Lawall <julia.lawall@lip6.fr>,
Lars-Peter Clausen <lars@metafoo.de>,
Michael.Hennerich@analog.com, Jonathan Cameron <jic23@kernel.org>,
knaack.h@gmx.de, Greg KH <gregkh@linuxfoundation.org>,
linux-iio@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH 00/10] staging: iio: Remove exceptional & on functions name
Date: Sat, 11 Mar 2017 12:40:34 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1703111237320.2202@hadrien> (raw)
In-Reply-To: <CALrZqyMcYgzH27n4gnRH5ydMajNJNs2n_n86hvQspeOMk0WoNg@mail.gmail.com>
On Sat, 11 Mar 2017, SIMRAN SINGHAL wrote:
> On Sat, Mar 11, 2017 at 2:57 PM, Julia Lawall <julia.lawall@lip6.fr> wrote:
> >
> >
> > On Sat, 11 Mar 2017, SIMRAN SINGHAL wrote:
> >
> >> On Sat, Mar 11, 2017 at 12:12 PM, Julia Lawall <julia.lawall@lip6.fr> wrote:
> >> >
> >> >
> >> > On Sat, 11 Mar 2017, simran singhal wrote:
> >> >
> >> >> This patch-series removes exceptional & on functions name.
> >> >
> >> > The semantic patch shown does nothing to check that the use of & is
> >> > exception in the given file. It just removes all the & on function names.
> >> >
> >> yes, I used this semantic patch only for only finding the functions with &
> >> and then I find out this drivers and use semantic patch for removing &.
> >
> > The commit message should be written with respect to what was actually
> > done, and not copied from a patch that actually did something else. The
> > original semantic patch, that was probably only put in the cover letter,
> > actually checked if the file mostly used function pointers in a particular
> > way.
> >
> Julia, so what should I do?
> I should not include this semantic patch as it does not check that that the use
> of & is exception in the given file.
> OR
> As I did it manually so I should mention this.
If you checked it manually, just mention that. I don't have the actual
patches handy any more, but you could also say something like:
Remove & from function pointers to conform to the style found elsewhere in
the file. Done using the following semantic patch.
This would be ok if the included semantic patch makes the change. It
doesn't suggest that the semantic patch checkked for the excpeptionality.
julia
>
> > julia
> >
> >>
> >> > julia
> >> >
> >> >>
> >> >> simran singhal (10):
> >> >> staging: iio: ad7192: Remove exceptional & on function name
> >> >> staging: iio: ad7780: Remove exceptional & on function name
> >> >> staging: iio: cdc: ad7746: Remove exceptional & on function name
> >> >> staging: iio: cdc: ad7152: Remove exceptional & on function name
> >> >> staging: iio: adis16240: Remove exceptional & on function name
> >> >> staging: iio: adis16201: Remove exceptional & on function name
> >> >> staging: iio: adis16209: Remove exceptional & on function name
> >> >> staging: iio: adis16203: Remove exceptional & on function name
> >> >> staging: iio: resolver: Remove exceptional & on function name
> >> >> staging: iio: gyro: Remove exceptional & on function name
> >> >>
> >> >> drivers/staging/iio/accel/adis16201.c | 4 ++--
> >> >> drivers/staging/iio/accel/adis16203.c | 4 ++--
> >> >> drivers/staging/iio/accel/adis16209.c | 4 ++--
> >> >> drivers/staging/iio/accel/adis16240.c | 4 ++--
> >> >> drivers/staging/iio/adc/ad7192.c | 12 ++++++------
> >> >> drivers/staging/iio/adc/ad7780.c | 2 +-
> >> >> drivers/staging/iio/cdc/ad7152.c | 6 +++---
> >> >> drivers/staging/iio/cdc/ad7746.c | 4 ++--
> >> >> drivers/staging/iio/gyro/adis16060_core.c | 2 +-
> >> >> drivers/staging/iio/resolver/ad2s1200.c | 2 +-
> >> >> drivers/staging/iio/resolver/ad2s90.c | 2 +-
> >> >> 11 files changed, 23 insertions(+), 23 deletions(-)
> >> >>
> >> >> --
> >> >> 2.7.4
> >> >>
> >> >> --
> >> >> 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/1489203401-17518-1-git-send-email-singhalsimran0%40gmail.com.
> >> >> For more options, visit https://groups.google.com/d/optout.
> >> >>
> >>
> >> --
> >> 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/CALrZqyODTiF%2BgdwwYnmL1W1oi-R0u2rM4c40jb5iWXFxJpfdJw%40mail.gmail.com.
> >> For more options, visit https://groups.google.com/d/optout.
> >>
>
prev parent reply other threads:[~2017-03-11 11:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-11 3:36 simran singhal
2017-03-11 3:36 ` [PATCH 01/10] staging: iio: ad7192: Remove exceptional & on function name simran singhal
2017-03-11 3:36 ` [PATCH 02/10] staging: iio: ad7780: " simran singhal
2017-03-11 3:36 ` [PATCH 03/10] staging: iio: cdc: ad7746: " simran singhal
2017-03-11 3:36 ` [PATCH 04/10] staging: iio: cdc: ad7152: " simran singhal
2017-03-11 3:36 ` [PATCH 05/10] staging: iio: adis16240: " simran singhal
2017-03-11 3:36 ` [PATCH 06/10] staging: iio: adis16201: " simran singhal
2017-03-11 3:36 ` [PATCH 07/10] staging: iio: adis16209: " simran singhal
2017-03-11 3:36 ` [PATCH 08/10] staging: iio: adis16203: " simran singhal
2017-03-11 3:36 ` [PATCH 09/10] staging: iio: resolver: " simran singhal
2017-03-11 3:36 ` [PATCH 10/10] staging: iio: gyro: " simran singhal
2017-03-11 6:42 ` [Outreachy kernel] [PATCH 00/10] staging: iio: Remove exceptional & on functions name Julia Lawall
2017-03-11 9:19 ` SIMRAN SINGHAL
2017-03-11 9:27 ` Julia Lawall
2017-03-11 11:32 ` SIMRAN SINGHAL
2017-03-11 11:40 ` 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.1703111237320.2202@hadrien \
--to=julia.lawall@lip6.fr \
--cc=Michael.Hennerich@analog.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--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=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
Powered by JetHome