From: Josef Schlehofer <pepe.schlehofer@gmail.com>
To: Felix Fietkau <nbd@nbd.name>,
Lorenzo Bianconi <lorenzo@kernel.org>,
Ryder Lee <ryder.lee@mediatek.com>,
Shayne Chen <shayne.chen@mediatek.com>,
Sean Wang <sean.wang@mediatek.com>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Ming Yen Hsieh <mingyen.hsieh@mediatek.com>,
JB Tsai <jb.tsai@mediatek.com>,
Allan Wang <allan.wang@mediatek.com>,
Quan Zhou <quan.zhou@mediatek.com>,
Devin Wittmayer <lucid_duck@justthetip.ca>,
linux-wireless@vger.kernel.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH wireless-next 0/2] wifi: mt76: mt7925: LED support for USB adapters
Date: Thu, 19 Nov 2026 08:11:18 +0100 [thread overview]
Message-ID: <20261119071118.78938-1-pepe.schlehofer@gmail.com> (raw)
In-Reply-To: <20261103133528.53197-1-pepe.schlehofer@gmail.com>
Hi Felix,
any comments on this series? Devin tested it on wireless-next and 6.18
with two firmware versions and sent a Tested-by [1]. The series still
applies to your mt76 branch.
Sean, JB, the question from the cover letter about driving GPIO 8 from
the host is still open.
[1] https://lore.kernel.org/linux-wireless/20261108190313.11505-1-lucid_duck@justthetip.ca/
Thanks,
Josef
prev parent reply other threads:[~2026-11-19 7:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 13:35 [PATCH wireless-next 0/2] wifi: mt76: mt7925: LED support for USB adapters Josef Schlehofer
2026-11-03 13:35 ` [PATCH wireless-next 1/2] wifi: mt76: allow LEDs with only brightness_set_blocking Josef Schlehofer
2026-11-03 13:35 ` [PATCH wireless-next 2/2] wifi: mt76: mt7925: add LED support for USB adapters Josef Schlehofer
2026-11-08 19:03 ` [PATCH wireless-next 0/2] wifi: mt76: mt7925: " Devin Wittmayer
2026-11-19 7:11 ` Josef Schlehofer [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=20261119071118.78938-1-pepe.schlehofer@gmail.com \
--to=pepe.schlehofer@gmail.com \
--cc=allan.wang@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=jb.tsai@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=lucid_duck@justthetip.ca \
--cc=matthias.bgg@gmail.com \
--cc=mingyen.hsieh@mediatek.com \
--cc=nbd@nbd.name \
--cc=quan.zhou@mediatek.com \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shayne.chen@mediatek.com \
/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