All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luka Gejak <luka.gejak@linux.dev>
To: Stepan Ionichev <sozdayvek@gmail.com>, gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	luka.gejak@linux.dev
Subject: Re: [PATCH v2] staging: rtl8723bs: remove unnecessary blank lines in rtw_ioctl_set.c
Date: Mon, 04 May 2026 15:03:59 +0200	[thread overview]
Message-ID: <9C5D7553-B3EB-4127-A655-F7E270752753@linux.dev> (raw)
In-Reply-To: <20260502084930.857-1-sozdayvek@gmail.com>

On May 2, 2026 10:49:30 AM GMT+02:00, Stepan Ionichev <sozdayvek@gmail.com> wrote:
>Drop blank lines flagged by checkpatch.pl in rtw_ioctl_set.c:
>
>  CHECK: Blank lines aren't necessary before a close brace '}'
>  CHECK: Blank lines aren't necessary after an open brace '{'
>
>No functional change.
>
>Signed-off-by: Stepan Ionichev <sozdayvek@gmail.com>
>---
>v2:
>- Rebased onto staging-next.
>- Dropped the hunk between rtw_set_802_11_infrastructure_mode() and
>  rtw_set_802_11_disassociate(): already addressed by commit 7dbc9fd71438
>  ("staging: rtl8723bs: remove multiple blank lines in core/").
>- Narrowed subject to mention rtw_ioctl_set.c, since the wider scope is
>  no longer needed.
>
> drivers/staging/rtl8723bs/core/rtw_ioctl_set.c | 3 ---
> 1 file changed, 3 deletions(-)
>

LGTM,

Reviewed-by: Luka Gejak <luka.gejak@linux.dev>

Best regards,
Luka Gejak


      parent reply	other threads:[~2026-05-04 13:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-01 16:38 [PATCH] staging: rtl8723bs: remove unnecessary blank lines Stepan Ionichev
2026-05-02  8:49 ` [PATCH v2] staging: rtl8723bs: remove unnecessary blank lines in rtw_ioctl_set.c Stepan Ionichev
2026-05-04 12:44   ` Nikolay Kulikov
2026-05-04 13:03   ` Luka Gejak [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=9C5D7553-B3EB-4127-A655-F7E270752753@linux.dev \
    --to=luka.gejak@linux.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=sozdayvek@gmail.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.