From: Greg KH <gregkh@linuxfoundation.org>
To: Tree Davies <tdavies@darkphysics.net>
Cc: philipp.g.hortmann@gmail.com, anjan@momi.ca, error27@gmail.com,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] Staging: rtl8192e: Function name cleanup series 1
Date: Tue, 25 Jul 2023 08:48:28 +0200 [thread overview]
Message-ID: <2023072548-unpledged-slacker-90b6@gregkh> (raw)
In-Reply-To: <ZL9tmaSHxKh2JCau@basil>
On Mon, Jul 24, 2023 at 11:37:13PM -0700, Tree Davies wrote:
> Rename functions to fix checkpatch warning: Avoid CamelCase
>
> Tree Davies (5):
> Staging: rtl8192e: Rename function ActivateBAEntry
> Staging: rtl8192e: Rename function DeActivateBAEntry
> Staging: rtl8192e: Rename function TxTsDeleteBA
> Staging: rtl8192e: Rename function RxTsDeleteBA
> Staging: rtl8192e: Rename function ResetBaEntry
>
> drivers/staging/rtl8192e/rtl819x_BAProc.c | 44 +++++++++++------------
> drivers/staging/rtl8192e/rtl819x_TSProc.c | 6 ++--
> drivers/staging/rtl8192e/rtllib.h | 2 +-
> 3 files changed, 26 insertions(+), 26 deletions(-)
Odd, how did you send these patches? They are not properly "threaded"
or "connected" such that if you look them up on lore.kernel.org, or in
your email client, they show that they should be connected.
Here's what they look like in my inbox right now:
1 T Jul 24 Tree Davies (0.6K) [PATCH 0/5] Staging: rtl8192e: Function name cleanup series 1
2 N T Jul 24 Tree Davies (1.9K) [PATCH 3/5] Staging: rtl8192e: Rename function TxTsDeleteBA
3 F Jul 25 To linux-kernel ( 29) [PATCH v2] Documentation: embargoed-hardware-issues.rst: add AMD to the list
4 N T Jul 24 Tree Davies (2.5K) [PATCH 5/5] Staging: rtl8192e: Rename function ResetBaEntry
5 N T Jul 24 Tree Davies (1.8K) [PATCH 4/5] Staging: rtl8192e: Rename function RxTsDeleteBA
6 N T Jul 24 Tree Davies (3.1K) [PATCH 2/5] Staging: rtl8192e: Rename function DeActivateBAEntry
7 N T Jul 24 Tree Davies (1.7K) [PATCH 1/5] Staging: rtl8192e: Rename function ActivateBAEntry
While if I look at a different recent series sent for staging patches, send
correctly, they look like:
372 T Jul 22 Franziska Naepe (0.9K) [PATCH 0/9] staging: rtl8723bs: ioctl_linux: Fix checkpatch issues
373 C Jul 22 Franziska Naepe (0.8K) ├─>[PATCH 9/9] staging: rtl8723bs: ioctl_linux: Fix comparison to false
374 C Jul 22 Franziska Naepe (7.2K) ├─>[PATCH 8/9] staging: rtl8723bs: ioctl_linux: Add preferred spaces
375 C Jul 22 Franziska Naepe (2.2K) ├─>[PATCH 7/9] staging: rtl8723bs: ioctl_linux: Fix alignment on open parenthesis
376 C Jul 22 Franziska Naepe ( 10K) ├─>[PATCH 6/9] staging: rtl8723bs: ioctl_linux: Remove unnecessary parentheses
377 C Jul 22 Franziska Naepe (5.9K) ├─>[PATCH 5/9] staging: rtl8723bs: ioctl_linux: Remove unnecessary blank lines
378 C Jul 22 Franziska Naepe (4.1K) ├─>[PATCH 4/9] staging: rtl8723bs: ioctl_linux: Remove multiple blank lines
379 C Jul 22 Franziska Naepe (1.0K) ├─>[PATCH 3/9] staging: rtl8723bs: ioctl_linux: Fix block comment alignment
380 C Jul 22 Franziska Naepe (0.9K) ├─>[PATCH 2/9] staging: rtl8723bs: ioctl_linux: Fix code indent
381 C Jul 22 Franziska Naepe (0.9K) └─>[PATCH 1/9] staging: rtl8723bs: ioctl_linux: Fix else on next line
See the difference with the -> and such? No other messages in the middle of
the thread, and they are all connected together so that our tools can handle
them as a series, not as individual patches.
If you use 'git send-email' to send the whole back of patches at once, they
will be properly connected together, so I do recommend using that if you are
starting out.
Please fix up and try again, thanks.
greg k-h
next prev parent reply other threads:[~2023-07-25 6:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 6:37 [PATCH 0/5] Staging: rtl8192e: Function name cleanup series 1 Tree Davies
2023-07-25 6:48 ` Greg KH [this message]
2023-07-27 4:37 ` Tree Davies
2023-07-27 4:53 ` Greg KH
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=2023072548-unpledged-slacker-90b6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=anjan@momi.ca \
--cc=error27@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=philipp.g.hortmann@gmail.com \
--cc=tdavies@darkphysics.net \
/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