Linux wireless drivers development
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Dale Whinham <daleyo@gmail.com>,
	Jeff Johnson <jeff.johnson@oss.qualcomm.com>
Cc: "François Roux" <franzelfranzel@gmail.com>,
	"Jeff Johnson" <jjohnson@kernel.org>,
	"Manivannan Sadhasivam" <mani@kernel.org>,
	"Krzysztof Kozlowski" <krzk@kernel.org>,
	"Konrad Dybcio" <konradybcio@kernel.org>,
	"Bjorn Andersson" <andersson@kernel.org>,
	"Jérôme de Bretagne" <jerome.debretagne@gmail.com>,
	ath12k@lists.infradead.org, linux-wireless@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wifi: ath12k: skip hardware rfkill setup on Microsoft Surface Pro 11
Date: Mon, 12 Oct 2026 09:15:49 +0200	[thread overview]
Message-ID: <8ff749b8-2ed2-4ccd-9f7d-e7bca7aeb38b@oss.qualcomm.com> (raw)
In-Reply-To: <CAFcmK8haaN=O+aqvcRr4t6jc6dr4Bf2QDDPso-aT_frqEfSPWA@mail.gmail.com>

On 10/5/26 6:50 PM, Dale Whinham wrote:
> On Mon, 5 Oct 2026 at 14:37, Jeff Johnson <jeff.johnson@oss.qualcomm.com> wrote:
>> my preference would to to break this out into a separate table-driven function
>> so that if other devices have this issue they would just need to add to the table.
> 
> Indeed, as far as I know Microsoft Surface Laptop 7 (aka. Romulus) is
> also affected by this issue.

I can confirm

Konrad

      reply	other threads:[~2026-10-12  7:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-04 16:51 [PATCH] wifi: ath12k: skip hardware rfkill setup on Microsoft Surface Pro 11 François Roux
2026-10-05 14:37 ` Jeff Johnson
2026-10-05 16:50   ` Dale Whinham
2026-10-12  7:15     ` Konrad Dybcio [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=8ff749b8-2ed2-4ccd-9f7d-e7bca7aeb38b@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=ath12k@lists.infradead.org \
    --cc=daleyo@gmail.com \
    --cc=franzelfranzel@gmail.com \
    --cc=jeff.johnson@oss.qualcomm.com \
    --cc=jerome.debretagne@gmail.com \
    --cc=jjohnson@kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mani@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