From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Roshan Khatri <topofeverest8848@gmail.com>, gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/4] staging: rtl8723bs: include: Fix spelling mistake in rtw_xmit.h
Date: Mon, 9 Sep 2024 19:36:51 +0200 [thread overview]
Message-ID: <0de6807e-c6d1-47c7-8f01-000800880c7f@gmail.com> (raw)
In-Reply-To: <20240909041352.2392-1-topofeverest8848@gmail.com>
On 9/9/24 06:13, Roshan Khatri wrote:
> This patch fixes spelling mistake to increase code readability
> and searching.
>
> Signed-off-by: Roshan Khatri <topofeverest8848@gmail.com>
> ---
> v2: Created patch series as suggested by Phillip
> v1: https://lore.kernel.org/all/20240906141024.10021-1-topofeverest8848@gmail.com/
>
> drivers/staging/rtl8723bs/include/rtw_xmit.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/rtl8723bs/include/rtw_xmit.h b/drivers/staging/rtl8723bs/include/rtw_xmit.h
> index a3b4310caddf..544468f57692 100644
> --- a/drivers/staging/rtl8723bs/include/rtw_xmit.h
> +++ b/drivers/staging/rtl8723bs/include/rtw_xmit.h
> @@ -15,7 +15,7 @@
>
> #define XMITBUF_ALIGN_SZ 512
>
> -/* xmit extension buff defination */
> +/* xmit extension buff definition */
> #define MAX_XMIT_EXTBUF_SZ (1536)
> #define NR_XMIT_EXTBUFF (32)
>
Hi Roshan,
something is wrong with your patch series.
When you look here you will see it is not a real series:
https://lore.kernel.org/linux-staging/
The command I use looks like this:
git format-patch -o ~/Documents/kernel/patches/ --cover-letter -n
--thread=shallow --to="Greg Kroah-Hartman
<gregkh@linuxfoundation.org>,linux-staging@lists.linux.dev,linux-kernel@vger.kernel.org"
74d21cf6062fc65c61ca2c91b81a3a98a646a4f2^..HEAD
Hope this helps...
No need to call may name in the change history.
Thanks for your support.
Bye Philipp
prev parent reply other threads:[~2024-09-09 17:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 4:13 Roshan Khatri
2024-09-09 17:36 ` Philipp Hortmann [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=0de6807e-c6d1-47c7-8f01-000800880c7f@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=topofeverest8848@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®