From: Luis de Bethencourt <luisbg@osg.samsung.com>
To: Anuradha Weeraman <anuradha@weeraman.com>,
Larry.Finger@lwfinger.net, florian.c.schilhabel@googlemail.com,
gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: rtl8712: Fixed brace and comment style issue
Date: Fri, 08 Jul 2016 19:24:30 +0100 [thread overview]
Message-ID: <577FEFDE.50200@osg.samsung.com> (raw)
In-Reply-To: <20160703035420.1912-1-anuradha@weeraman.com>
On 03/07/16 04:54, Anuradha Weeraman wrote:
> Fixed issues with coding style.
>
> Signed-off-by: Anuradha Weeraman <anuradha@weeraman.com>
> ---
> drivers/staging/rtl8712/xmit_linux.c | 15 ++++++++-------
> 1 file changed, 8 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/staging/rtl8712/xmit_linux.c b/drivers/staging/rtl8712/xmit_linux.c
> index 695f9b9..1e86133 100644
> --- a/drivers/staging/rtl8712/xmit_linux.c
> +++ b/drivers/staging/rtl8712/xmit_linux.c
> @@ -91,7 +91,8 @@ void r8712_set_qos(struct pkt_file *ppktfile, struct pkt_attrib *pattrib)
> } else {
> /* "When priority processing of data frames is supported,
> * a STA's SME should send EAPOL-Key frames at the highest
> - * priority." */
> + * priority."
> + */
>
> if (pattrib->ether_type == 0x888e)
> UserPriority = 7;
> @@ -162,16 +163,16 @@ int r8712_xmit_entry(_pkt *pkt, struct net_device *pnetdev)
> struct _adapter *padapter = netdev_priv(pnetdev);
> struct xmit_priv *pxmitpriv = &(padapter->xmitpriv);
>
> - if (!r8712_if_up(padapter)) {
> + if (!r8712_if_up(padapter))
> goto _xmit_entry_drop;
> - }
> +
> pxmitframe = r8712_alloc_xmitframe(pxmitpriv);
> - if (!pxmitframe) {
> + if (!pxmitframe)
> goto _xmit_entry_drop;
> - }
> - if ((!r8712_update_attrib(padapter, pkt, &pxmitframe->attrib))) {
> +
> + if ((!r8712_update_attrib(padapter, pkt, &pxmitframe->attrib)))
> goto _xmit_entry_drop;
> - }
> +
> padapter->ledpriv.LedControlHandler(padapter, LED_CTL_TX);
> pxmitframe->pkt = pkt;
> if (r8712_pre_xmit(padapter, pxmitframe)) {
>
Patch applies cleanly and removes the checkpatch issues related to
unnecessary braces and trailing */ in a different line.
Hi Anuradha,
It is a good idea to include the checkpatch issue you are solving in
the commit message, in this case it would be:
Fixed issues with coding style
WARNING: Block comments use a trailing */ on a separate line
#94: FILE: drivers/staging/rtl8712/xmit_linux.c:94:
+ * priority." */
WARNING: braces {} are not necessary for single statement blocks
#165: FILE: drivers/staging/rtl8712/xmit_linux.c:165:
+ if (!r8712_if_up(padapter)) {
+ goto _xmit_entry_drop;
+ }
---
You can send each type of checkpatch issue in an separate patch. If
you do this, please fix the other issues as well :) There are some
CamelCase problems and the GPL header needs fixing.
Thanks
Luis
next prev parent reply other threads:[~2016-07-08 18:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-03 3:54 [PATCH] Staging: rtl8712: Fixed brace and comment style issue Anuradha Weeraman
2016-07-08 18:24 ` Luis de Bethencourt [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-06-27 7:37 Anuradha Weeraman
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=577FEFDE.50200@osg.samsung.com \
--to=luisbg@osg.samsung.com \
--cc=Larry.Finger@lwfinger.net \
--cc=anuradha@weeraman.com \
--cc=devel@driverdev.osuosl.org \
--cc=florian.c.schilhabel@googlemail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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