From: Greg KH <gregkh@linuxfoundation.org>
To: Derek Robson <robsonde@gmail.com>
Cc: Larry.Finger@lwfinger.net, florian.c.schilhabel@googlemail.com,
binoy.jayan@linaro.org, arnd@arndb.de, bhumirks@gmail.com,
shaily15297@yahoo.com, raphael.beamonte@gmail.com,
becher.jannik@gmail.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/9] Staging: rtl8712: rtl871x_mp_ioctl.h - style fix
Date: Mon, 27 Feb 2017 15:22:47 +0100 [thread overview]
Message-ID: <20170227142247.GA16503@kroah.com> (raw)
In-Reply-To: <2766636898e46cb49ac68feeb49819c4caf7e9b0.1488075534.git.robsonde@gmail.com>
On Sun, Feb 26, 2017 at 03:32:08PM +1300, Derek Robson wrote:
> Fixed style of block comments
> Found using checkpatch
>
> Signed-off-by: Derek Robson <robsonde@gmail.com>
> ---
> drivers/staging/rtl8712/rtl871x_mp_ioctl.h | 32 +++++++++++++++---------------
> 1 file changed, 16 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/staging/rtl8712/rtl871x_mp_ioctl.h b/drivers/staging/rtl8712/rtl871x_mp_ioctl.h
> index 1102451a733d..c99a6dbae476 100644
> --- a/drivers/staging/rtl8712/rtl871x_mp_ioctl.h
> +++ b/drivers/staging/rtl8712/rtl871x_mp_ioctl.h
> @@ -162,26 +162,26 @@ static const struct oid_obj_priv oid_rtl_seg_81_80_00[] = {
> */
> {1, oid_rt_pro_set_channel_direct_call_hdl}, /*0x08*/
> {1, oid_null_function}, /*0x09
> - * OID_RT_PRO_SET_SLEEP_MODE_DIRECT_CALL
> - */
> + * OID_RT_PRO_SET_SLEEP_MODE_DIRECT_CALL
> + */
> {1, oid_null_function}, /*0x0A
> - * OID_RT_PRO_SET_WAKE_MODE_DIRECT_CALL
> - */
> + * OID_RT_PRO_SET_WAKE_MODE_DIRECT_CALL
> + */
> {1, oid_rt_pro_set_continuous_tx_hdl}, /*0x0B
> - * OID_RT_PRO_SET_TX_CONTINUOUS_DIRECT_CALL
> - */
> + * OID_RT_PRO_SET_TX_CONTINUOUS_DIRECT_CALL
Now you are going out beyond 80 columns, which is what caused someone to
move the comment to the left earlier :(
Just put the comment in a single line, above the data definition, like
this:
/* 0x0B OID_RT_PRO_SET_TX_CONTINUOUS_DIRECT_CALL */
{1, oid_rt_pro_set_continuous_tx_hdl},
Which makes it easier for everyone to read and understand, which is the
main goal of cleaning up code.
thanks,
greg k-h
next prev parent reply other threads:[~2017-02-27 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-26 2:30 [PATCH 0/9] drivers: staging: rtl8712 - style fix Derek Robson
2017-02-26 2:30 ` [PATCH 1/9] Staging: rtl8712: rtl871x_cmd.h - block comments Derek Robson
2017-02-26 2:30 ` [PATCH 2/9] Staging: rtl8712: rtl871x_event.h - style fix Derek Robson
2017-02-26 2:31 ` [PATCH 3/9] Staging: rtl8712: rtl871x_io.h " Derek Robson
2017-02-26 2:31 ` [PATCH 4/9] Staging: rtl8712: rtl871x_mlme.h " Derek Robson
2017-02-26 2:32 ` [PATCH 5/9] Staging: rtl8712: rtl871x_mp_ioctl.h " Derek Robson
2017-02-27 14:22 ` Greg KH [this message]
2017-02-26 2:32 ` [PATCH 6/9] Staging: rtl8712: rtl871x_pwrctrl.h " Derek Robson
2017-02-26 2:32 ` [PATCH 7/9] Staging: rtl8712: rtl871x_recv.h " Derek Robson
2017-02-26 2:33 ` [PATCH 8/9] Staging: rtl8712: wifi.h " Derek Robson
2017-02-26 2:33 ` [PATCH 9/9] Staging: rtl8712: wlan_bssdef.h " Derek Robson
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=20170227142247.GA16503@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Larry.Finger@lwfinger.net \
--cc=arnd@arndb.de \
--cc=becher.jannik@gmail.com \
--cc=bhumirks@gmail.com \
--cc=binoy.jayan@linaro.org \
--cc=devel@driverdev.osuosl.org \
--cc=florian.c.schilhabel@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=raphael.beamonte@gmail.com \
--cc=robsonde@gmail.com \
--cc=shaily15297@yahoo.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.