From: Marcel Holtmann <marcel@holtmann.org>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>, Takashi Iwai <tiwai@suse.de>,
Fernando Ramos <greenfoo@u92.eu>,
Johan Hedberg <johan.hedberg@gmail.com>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Tedd Ho-Jeong An <tedd.an@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Apply initial command workaround for more Intel chips
Date: Thu, 20 Jan 2022 16:07:37 +0100 [thread overview]
Message-ID: <ACC75B0C-E755-4041-8C07-CB87C8BCC566@holtmann.org> (raw)
In-Reply-To: <6c194b50-84f6-a554-140c-174cb658813a@leemhuis.info>
Hi Thorsten,
> Could the bluetooth maintainers please provide a status update? I wonder
> if it's time to bring this regression to Linus attention, as it seems to
> be an issue that hits quite a few users -- and at the same takes quite a
> long time to get fixed for a issue where a patch with a workaround was
> already proposed one and a half months ago.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=95655456e7cee858a23793f67025765b4c4c227b
Regards
Marcel
next prev parent reply other threads:[~2022-01-20 15:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 16:22 [PATCH] Bluetooth: Apply initial command workaround for more Intel chips Takashi Iwai
2021-12-02 16:32 ` Paul Menzel
2021-12-02 16:47 ` Takashi Iwai
2021-12-02 16:58 ` Paul Menzel
2021-12-03 7:24 ` Takashi Iwai
2021-12-03 21:18 ` Marcel Holtmann
2021-12-04 11:20 ` Takashi Iwai
2021-12-05 10:33 ` Fernando Ramos
2021-12-07 16:14 ` Marcel Holtmann
2021-12-10 13:23 ` Takashi Iwai
2022-01-16 14:06 ` Paul Menzel
2022-01-20 14:26 ` Thorsten Leemhuis
2022-01-20 15:07 ` Marcel Holtmann [this message]
2022-01-20 15:13 ` Thorsten Leemhuis
2022-01-20 14:32 ` Takashi Iwai
2021-12-28 12:43 ` Thorsten Leemhuis
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=ACC75B0C-E755-4041-8C07-CB87C8BCC566@holtmann.org \
--to=marcel@holtmann.org \
--cc=greenfoo@u92.eu \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=luiz.dentz@gmail.com \
--cc=pmenzel@molgen.mpg.de \
--cc=tedd.an@intel.com \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).