All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rehas Sachdeva <aquannie@gmail.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: outreachy-kernel@googlegroups.com, Lior Dotan <liodot@gmail.com>,
	Christopher Harrer <charrer@alacritech.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [Outreachy kernel] [PATCH 1/5] staging: slicoss: Fix alignment with open parentheses
Date: Fri, 16 Sep 2016 00:58:48 +0530	[thread overview]
Message-ID: <20160915192848.GA4742@toblerone> (raw)
In-Reply-To: <alpine.DEB.2.10.1609152118560.3364@hadrien>

On Thu, Sep 15, 2016 at 09:20:12PM +0200, Julia Lawall wrote:
> 
> 
> On Fri, 16 Sep 2016, Rehas Sachdeva wrote:
> 
> > Align statements following a line with open parentheses to start after the '('.
> > Issue detected by checkpatch.pl.
> >
> > Signed-off-by: Rehas Sachdeva <aquannie@gmail.com>
> > ---
> >  drivers/staging/slicoss/slicoss.c | 28 ++++++++++++++--------------
> >  1 file changed, 14 insertions(+), 14 deletions(-)
> >
> > diff --git a/drivers/staging/slicoss/slicoss.c b/drivers/staging/slicoss/slicoss.c
> > index 21280a3..6bfb7a8 100644
> > --- a/drivers/staging/slicoss/slicoss.c
> > +++ b/drivers/staging/slicoss/slicoss.c
> > @@ -191,7 +191,7 @@ static void slic_timer_ping(ulong dev)
> >   *
> >   */
> >  static void slic_link_config(struct adapter *adapter,
> > -		      u32 linkspeed, u32 linkduplex)
> > +			     u32 linkspeed, u32 linkduplex)
> >  {
> >  	u32 speed;
> >  	u32 duplex;
> > @@ -707,7 +707,7 @@ static void slic_config_clear(struct adapter *adapter)
> >  }
> >
> >  static bool slic_mac_filter(struct adapter *adapter,
> > -			struct ether_header *ether_frame)
> > +			    struct ether_header *ether_frame)
> >  {
> >  	struct net_device *netdev = adapter->netdev;
> >  	u32 opts = adapter->macopts;
> > @@ -830,10 +830,10 @@ static void slic_timer_load_check(ulong cardaddr)
> >  }
> >
> >  static int slic_upr_queue_request(struct adapter *adapter,
> > -			   u32 upr_request,
> > -			   u32 upr_data,
> > -			   u32 upr_data_h,
> > -			   u32 upr_buffer, u32 upr_buffer_h)
> > +				  u32 upr_request,
> > +				  u32 upr_data,
> > +				  u32 upr_data_h,
> > +				  u32 upr_buffer, u32 upr_buffer_h)
> 
> Maybe you could put a few more arguments on the same line.  For example,
> since upr_buffer and upr_buffer_h are already on the same line, maybe you
> could do the same with upr_data and upr_data_h.
>

I see. I'll make the changes right away. Thanks for pointing out.

Rehas

> >  {
> >  	struct slic_upr *upr;
> >  	struct slic_upr *uprqueue;
> > @@ -899,19 +899,19 @@ static void slic_upr_start(struct adapter *adapter)
> >  }
> >
> >  static int slic_upr_request(struct adapter *adapter,
> > -		     u32 upr_request,
> > -		     u32 upr_data,
> > -		     u32 upr_data_h,
> > -		     u32 upr_buffer, u32 upr_buffer_h)
> > +			    u32 upr_request,
> > +			    u32 upr_data,
> > +			    u32 upr_data_h,
> > +			    u32 upr_buffer, u32 upr_buffer_h)
> 
> Likewise here.
> 
> julia
> 
> 
> >  {
> >  	unsigned long flags;
> >  	int rc;
> >
> >  	spin_lock_irqsave(&adapter->upr_lock, flags);
> >  	rc = slic_upr_queue_request(adapter,
> > -					upr_request,
> > -					upr_data,
> > -					upr_data_h, upr_buffer, upr_buffer_h);
> > +				    upr_request,
> > +				    upr_data,
> > +				    upr_data_h, upr_buffer, upr_buffer_h);
> >  	if (rc)
> >  		goto err_unlock_irq;
> >
> > @@ -1421,7 +1421,7 @@ retry:
> >  }
> >
> >  static void slic_cmdq_putdone_irq(struct adapter *adapter,
> > -				struct slic_hostcmd *cmd)
> > +				  struct slic_hostcmd *cmd)
> >  {
> >  	struct slic_cmdqueue *cmdq = &adapter->cmdq_done;
> >
> > --
> > 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/a0e1623587ce0b842607142663aa65d7871245cc.1473966683.git.aquannie%40gmail.com.
> > For more options, visit https://groups.google.com/d/optout.
> >


  reply	other threads:[~2016-09-15 19:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-15 19:13 [PATCH 0/5] staging: slicoss: Fix multiple checkpatch warnings Rehas Sachdeva
2016-09-15 19:14 ` [PATCH 1/5] staging: slicoss: Fix alignment with open parentheses Rehas Sachdeva
2016-09-15 19:20   ` [Outreachy kernel] " Julia Lawall
2016-09-15 19:28     ` Rehas Sachdeva [this message]
2016-09-15 19:14 ` [PATCH 2/5] staging: slicoss: Remove blank lines before & after braces Rehas Sachdeva
2016-09-15 19:15 ` [PATCH 3/5] staging: slicoss: Add {} to an arm of if-else Rehas Sachdeva
2016-09-16  7:54   ` [Outreachy kernel] " Greg Kroah-Hartman
2016-09-15 19:15 ` [PATCH 4/5] staging: slicoss: Remove unnecessary braces {} Rehas Sachdeva
2016-09-15 19:15 ` [PATCH 5/5] staging: slicoss: Remove unnecessary blank line Rehas Sachdeva

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=20160915192848.GA4742@toblerone \
    --to=aquannie@gmail.com \
    --cc=charrer@alacritech.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=julia.lawall@lip6.fr \
    --cc=liodot@gmail.com \
    --cc=outreachy-kernel@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.