From: Kalle Valo <kvalo@kernel.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: linux-wireless@vger.kernel.org, johannes@sipsolutions.net,
aaro.koskinen@iki.fi, rwbugreport@lost-in-the-void.net,
ryder.lee@mediatek.com, Felix Fietkau <nbd@nbd.name>
Subject: Re: [PATCH 5.16] mac80211: fix rate control for retransmitted frames
Date: Mon, 13 Dec 2021 11:21:25 +0200 [thread overview]
Message-ID: <87y24on9m2.fsf@tynnyri.adurom.net> (raw)
In-Reply-To: <b8cd1251-691c-a927-cff2-3476977667b1@leemhuis.info> (Thorsten Leemhuis's message of "Sun, 12 Dec 2021 12:45:37 +0100")
Thorsten Leemhuis <regressions@leemhuis.info> writes:
> Hi, this is your Linux kernel regression tracker speaking.
>
> Top-posting for once, to make this easy accessible to everyone.
>
> What is talking below fix so long to get mainlined? The patch and the
> confirmation that it fixes the regressions was 19 days ago. The patch is
> also in linux-next for 12 days. From my point of view as regression
> tracker that seem "too long", as this is a regression that also affects
> a stable kernel.
>
> Or am I missing something?
In general it just takes time for wireless patches to reach Linus' tree.
For example, we don't usually send pull requests to the net tree every
week so that alone causes delay.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2021-12-13 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 20:43 [PATCH 5.16] mac80211: fix rate control for retransmitted frames Felix Fietkau
2021-11-22 21:04 ` Aaro Koskinen
2021-11-23 14:36 ` Thorsten Leemhuis
2021-12-12 11:45 ` Thorsten Leemhuis
2021-12-13 9:21 ` Kalle Valo [this message]
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=87y24on9m2.fsf@tynnyri.adurom.net \
--to=kvalo@kernel.org \
--cc=aaro.koskinen@iki.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=regressions@leemhuis.info \
--cc=rwbugreport@lost-in-the-void.net \
--cc=ryder.lee@mediatek.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.