From: Dmitry Kandybka <d.kandybka@gmail.com>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"lvc-project@linuxtesting.org" <lvc-project@linuxtesting.org>,
Dmitry Antipov <dmantipov@yandex.ru>
Subject: Re: [PATCH] wifi: rtw88: coex: remove rf4ce unused code
Date: Fri, 11 Oct 2024 09:45:18 +0300 [thread overview]
Message-ID: <ab931eaea64e65d1655c8bfd95ffddf32d78ca57.camel@gmail.com> (raw)
In-Reply-To: <9c83fca1a28c4b3f8fb2ca65752ad655@realtek.com>
On Fri, 2024-10-11 at 00:26 +0000, Ping-Ke Shih wrote:
>
> > This is kindly reminder. Could you pay some attention to this patch and
> > clarify if the rf4ce is actual for this moment and future?
>
> Yes. Our coex developers want to keep this chunk. For me, this kind of
> cleanup
> patch is not very help to driver, but I and developers need much time to
> confirm and judge if we keep or remove them, so I would want to ignore
> this
> kind of patches...
>
>
Thanks for you clarification. Have a good work on driver.
next prev parent reply other threads:[~2024-10-11 6:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 5:52 [PATCH] wifi: rtw88: coex: remove rf4ce unused code Dmitry Kandybka
2024-10-10 8:19 ` Dmitry Kandybka
2024-10-11 0:26 ` Ping-Ke Shih
2024-10-11 6:45 ` Dmitry Kandybka [this message]
2024-10-15 9:59 ` Kalle Valo
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=ab931eaea64e65d1655c8bfd95ffddf32d78ca57.camel@gmail.com \
--to=d.kandybka@gmail.com \
--cc=dmantipov@yandex.ru \
--cc=linux-wireless@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=pkshih@realtek.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).