From: Julia Lawall <julia.lawall@lip6.fr>
To: Arushi Singhal <arushisinghal19971997@gmail.com>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH v4 1/2] staging: ks7010: Unnecessary parentheses are removed.
Date: Sun, 26 Feb 2017 18:33:43 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1702261831470.2056@hadrien> (raw)
In-Reply-To: <20170226172741.GA20524@arushi-HP-Pavilion-Notebook>
On Sun, 26 Feb 2017, Arushi Singhal wrote:
> Unnecessary parentheses are removed as reported by checkpatch.pl
> to make coder nicer and to improve readability.
> Also coding style is improved.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);
Something is wrong in this patch. It looks like it is introducing the
code that you wanted to remove.
In the commit message, there should be a space after the period. It is
not clear what "For example:-" means. If it is part of the same sentence
as the next line, then tIts in the next line should not be capitalized.
Did Greg not accept the previous version of this patch?
julia
>
> Signed-off-by: Arushi Singhal <arushisinghal19971997@gmail.com>
> ---
> Changes in v4:
> - Commit message made more accurate and as per the changes.
>
> drivers/staging/ks7010/ks_hostif.c | 24 ++++++++++++------------
> 1 file changed, 12 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/staging/ks7010/ks_hostif.c b/drivers/staging/ks7010/ks_hostif.c
> index b643a37fb943..1fbd495e5e63 100644
> --- a/drivers/staging/ks7010/ks_hostif.c
> +++ b/drivers/staging/ks7010/ks_hostif.c
> @@ -113,7 +113,7 @@ int get_current_ap(struct ks_wlan_private *priv, struct link_ap_info_t *ap_info)
> int rc = 0;
>
> DPRINTK(3, "\n");
> - ap = &priv->current_ap;
> + ap = &(priv->current_ap);
>
> if ((priv->connect_status & CONNECT_STATUS_MASK) == DISCONNECT_STATUS) {
> memset(ap, 0, sizeof(struct local_ap_t));
> @@ -121,19 +121,19 @@ int get_current_ap(struct ks_wlan_private *priv, struct link_ap_info_t *ap_info)
> }
>
> /* bssid */
> - memcpy(ap->bssid, ap_info->bssid, ETH_ALEN);
> + memcpy(&(ap->bssid[0]), &(ap_info->bssid[0]), ETH_ALEN);
> /* essid */
> - memcpy(ap->ssid.body, priv->reg.ssid.body,
> + memcpy(&(ap->ssid.body[0]), &(priv->reg.ssid.body[0]),
> priv->reg.ssid.size);
> ap->ssid.size = priv->reg.ssid.size;
> /* rate_set */
> - memcpy(ap->rate_set.body, ap_info->rate_set.body,
> + memcpy(&(ap->rate_set.body[0]), &(ap_info->rate_set.body[0]),
> ap_info->rate_set.size);
> ap->rate_set.size = ap_info->rate_set.size;
> if (ap_info->ext_rate_set.size) {
> /* rate_set */
> - memcpy(&ap->rate_set.body[ap->rate_set.size],
> - ap_info->ext_rate_set.body,
> + memcpy(&(ap->rate_set.body[ap->rate_set.size]),
> + &(ap_info->ext_rate_set.body[0]),
> ap_info->ext_rate_set.size);
> ap->rate_set.size += ap_info->ext_rate_set.size;
> }
> @@ -153,11 +153,11 @@ int get_current_ap(struct ks_wlan_private *priv, struct link_ap_info_t *ap_info)
> ap->rsn_ie.id = 0x30;
> if (ap_info->rsn.size <= RSN_IE_BODY_MAX) {
> ap->rsn_ie.size = ap_info->rsn.size;
> - memcpy(ap->rsn_ie.body, ap_info->rsn.body,
> + memcpy(&(ap->rsn_ie.body[0]), &(ap_info->rsn.body[0]),
> ap_info->rsn.size);
> } else {
> ap->rsn_ie.size = RSN_IE_BODY_MAX;
> - memcpy(ap->rsn_ie.body, ap_info->rsn.body,
> + memcpy(&(ap->rsn_ie.body[0]), &(ap_info->rsn.body[0]),
> RSN_IE_BODY_MAX);
> }
> } else if ((ap_info->rsn_mode & RSN_MODE_WPA)
> @@ -165,11 +165,11 @@ int get_current_ap(struct ks_wlan_private *priv, struct link_ap_info_t *ap_info)
> ap->wpa_ie.id = 0xdd;
> if (ap_info->rsn.size <= RSN_IE_BODY_MAX) {
> ap->wpa_ie.size = ap_info->rsn.size;
> - memcpy(ap->wpa_ie.body, ap_info->rsn.body,
> + memcpy(&(ap->wpa_ie.body[0]), &(ap_info->rsn.body[0]),
> ap_info->rsn.size);
> } else {
> ap->wpa_ie.size = RSN_IE_BODY_MAX;
> - memcpy(ap->wpa_ie.body, ap_info->rsn.body,
> + memcpy(&(ap->wpa_ie.body[0]), &(ap_info->rsn.body[0]),
> RSN_IE_BODY_MAX);
> }
> } else {
> @@ -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, ap_info->bssid, ETH_ALEN);
> + memcpy(&(ap->bssid[0]), &(ap_info->bssid[0]), ETH_ALEN);
> /* rssi */
> ap->rssi = ap_info->rssi;
> /* sq */
> @@ -224,7 +224,7 @@ int get_ap_information(struct ks_wlan_private *priv, struct ap_info_t *ap_info,
> /* channel */
> ap->channel = ap_info->ch_info;
>
> - bp = ap_info->body;
> + bp = &(ap_info->body[0]);
> bsize = ap_info->body_size;
> offset = 0;
>
> --
> 2.11.0
>
> --
> 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/20170226172741.GA20524%40arushi-HP-Pavilion-Notebook.
> For more options, visit https://groups.google.com/d/optout.
>
prev parent reply other threads:[~2017-02-26 17:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-26 17:27 Arushi Singhal
2017-02-26 17:33 ` 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.1702261831470.2056@hadrien \
--to=julia.lawall@lip6.fr \
--cc=arushisinghal19971997@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--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
all inboxes | Powered by JetHome®