public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan DSilva <expitau@gmail.com>
To: gregkh@linuxfoundation.org, philipp.g.hortmann@gmail.com,
	tdavies@darkphysics.net, error27@gmail.com
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	expitau@gmail.com
Subject: [PATCH v2] staging: rtl8192e: Add blank line after declarations
Date: Fri, 15 Dec 2023 15:29:18 +0000	[thread overview]
Message-ID: <20231215152918.532037-1-expitau@gmail.com> (raw)
In-Reply-To: <ZXvevJ2vEEQ92rau@oatmeal.darkphysics>

Remove a warning about line breaks after declarations found by checkpatch.

Signed-off-by: Nathan DSilva <expitau@gmail.com>
---

Thank you very much for your response. I didn't realize you could select
multiple --to recipients, or that you could have comments not in the changelog.

 drivers/staging/rtl8192e/rtllib_rx.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/staging/rtl8192e/rtllib_rx.c b/drivers/staging/rtl8192e/rtllib_rx.c
index ecaa4dec3f94..397859c7f5b1 100644
--- a/drivers/staging/rtl8192e/rtllib_rx.c
+++ b/drivers/staging/rtl8192e/rtllib_rx.c
@@ -946,6 +946,7 @@ static int rtllib_rx_data_filter(struct rtllib_device *ieee, struct ieee80211_hd
 {
 	u8 type, stype;
 	u16 fc = le16_to_cpu(hdr->frame_control);
+
 	type = WLAN_FC_GET_TYPE(fc);
 	stype = WLAN_FC_GET_STYPE(fc);
 
-- 
2.43.0

  reply	other threads:[~2023-12-15 15:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-15  3:28 [PATCH] staging: rtl8192e: Add blank line after declarations Nathan DSilva
2023-12-15  5:06 ` <Tree Davies
2023-12-15 15:29   ` Nathan DSilva [this message]
2023-12-15 15:48     ` [PATCH v2] " Greg KH
2024-01-02 13:22     ` Dan Carpenter
2024-01-02 13:24     ` Dan Carpenter
2024-01-02 13:17   ` [PATCH] " Dan Carpenter
2023-12-15 12:33 ` Greg KH

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=20231215152918.532037-1-expitau@gmail.com \
    --to=expitau@gmail.com \
    --cc=error27@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=philipp.g.hortmann@gmail.com \
    --cc=tdavies@darkphysics.net \
    /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