From: Julia Lawall <julia.lawall@lip6.fr>
To: "Markus Böhme" <markus.boehme@mailbox.org>
Cc: Nadim almas <nadim.902@gmail.com>,
gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
mmarek@suse.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 32/32] Staging/octeon-usb/octeon-hcd.c: Compression of lines for immediate return This patch compresses two lines in to a single line in file octeon-hcd.c
Date: Sat, 23 Jul 2016 23:10:42 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.10.1607232308150.3027@hadrien> (raw)
In-Reply-To: <13fa9fa8-0bdd-f001-19dc-fd44a1efffa4@mailbox.org>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 3106 bytes --]
On Sat, 23 Jul 2016, Markus Böhme wrote:
> Nadim,
>
> several points stand out in your patch:
>
> On 07/22/2016 12:17 PM, Nadim almas wrote:
> > if immediate return statement is found. It also removes variable
> > bytes_written as
> > it is no longer needed.
> >
> > It is done using script Coccinelle. And coccinelle uses following
> > semantic
> > patch for this compression function:
> >
> > @@
> > expression ret;
> > identifier f;
> > @@
> >
> > -ret =
> > +return
> > f(...);
> > -return ret;
>
> The commit message is malformed. Start a new paragraph for the longer
> description of what you are doing after the short one.
>
> >
> > Signed-off-by: Nadim Almas<nadim.902@gmail.com>
> > Acked-by: Julia Lawall <julia.lawall@lip6.fr>
>
> If Julia acked this patch she probably should be copied on this mail.
No, I haven't seen it... And I don't think the above semantic patch
should have made these changes.
julia
>
> > ---
> > Makefile | 2 +-
> > drivers/staging/octeon-usb/octeon-hcd.c | 16 ++++++++--------
> > 2 files changed, 9 insertions(+), 9 deletions(-)
> >
> > diff --git a/Makefile b/Makefile
> > index 4fb6bea..3d9d77a6 100644
> > --- a/Makefile
> > +++ b/Makefile
> > @@ -1,7 +1,7 @@
> > VERSION = 4
> > PATCHLEVEL = 7
> > SUBLEVEL = 0
> > -EXTRAVERSION = -rc4
> > +EXTRAVERSION = -eudyptula-rc4
>
> No need to change this.
>
> > NAME = Psychotic Stoned Sheep
> >
> > # *DOCUMENTATION*
> > diff --git a/drivers/staging/octeon-usb/octeon-hcd.c b/drivers/staging/octeon-usb/octeon-hcd.c
> > index 17442b3..b801c8a 100644
> > --- a/drivers/staging/octeon-usb/octeon-hcd.c
> > +++ b/drivers/staging/octeon-usb/octeon-hcd.c
> > @@ -508,15 +508,15 @@ static int octeon_map_urb_for_dma(struct usb_hcd *hcd, struct urb *urb,
> > {
> > int ret;
> >
> > - ret = octeon_alloc_temp_buffer(urb, mem_flags);
> > - if (ret)
> > - return ret;
> > +
> > + if (octeon_alloc_temp_buffer(urb, mem_flags))
> > + return octeon_alloc_temp_buffer(urb, mem_flags);
>
> This cannot possibly be correct! You are calling a function with side
> effects twice. The first call in the condition might fail while the call
> in the return statement might succeed, never minding the wastefulness of
> two identical calls. Besides, the original code here seems fine to me.
>
> >
> > - ret = usb_hcd_map_urb_for_dma(hcd, urb, mem_flags);
> > - if (ret)
> > +
> > + if (usb_hcd_map_urb_for_dma(hcd, urb, mem_flags))
> > octeon_free_temp_buffer(urb);
> >
> > - return ret;
> > + return usb_hcd_map_urb_for_dma(hcd, urb, mem_flags);
> > }
>
> Same here.
>
> >
> > /**
> > @@ -542,8 +542,8 @@ static void octeon_unmap_urb_for_dma(struct usb_hcd *hcd, struct urb *urb)
> > */
> > static inline u32 cvmx_usb_read_csr32(struct octeon_hcd *usb, u64 address)
> > {
> > - u32 result = cvmx_read64_uint32(address ^ 4);
> > - return result;
> > +
> > + return cvmx_read64_uint32(address ^ 4);
> > }
> >
> > /**
> >
>
> This change looks fine, though.
>
> Automatically generating patches does not free you from validating each
> of them manually.
>
> Regards,
> Markus
>
prev parent reply other threads:[~2016-07-23 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 10:17 Nadim almas
2016-07-23 21:02 ` Markus Böhme
2016-07-23 21:10 ` 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.10.1607232308150.3027@hadrien \
--to=julia.lawall@lip6.fr \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.boehme@mailbox.org \
--cc=mmarek@suse.com \
--cc=nadim.902@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
all inboxes | Powered by JetHome®