From: Jakov Novak <jakovnovak30@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: Kees Cook <kees@kernel.org>,
Szymon Wilczek <swilczek.lx@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
Johannes Berg <johannes.berg@intel.com>,
Thomas Gleixner <tglx@kernel.org>,
"John W . Linville" <linville@tuxdriver.com>,
Dan Williams <dcbw@redhat.com>,
libertas-dev@lists.infradead.org, linux-kernel@vger.kernel.org,
skhan@linuxfoundation.org, Jakov Novak <jakovnovak30@gmail.com>
Subject: [PATCH 0/1] usb: fix bug in marvell libertas driver
Date: Fri, 10 Apr 2026 23:32:40 +0200 [thread overview]
Message-ID: <20260410213241.1177592-1-jakovnovak30@gmail.com> (raw)
This patch fixes a bug inside the Marvell Libertas driver.
The problem was the if_usb_disconnect function not properly
calling wake_up(), which lead to if_usb_prog_firmware being
stuck on initialization. This caused the lbs_wait_for_firmware_load
to be stuck as well and to trigger the error message.
The solution was to add the wake_up() call inside if_usb_disconnect.
Jakov Novak (1):
add wake_up call inside if_usb_disconnect
drivers/net/wireless/marvell/libertas/if_usb.c | 1 +
1 file changed, 1 insertion(+)
--
2.53.0
next reply other threads:[~2026-04-10 21:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 21:32 Jakov Novak [this message]
2026-04-10 21:32 ` [PATCH 1/1] add wake_up call inside if_usb_disconnect Jakov Novak
2026-04-15 12:11 ` Johannes Berg
2026-04-15 13:31 ` [PATCH v2 0/1] wifi: libertas: fix bug in Marvell Libertas driver Jakov Novak
2026-04-15 13:31 ` [PATCH v2 1/1] wifi: libertas: add wake_up() call to properly notify fw_wq during disconnect Jakov Novak
2026-05-04 15:04 ` [resend PATCH v2 0/1] wifi: libertas: fix bug in Marvell Libertas driver Jakov Novak
2026-05-04 15:04 ` [resend PATCH v2 1/1] wifi: libertas: add wake_up() call to properly notify Jakov Novak
2026-05-04 15:11 ` [resend PATCH v2 0/1] wifi: libertas: fix bug in Marvell Libertas driver Johannes Berg
2026-05-04 15:59 ` Jeff Johnson
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=20260410213241.1177592-1-jakovnovak30@gmail.com \
--to=jakovnovak30@gmail.com \
--cc=dcbw@redhat.com \
--cc=johannes.berg@intel.com \
--cc=kees@kernel.org \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mingo@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=swilczek.lx@gmail.com \
--cc=tglx@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 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.