From: Kalle Valo <kvalo@kernel.org>
To: Bitterblue Smith <rtl8821cerfe2@gmail.com>
Cc: Jes Sorensen <jes.sorensen@gmail.com>,
linux-wireless@vger.kernel.org, chris.chiu@canonical.com,
Barry Day <briselec@gmail.com>
Subject: Re: [PATCH 1/4] wifi: rtl8xxxu: gen2: Turn on the rate control
Date: Wed, 28 Sep 2022 14:07:18 +0300 [thread overview]
Message-ID: <87zgejrc49.fsf@kernel.org> (raw)
In-Reply-To: <25f998e2-20e9-fcb5-2518-8aef1033ecc0@gmail.com> (Bitterblue Smith's message of "Wed, 28 Sep 2022 12:52:27 +0300")
Bitterblue Smith <rtl8821cerfe2@gmail.com> writes:
> On 28/09/2022 11:39, Kalle Valo wrote:
>
>> Bitterblue Smith <rtl8821cerfe2@gmail.com> writes:
>>
>>> I guess I have to send a different patch for this now.
>>
>> So what should I do with this patchset? Can I take patches 2-4?
>
> Yes, please. They're all independent.
Very good, so I'll then take patches 2-4. I'll drop patch 1 and wait for
the next version.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-09-28 11:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 12:26 [PATCH 0/4] wifi: rtl8xxxu: A few improvements Bitterblue Smith
2022-09-18 12:35 ` [PATCH 1/4] wifi: rtl8xxxu: gen2: Turn on the rate control Bitterblue Smith
2022-09-25 16:53 ` Jes Sorensen
2022-09-27 19:49 ` Bitterblue Smith
2022-09-28 8:39 ` Kalle Valo
2022-09-28 9:52 ` Bitterblue Smith
2022-09-28 11:07 ` Kalle Valo [this message]
2022-09-18 12:40 ` [PATCH 2/4] wifi: rtl8xxxu: gen2: Enable 40 MHz channel width Bitterblue Smith
2022-09-25 16:55 ` Jes Sorensen
2022-09-29 6:18 ` Kalle Valo
2022-09-18 12:42 ` [PATCH 3/4] wifi: rtl8xxxu: Fix AIFS written to REG_EDCA_*_PARAM Bitterblue Smith
2022-09-25 16:56 ` Jes Sorensen
2022-09-26 9:24 ` Kalle Valo
2022-09-18 12:47 ` [PATCH 4/4] wifi: rtl8xxxu: Improve rtl8xxxu_queue_select Bitterblue Smith
2022-09-25 16:57 ` Jes Sorensen
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=87zgejrc49.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=briselec@gmail.com \
--cc=chris.chiu@canonical.com \
--cc=jes.sorensen@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rtl8821cerfe2@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.