linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@inria.fr>
To: Aline Santana Cordeiro <alinesantanacordeiro@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org, outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH v3] staging: media: atomisp: pci: Change line break to avoid an open parenthesis at the end of the line
Date: Wed, 21 Apr 2021 15:56:08 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2104211555040.9436@hadrien> (raw)
In-Reply-To: <7aeac7041a6f6d7b3d8563f0d0bf0a4d31f379b0.camel@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4408 bytes --]



On Wed, 21 Apr 2021, Aline Santana Cordeiro wrote:

> Em qua, 2021-04-21 às 15:08 +0200, Julia Lawall escreveu:
> >
> >
> > On Wed, 21 Apr 2021, Aline Santana Cordeiro wrote:
> >
> > > Change line break to avoid an open parenthesis at the end of the
> > > line.
> > > It consequently removed spaces at the start of the subsequent line.
> >
> > The message is hard to understand.  There are a lot of singular
> > nouns, but
> > actually there are two changes.  Which change is being described by
> > the
> > above message?  What does "It" refer to?
> >
> > julia
>
> Checkpatch indicated two problems with this function declaration:
> 1) The line ending with an open parenthesis, and
> 2) The following line - with the function parameters - has spaces in
> its identation.
>
> When I changed the line break to put the function name and its
> parameter in the following line, both checkpath checks were eliminated.
>
> So, the main change was the line break and, also, the line break (it)
> removed the space in the following line.
>
> Is it better to change the message and explain only about the line
> break?

The message should explain about the whole patch.  So if you change two
things, it should be clear that what you are saying covers both of them.

But it seems that Matthew doesn't think that the line break is a good idea
anyway.

julia

>
> Thank you,
> Aline
> >
> >
> > > Both issues detected by checkpatch.pl.
> > >
> > > Signed-off-by: Aline Santana Cordeiro <
> > > alinesantanacordeiro@gmail.com>
> > > ---
> > >
> > > Changes since v2:
> > >  - Insert a space between the function type and pointer
> > >
> > > Changes since v1:
> > >  - Keep the pointer with the function return type
> > >    instead of left it with the function name
> > >
> > >  drivers/staging/media/atomisp/pci/atomisp_cmd.h | 10 +++++-----
> > >  1 file changed, 5 insertions(+), 5 deletions(-)
> > >
> > > diff --git a/drivers/staging/media/atomisp/pci/atomisp_cmd.h
> > > b/drivers/staging/media/atomisp/pci/atomisp_cmd.h
> > > index 1c0d464..639eca3 100644
> > > --- a/drivers/staging/media/atomisp/pci/atomisp_cmd.h
> > > +++ b/drivers/staging/media/atomisp/pci/atomisp_cmd.h
> > > @@ -75,8 +75,8 @@ void atomisp_wdt(struct timer_list *t);
> > >  void atomisp_setup_flash(struct atomisp_sub_device *asd);
> > >  irqreturn_t atomisp_isr(int irq, void *dev);
> > >  irqreturn_t atomisp_isr_thread(int irq, void *isp_ptr);
> > > -const struct atomisp_format_bridge
> > > *get_atomisp_format_bridge_from_mbus(
> > > -    u32 mbus_code);
> > > +const struct atomisp_format_bridge *
> > > +get_atomisp_format_bridge_from_mbus(u32 mbus_code);
> > >  bool atomisp_is_mbuscode_raw(uint32_t code);
> > >  int atomisp_get_frame_pgnr(struct atomisp_device *isp,
> > >                            const struct ia_css_frame *frame, u32
> > > *p_pgnr);
> > > @@ -381,9 +381,9 @@ enum mipi_port_id __get_mipi_port(struct
> > > atomisp_device *isp,
> > >
> > >  bool atomisp_is_vf_pipe(struct atomisp_video_pipe *pipe);
> > >
> > > -void atomisp_apply_css_parameters(
> > > -    struct atomisp_sub_device *asd,
> > > -    struct atomisp_css_params *css_param);
> > > +void atomisp_apply_css_parameters(struct atomisp_sub_device *asd,
> > > +                                 struct atomisp_css_params
> > > *css_param);
> > > +
> > >  void atomisp_free_css_parameters(struct atomisp_css_params
> > > *css_param);
> > >
> > >  void atomisp_handle_parameter_and_buffer(struct atomisp_video_pipe
> > > *pipe);
> > > --
> > > 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 view this discussion on the web visit
> > > https://groups.google.com/d/msgid/outreachy-kernel/20210421123718.GA4597%40focaruja
> > > .
> > >
>
>
> --
> 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 view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/7aeac7041a6f6d7b3d8563f0d0bf0a4d31f379b0.camel%40gmail.com.
>

  reply	other threads:[~2021-04-21 13:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21 12:37 [PATCH v3] staging: media: atomisp: pci: Change line break to avoid an open parenthesis at the end of the line Aline Santana Cordeiro
2021-04-21 13:08 ` [Outreachy kernel] " Julia Lawall
2021-04-21 13:45   ` Aline Santana Cordeiro
2021-04-21 13:56     ` Julia Lawall [this message]
2021-04-21 14:21       ` Aline Santana Cordeiro
2021-04-23  9:21         ` Hans Verkuil
2021-04-24  2:10           ` Aline Santana Cordeiro
2021-04-21 13:15 ` Matthew Wilcox
2021-04-26  9:18   ` Sakari Ailus

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.22.394.2104211555040.9436@hadrien \
    --to=julia.lawall@inria.fr \
    --cc=alinesantanacordeiro@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=mchehab@kernel.org \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=sakari.ailus@linux.intel.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;
as well as URLs for NNTP newsgroup(s).