From: Joash Naidoo <joash.n09@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Larry.Finger@lwfinger.net, phil@philpotter.co.uk,
paskripkin@gmail.com, dan.carpenter@oracle.com,
linux-staging@lists.linux.dev
Subject: Re: [PATCH v3] staging: r8188eu: fix too many leading tabs
Date: Tue, 27 Sep 2022 08:24:01 +0200 [thread overview]
Message-ID: <87y1u5xrkh.fsf@gmail.com> (raw)
In-Reply-To: <Yy7kON0jNecPXN/k@kroah.com>
Greg KH <gregkh@linuxfoundation.org> writes:
> On Mon, Sep 19, 2022 at 03:23:10PM +0200, Joash Naidoo wrote:
>> Coding style fix. Fix too many leading tabs and line length.
>>
>> Signed-off-by: Joash Naidoo <joash.n09@gmail.com>
>> ---
>> Changes in v3:
>> - Fix flipped condition mistake
>> - move skb NULL check before dereferencing it
>> Changes in v2:
>> - Flip additional nested if conditions and don't reverse
>> the last if statement
>> - Move declarations to start of function
>> - Separate converting __constant_htons to htons to another
>> patch
>
> Always test-build your changes before sending them out so you do
> not get
> grumpy emails from maintainers asking why you didn't test-build
> your
> changes...
>
> thanks,
>
> greg k-h
Hi Greg,
Indeed building and testing is a vital step before sending
changes. Is this message referring to my V3 patch not building? Or
referring to my earlier versions?
Before sending I built my changes with:
make M=drivers/staging/r8188eu clean
make M=drivers/staging/r8188eu
I have a TP-Link Wifi dongle (Model: TL-WN725N) which I used to
test. I enabled the driver as module with make menuconfig, built,
installed (make modules_install && make install) and booted the
modified kernel image (vmlinuz-6.0.0-rc5+). Then I ensured my
wpa_supplicant service runs fine and then just checked if I could
still connect to Wifi and browse the web. (I understand this is
limited, since I didn't catch my error in V2) Furthermore, I also
ran:
dmesg -t -l crit
dmesg -t -l warn
dmesg -t -l err
I have only gotten the following relevant warning:
r8188eu: module is from the staging directory, the quality is
unknown, you have been warned.
If there is anything I still may be lacking, please advise. Thank
you for your support.
Kind Regards,
Joash
next prev parent reply other threads:[~2022-09-27 6:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 13:23 [PATCH v3] staging: r8188eu: fix too many leading tabs Joash Naidoo
2022-09-24 11:04 ` Greg KH
2022-09-27 6:24 ` Joash Naidoo [this message]
2022-09-27 7:04 ` Michael Straube
2022-09-27 7:05 ` Dan Carpenter
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=87y1u5xrkh.fsf@gmail.com \
--to=joash.n09@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-staging@lists.linux.dev \
--cc=paskripkin@gmail.com \
--cc=phil@philpotter.co.uk \
/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