linux-kernel - Re: [PATCH] staging: rtl8192e: Add blank line after declarations

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ZXvevJ2vEEQ92rau@oatmeal.darkphysics>
Date: Thu, 14 Dec 2023 21:06:04 -0800
From: "<Tree Davies" <tdavies@...kphysics.net>
To: Nathan DSilva <expitau@...il.com>
Cc: gregkh@...uxfoundation.org, philipp.g.hortmann@...il.com,
	tdavies@...kphysics.net, kamrankhadijadj@...il.com,
	linux-staging@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging: rtl8192e: Add blank line after declarations

On Fri, Dec 15, 2023 at 03:28:52AM +0000, Nathan DSilva wrote:
> Found using checkpatch, removes one warning about line breaks after
> declarations.
> 
> This is my first patch, feedback is welcome. I am submitting this as a test
> before moving to other subsystems to (hopefully) make more meaningful
> contributions.
> 
> Signed-off-by: Nathan DSilva <expitau@...il.com>
> ---
>  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

Hi Nathan,

Thanks for your patch, but here are few comments.

1. Your subject line looks good. Keep it.

2. Your commit message should read something like.. 'Do x to fix Y'.
There are lots of examples in the log for this driver which demonstrates this.
You don't want 'This is first patch' in the commit log.

3. For this driver, it is best to send your patches to Greg, Philipp Hortmann,
and Dan Carpenter (error27@...il.com) looks at them sometimes too. And like you
did, cc the mailing lists.

For example, My setup usually looks like...
git send-email ./patches/*  --to=gregkh@...uxfoundation.org --to=philipp.g.hortmann@...il.com --to=anjan@...i.ca  --cc=linux-staging@...ts.linux.dev --cc=linux-kernel@...r.kernel.org

A good source of info for sending patches can be foound here:
at https://docs.kernel.org/process/submitting-patches.html
and also there is a free tutorial at:
https://trainingportal.linuxfoundation.org/courses/a-beginners-guide-to-linux-kernel-development-lfd103

I'm a newbie myself, but I'm happy to help.
Cheers
Tree