All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Heidelberg <david@ixit.cz>
To: Brian Norris <briannorris@chromium.org>
Cc: Miaoqing Pan <miaoqing@codeaurora.org>,
	Kalle Valo <kvalo@codeaurora.org>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2] ath10k: fix wmi mgmt tx queue full due to race condition
Date: Mon, 09 Aug 2021 21:40:38 +0200	[thread overview]
Message-ID: <QZ7LXQ.RQD9UODPTG672@ixit.cz> (raw)
In-Reply-To: <CA+ASDXOHFijzJeRFEFy6okgNYNZKdc6HZtzZ9-6mdkYEfzL-2g@mail.gmail.com>

Thank you,

you're right, I messed up Reply-to. I'll follow the Option 2.

Thank you
Best regards
David Heidelberg

On Mon, Aug 9 2021 at 12:01:45 -0700, Brian Norris 
<briannorris@chromium.org> wrote:
> (NB: I think your Reply-To header was wrong, so I've chosen to modify
> that in hopes of actually reaching you.)
> 
> On Mon, Aug 9, 2021 at 2:52 AM David Heidelberg <david@ixit.cz> wrote:
>>  since I noticed this issue is very common (at least for me and some
>>  others) on 4.14 kernels [1] [2] would you think that backporting 
>> this
>>  patch into stable would make sense? I assume that at some point it
>>  could help some OpenWRT/LEDE and other devices (since for Turris 
>> it'll
>>  be most likely backported anyway).
>> 
>>  Thank you for the working on this!
>>  David
>> 
>>  [1]
>>  
>> https://forum.turris.cz/t/5-2-4-patch-wifi-fails-after-while-wmi-mgmt-tx-queue-is-full/15510
>>  [2] https://forum.turris.cz/t/unstable-wifi-on-mox-b/11065/
> 
> Seems reasonable to me. The right way to submit such a request is
> documented here:
> 
> https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> 
> Because this wasn't identified as a -stable candidate when first
> submitted, you'll need either Option 2 or Option 3.
> 
> Regards,
> Brian



  reply	other threads:[~2021-08-09 19:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-09  9:51 [PATCH v2] ath10k: fix wmi mgmt tx queue full due to race condition David Heidelberg
2021-08-09 19:01 ` Brian Norris
2021-08-09 19:40   ` David Heidelberg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-12-22  6:34 Miaoqing Pan
2020-12-22  6:34 ` Miaoqing Pan
2020-12-22 18:26 ` Brian Norris
2020-12-22 18:26   ` Brian Norris
2021-01-28  7:19 ` Kalle Valo
2021-01-28  7:19 ` 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=QZ7LXQ.RQD9UODPTG672@ixit.cz \
    --to=david@ixit.cz \
    --cc=briannorris@chromium.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=miaoqing@codeaurora.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 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.