mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@lip6.fr>
To: Joe Perches <joe@perches.com>
Cc: Arushi Singhal <arushisinghal19971997@gmail.com>,
	gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org, outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] Re: [PATCH 1/2] staging: ks7010: Unnecessary parentheses are removed.
Date: Sun, 19 Feb 2017 20:20:02 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1702192018570.2363@hadrien> (raw)
In-Reply-To: <1487531915.2198.38.camel@perches.com>



On Sun, 19 Feb 2017, Joe Perches wrote:

> On Sun, 2017-02-19 at 19:58 +0100, Julia Lawall wrote:
> > On Sun, 19 Feb 2017, Joe Perches wrote:
> > > On Sun, 2017-02-19 at 23:56 +0530, Arushi Singhal wrote:
> > > > Unnecessary parentheses should be avoided as reported by checkpatch.pl.
> > > > Remove unnecessary parentheses, as reported by checkpatch as are nicer
> > > > to read.For example:-
> > > > It's often nicer to read if &(foo[0]) is converted to foo like:
> > > >      memcpy(&(ap->bssid[0]), &(ap_info->bssid[0]), ETH_ALEN);
> > > >      memcpy(ap->bssid, ap_info->bssid, ETH_ALEN);
> > > []
> > > > diff --git a/drivers/staging/ks7010/ks_hostif.c b/drivers/staging/ks7010/ks_hostif.c
> > > []
> > > > @@ -212,7 +212,7 @@ int get_ap_information(struct ks_wlan_private *priv, struct ap_info_t *ap_info,
> > > >  	memset(ap, 0, sizeof(struct local_ap_t));
> > > >
> > > >  	/* bssid */
> > > > -	memcpy(&(ap->bssid[0]), &(ap_info->bssid[0]), ETH_ALEN);
> > > > +	memcpy(&ap->bssid[0], &ap_info->bssid[0], ETH_ALEN);
> > >
> > > This code doesn't match the suggested style of
> > > your commit message.
> >
> > Is what is suggested in the commit message correct?  That is, is the 0th
> > element of an array always at the same address as a pointer to the array
> > itself?
>
> I think your wording is a little fuzzy.
>
> Assuming you mean not a pointer to the array,
> but the array itself, yes.

Yes, I mean the array itself,sorry.  Thanks.

Arushi, it would be good it you could make the change you proposed to
make.  The calls would look much more normal that way.

thanks,
julia

>
> --
> 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/1487531915.2198.38.camel%40perches.com.
> For more options, visit https://groups.google.com/d/optout.
>

  reply	other threads:[~2017-02-19 19:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-19 18:26 Arushi Singhal
2017-02-19 18:31 ` Joe Perches
2017-02-19 18:58   ` [Outreachy kernel] " Julia Lawall
2017-02-19 19:18     ` Joe Perches
2017-02-19 19:20       ` Julia Lawall [this message]
2017-02-19 18:55 ` [Outreachy kernel] " Julia Lawall

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.1702192018570.2363@hadrien \
    --to=julia.lawall@lip6.fr \
    --cc=arushisinghal19971997@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome