From: Dan Carpenter <dan.carpenter@oracle.com>
To: Nam Cao <namcaov@gmail.com>
Cc: hdegoede@redhat.com, Larry.Finger@lwfinger.net,
gregkh@linuxfoundation.org, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
lkp@intel.com
Subject: Re: [PATCH v3 1/3] staging: rtl8723bs: remove unused function ODM_InbandNoise_Monitor
Date: Mon, 22 Aug 2022 11:21:19 +0300 [thread overview]
Message-ID: <20220822082119.GB2695@kadam> (raw)
In-Reply-To: <CA+sZ8B9Pa5h8K9LS17fB2Oy8oRadnVSeup6dqfWoVfV1DKkckw@mail.gmail.com>
On Sat, Aug 20, 2022 at 08:44:19PM +0200, Nam Cao wrote:
> Please ignore these emails. They are detached from the thread for some reason.
>
It's actually normally better to just start a new thread when you resend.
We used to tell people to use --in-reply-to but that ends up being a
pain. The threads get messy. Also these days some subsystems use
patchwork and patchwork does not like --in-reply-to.
regards,
dan carpenter
next prev parent reply other threads:[~2022-08-22 8:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1661018051.git.namcaov@gmail.com>
2022-08-20 18:00 ` [PATCH v3 1/3] staging: rtl8723bs: remove unused function ODM_InbandNoise_Monitor Nam Cao
2022-08-20 18:44 ` Nam Cao
2022-08-22 8:21 ` Dan Carpenter [this message]
2022-08-20 18:00 ` [PATCH v3 2/3] staging: rtl8723bs: remove member noise_level from struct dm_odm_t Nam Cao
2022-08-20 18:00 ` [PATCH v3 3/3] staging: rtl8723bs: remove odm_NoiseMonitor.h and odm_NoiseMonitor.c Nam Cao
2022-08-20 18:00 [PATCH v3 0/3] remove useless files Nam Cao
2022-08-20 18:34 ` [PATCH v3 1/3] staging: rtl8723bs: remove unused function ODM_InbandNoise_Monitor Nam Cao
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=20220822082119.GB2695@kadam \
--to=dan.carpenter@oracle.com \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=lkp@intel.com \
--cc=namcaov@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;
as well as URLs for NNTP newsgroup(s).