From: Michael Straube <straube.linux@gmail.com>
To: Joash Naidoo <joash.n09@gmail.com>, 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 09:04:33 +0200 [thread overview]
Message-ID: <95bc3971-7c01-ba9f-c6f8-984b6ae76846@gmail.com> (raw)
In-Reply-To: <87y1u5xrkh.fsf@gmail.com>
On 9/27/22 08:24, Joash Naidoo wrote:
>
> 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?
>
Hi Joash,
v3 introduces a gcc warning.
drivers/staging/r8188eu/core/rtw_br_ext.c: In function 'dhcp_flag_bcast':
drivers/staging/r8188eu/core/rtw_br_ext.c:606:9: warning: ISO C90
forbids mixed declarations and code [-Wdeclaration-after-statement]
606 | __be16 protocol = *((__be16 *)(skb->data + 2 * ETH_ALEN));
| ^~~~~~
regards,
Michael
next prev parent reply other threads:[~2022-09-27 7:04 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
2022-09-27 7:04 ` Michael Straube [this message]
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=95bc3971-7c01-ba9f-c6f8-984b6ae76846@gmail.com \
--to=straube.linux@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=joash.n09@gmail.com \
--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