Linux kernel staging patches
 help / color / mirror / Atom feed
From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: "Santiago Ruano Rincón" <santiagorr@riseup.net>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: helen.koike@collabora.com, ~lkcamp/patches@lists.sr.ht
Subject: Re: [PATCH] staging: rtl8723bs: rtw_mlme_ext: replace spaces by tabs
Date: Tue, 30 Jul 2024 21:18:53 +0200	[thread overview]
Message-ID: <800efa55-1765-48ea-8648-f9a6739342b6@gmail.com> (raw)
In-Reply-To: <20240730080531.991195-1-santiagorr@riseup.net>

On 7/30/24 10:05, Santiago Ruano Rincón wrote:
> Fix checkpatch error "ERROR: code indent should use tabs where possible"
> in include/rtw_mlme_ext.h:388.
> 
> Signed-off-by: Santiago Ruano Rincón <santiagorr@riseup.net>
> 
> ---
> I am (mostly) a newcommer. Could you please tell me if there is anything
> wrong with this patch? Thank you!
> 
> checkpatch reports a warning in line 387:
> "WARNING: line length of 135 exceeds 100 columns"
> Should I fix the warning in the same patch, or should I send a second
> patch to fix it?
> ---
> ---
>   drivers/staging/rtl8723bs/include/rtw_mlme_ext.h | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/staging/rtl8723bs/include/rtw_mlme_ext.h b/drivers/staging/rtl8723bs/include/rtw_mlme_ext.h
> index 5b8574f5a..720aeeb00 100644
> --- a/drivers/staging/rtl8723bs/include/rtw_mlme_ext.h
> +++ b/drivers/staging/rtl8723bs/include/rtw_mlme_ext.h
> @@ -384,8 +384,8 @@ struct mlme_ext_priv {
>   	unsigned char default_supported_mcs_set[16];
>   
>   	struct ss_res		sitesurvey_res;
> -	struct mlme_ext_info mlmext_info;/* for sta/adhoc mode, including current scanning/connecting/connected related info. */
> -                                                     /* for ap mode, network includes ap's cap_info */
> +	struct mlme_ext_info mlmext_info;	/* for sta/adhoc mode, including current scanning/connecting/connected related info. */
> +						/* for ap mode, network includes ap's cap_info */
>   	struct timer_list		survey_timer;
>   	struct timer_list		link_timer;
>   	struct timer_list		sa_query_timer;


Hi Santiago,

it could be two patches or one. You are only allowed to do one thing at 
a time. So it is also a little depending on your description. The way 
you describe this it is more like two patches.
If your description would be like:

Insert line break to comment, that exceeds 100 columns, to improve 
readability.

It would be OK to correct the indent as well.

If you send in a second version of this patch please use a change 
history. Description from Dan under:
https://staticthinking.wordpress.com/2022/07/27/how-to-send-a-v2-patch/

In case of questions feel free to contact me directly.

Thanks for your support.

Bye Philipp







  reply	other threads:[~2024-07-30 19:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-30  8:05 [PATCH] staging: rtl8723bs: rtw_mlme_ext: replace spaces by tabs Santiago Ruano Rincón
2024-07-30 19:18 ` Philipp Hortmann [this message]
     [not found]   ` <ZqrAgXs7qbt3RVaD@voleno>
2024-08-01  5:47     ` Philipp Hortmann

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=800efa55-1765-48ea-8648-f9a6739342b6@gmail.com \
    --to=philipp.g.hortmann@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=helen.koike@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=santiagorr@riseup.net \
    --cc=~lkcamp/patches@lists.sr.ht \
    /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