From: "Ethan Tidmore" <ethantidmore06@gmail.com>
To: "Marcos Andrade" <marcosandrade95963@gmail.com>,
<gregkh@linuxfoundation.org>
Cc: <linux-staging@lists.linux.dev>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: rtl8723bs: Replace network magic numbers with EtherType macros
Date: Sat, 14 Mar 2026 16:30:41 -0500 [thread overview]
Message-ID: <DH2TQCWG23A8.1K0YKHXF7QQYP@gmail.com> (raw)
In-Reply-To: <20260314210426.42532-1-marcosandrade95963@gmail.com>
On Sat Mar 14, 2026 at 4:04 PM CDT, Marcos Andrade wrote:
> Replace hardcoded magic numbers for network protocols (e.g., 0x0806
> for ARP, 0x888e for EAPOL) with their standard EtherType macro
> equivalents (ETH_P_ARP, ETH_P_PAE) defined in <linux/if_ether.h>.
>
> This change improves code readability and aligns the driver with
> standard Linux networking definitions.
>
> Signed-off-by: Marcos Andrade <marcosandrade95963@gmail.com>
> ---
...
> +#include "linux/delay.h"
> +#include "linux/if_ether.h"
You always include linux api headers with <> not "". Also, header files
should be included in alphabetical order:
> #include <drv_types.h>
#include <linux/if_ether.h>
You won't include <linux/delay.h> in your v2 for reasons below.
>
> static u8 P802_1H_OUI[P80211_OUI_LEN] = { 0x00, 0x00, 0xf8 };
> @@ -128,7 +130,7 @@ s32 _rtw_init_xmit_priv(struct xmit_priv *pxmitpriv, struct adapter *padapter)
> /* Tx buf allocation may fail sometimes, so sleep and retry. */
> res = rtw_os_xmit_resource_alloc(padapter, pxmitbuf, (MAX_XMITBUF_SZ + XMITBUF_ALIGN_SZ), true);
> if (res == _FAIL) {
> - msleep(10);
> + usleep_range(10000, 11000);
You didn't mention this in your changelog and is an unrelated change.
Please make this its own separate patch. Also, this should be changed
from msleep(10) to fsleep(10 * USEC_PER_MSEC) as this is the new
standard API.
Thanks,
ET
prev parent reply other threads:[~2026-03-14 21:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-14 21:04 Marcos Andrade
2026-03-14 21:30 ` Ethan Tidmore [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=DH2TQCWG23A8.1K0YKHXF7QQYP@gmail.com \
--to=ethantidmore06@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=marcosandrade95963@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®