From: Greg KH <gregkh@linuxfoundation.org>
To: "Georg Müller" <georgmueller@gmx.net>
Cc: stable@vger.kernel.org, Lorenzo Bianconi <lorenzo@kernel.org>
Subject: Re: Stable request: wifi: mt76: do not run mt76_unregister_device() on unregistered hw
Date: Wed, 2 Oct 2024 12:16:40 +0200 [thread overview]
Message-ID: <2024100221-flight-whenever-eedb@gregkh> (raw)
In-Reply-To: <f520eda3-0831-4590-b337-3bfd85096922@gmx.net>
On Wed, Oct 02, 2024 at 11:55:52AM +0200, Georg Müller wrote:
> commit 41130c32f3a18fcc930316da17f3a5f3bc326aa1 upstream
>
> This was not marked as stable (but has a Fixes: tag), but causes the USB stack
> to crash with 6.1.x kernels.
>
> The patch does not apply when cherry-picking because of the context.
> Should I send the patch again with updated context so that it applies without
> conflicts?
Yes, please submit a working, tested, patch and we will be glad to apply
it.
thanks,
greg k-h
next prev parent reply other threads:[~2024-10-02 10:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 9:55 Stable request: wifi: mt76: do not run mt76_unregister_device() on unregistered hw Georg Müller
2024-10-02 10:16 ` Greg KH [this message]
2024-10-02 12:06 ` [PATCH] " Georg Müller
2024-10-02 12:39 ` Greg KH
2024-10-02 12:41 ` Georg Müller
2024-10-02 12:55 ` Greg KH
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=2024100221-flight-whenever-eedb@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=georgmueller@gmx.net \
--cc=lorenzo@kernel.org \
--cc=stable@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