From: Morgan Freeman <morganfreeman6991@gmail.com>
To: Aditya Shankar <aditya.shankar@microchip.com>
Cc: linux-wireless@vger.kernel.org, ganesh.krishna@microchip.com,
gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
Claudiu.Beznea@microchip.com
Subject: Re: [PATCH v2] staging: wilc1000: Fix problems reported by checkpatch
Date: Sat, 16 Dec 2017 17:38:00 +0530 [thread overview]
Message-ID: <20171216120800.GA4457@himanshu-Vostro-3559> (raw)
In-Reply-To: <1513410864-6566-1-git-send-email-aditya.shankar@microchip.com>
Hi Aditya,
On Sat, Dec 16, 2017 at 01:24:24PM +0530, Aditya Shankar wrote:
> This commit fixes below style problems in multiple lines
> Fix checkpatch WARNING: line over 80 characters
>
> Signed-off-by: Aditya Shankar <aditya.shankar@microchip.com>
> ---
The patch subject is not correct!
I'm pretty sure checkpatch will complain if you run it through:
WARNING: A patch subject line should describe the change not the tool
that found it
Take a look at:
https://www.kernel.org/doc/html/latest/process/submitting-patches.html#describe-your-changes
Thanks
Himanshu Jha
> drivers/staging/wilc1000/linux_mon.c | 18 ++++++++++++------
> 1 file changed, 12 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/staging/wilc1000/linux_mon.c b/drivers/staging/wilc1000/linux_mon.c
> index 91d49c4..1c740af 100644
> --- a/drivers/staging/wilc1000/linux_mon.c
> +++ b/drivers/staging/wilc1000/linux_mon.c
> @@ -69,7 +69,8 @@ void WILC_WFI_monitor_rx(u8 *buff, u32 size)
> if (pkt_offset & IS_MANAGMEMENT_CALLBACK) {
> /* hostapd callback mgmt frame */
>
> - skb = dev_alloc_skb(size + sizeof(struct wilc_wfi_radiotap_cb_hdr));
> + skb = dev_alloc_skb(size +
> + sizeof(struct wilc_wfi_radiotap_cb_hdr));
> if (!skb)
> return;
>
> @@ -80,7 +81,8 @@ void WILC_WFI_monitor_rx(u8 *buff, u32 size)
>
> cb_hdr->hdr.it_version = 0; /* PKTHDR_RADIOTAP_VERSION; */
>
> - cb_hdr->hdr.it_len = cpu_to_le16(sizeof(struct wilc_wfi_radiotap_cb_hdr));
> + cb_hdr->hdr.it_len =
> + cpu_to_le16(sizeof(struct wilc_wfi_radiotap_cb_hdr));
>
> cb_hdr->hdr.it_present = cpu_to_le32(
> (1 << IEEE80211_RADIOTAP_RATE) |
> @@ -96,7 +98,8 @@ void WILC_WFI_monitor_rx(u8 *buff, u32 size)
> }
>
> } else {
> - skb = dev_alloc_skb(size + sizeof(struct wilc_wfi_radiotap_hdr));
> + skb = dev_alloc_skb(size +
> + sizeof(struct wilc_wfi_radiotap_hdr));
>
> if (!skb)
> return;
> @@ -105,7 +108,8 @@ void WILC_WFI_monitor_rx(u8 *buff, u32 size)
> hdr = skb_push(skb, sizeof(*hdr));
> memset(hdr, 0, sizeof(struct wilc_wfi_radiotap_hdr));
> hdr->hdr.it_version = 0; /* PKTHDR_RADIOTAP_VERSION; */
> - hdr->hdr.it_len = cpu_to_le16(sizeof(struct wilc_wfi_radiotap_hdr));
> + hdr->hdr.it_len =
> + cpu_to_le16(sizeof(struct wilc_wfi_radiotap_hdr));
> hdr->hdr.it_present = cpu_to_le32
> (1 << IEEE80211_RADIOTAP_RATE); /* | */
> hdr->rate = 5; /* txrate->bitrate / 5; */
> @@ -197,7 +201,8 @@ static netdev_tx_t WILC_WFI_mon_xmit(struct sk_buff *skb,
> skb_pull(skb, rtap_len);
>
> if (skb->data[0] == 0xc0 && (!(memcmp(broadcast, &skb->data[4], 6)))) {
> - skb2 = dev_alloc_skb(skb->len + sizeof(struct wilc_wfi_radiotap_cb_hdr));
> + skb2 = dev_alloc_skb(skb->len +
> + sizeof(struct wilc_wfi_radiotap_cb_hdr));
> if (!skb2)
> return -ENOMEM;
>
> @@ -208,7 +213,8 @@ static netdev_tx_t WILC_WFI_mon_xmit(struct sk_buff *skb,
>
> cb_hdr->hdr.it_version = 0; /* PKTHDR_RADIOTAP_VERSION; */
>
> - cb_hdr->hdr.it_len = cpu_to_le16(sizeof(struct wilc_wfi_radiotap_cb_hdr));
> + cb_hdr->hdr.it_len =
> + cpu_to_le16(sizeof(struct wilc_wfi_radiotap_cb_hdr));
>
> cb_hdr->hdr.it_present = cpu_to_le32(
> (1 << IEEE80211_RADIOTAP_RATE) |
> --
> 2.7.4
>
>
prev parent reply other threads:[~2017-12-16 12:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-16 7:54 [PATCH v2] staging: wilc1000: Fix problems reported by checkpatch Aditya Shankar
2017-12-16 12:08 ` Morgan Freeman [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=20171216120800.GA4457@himanshu-Vostro-3559 \
--to=morganfreeman6991@gmail.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=aditya.shankar@microchip.com \
--cc=devel@driverdev.osuosl.org \
--cc=ganesh.krishna@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-wireless@vger.kernel.org \
/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