From: Ping-Ke Shih <pkshih@realtek.com>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: Kalle Valo <kvalo@kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Dmitriy Antipov <Dmitriy.Antipov@softline.com>
Subject: RE: [PATCH] rtlwifi: remove unused timer and related code
Date: Thu, 1 Jun 2023 01:36:34 +0000 [thread overview]
Message-ID: <b3860092d9d342e389569be49512ef8f@realtek.com> (raw)
In-Reply-To: <20230531143001.674220-1-dmantipov@yandex.ru>
> -----Original Message-----
> From: Dmitry Antipov <dmantipov@yandex.ru>
> Sent: Wednesday, May 31, 2023 10:30 PM
> To: Ping-Ke Shih <pkshih@realtek.com>
> Cc: Kalle Valo <kvalo@kernel.org>; linux-wireless@vger.kernel.org; Dmitry Antipov <dmantipov@yandex.ru>;
> Dmitriy Antipov <Dmitriy.Antipov@softline.com>
> Subject: [PATCH] rtlwifi: remove unused timer and related code
subject prefix "wifi: rtlwifi: ..."
s-o-b doesn't match your e-mail address of "From".
>
> Drop unused 'dualmac_easyconcurrent_retrytimer' of 'struct rtl_works',
> corresponding 'rtl_easy_concurrent_retrytimer_callback()' handler,
> 'dualmac_easy_concurrent' function pointer of 'struct rtl_hal_ops'
> and related call to 'timer_setup()' in '_rtl_init_deferred_work()'.
>
> Signed-off-by: Dmitriy Antipov <Dmitriy.Antipov@softline.com>
next prev parent reply other threads:[~2023-06-01 1:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 14:30 [PATCH] rtlwifi: remove unused timer and related code Dmitry Antipov
2023-06-01 1:36 ` Ping-Ke Shih [this message]
2023-06-01 4:19 ` Dmitry Antipov
2023-06-01 4:23 ` [PATCH] wifi: " Dmitry Antipov
2023-06-01 5:10 ` Ping-Ke Shih
2023-06-01 5:46 ` Kalle Valo
2023-06-01 8:17 ` [PATCH] [v3] " Dmitry Antipov
2023-06-01 8:23 ` Ping-Ke Shih
2023-06-01 8:31 ` [PATCH] [v4] " Dmitry Antipov
2023-06-01 8:39 ` Ping-Ke Shih
2023-06-01 8:51 ` [PATCH] [v5] " Dmitry Antipov
2023-06-01 12:28 ` Ping-Ke Shih
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=b3860092d9d342e389569be49512ef8f@realtek.com \
--to=pkshih@realtek.com \
--cc=Dmitriy.Antipov@softline.com \
--cc=dmantipov@yandex.ru \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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).