From: Johannes Berg <johannes@sipsolutions.net>
To: Lucid Duck <lucid_duck@justthetip.ca>,
nbd@nbd.name, lorenzo.bianconi83@gmail.com
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/3] wifi: mt76: kernel 6.18 compatibility and txpower reporting fix
Date: Mon, 19 Jan 2026 10:06:56 +0100 [thread overview]
Message-ID: <bb4d01dc4cda7e2fdb85489e8e42f2bcfdc1fc96.camel@sipsolutions.net> (raw)
In-Reply-To: <20260115230252.43391-1-lucid_duck@justthetip.ca> (sfid-20260116_000600_198058_1F58BA40)
Hi,
I don't know who you are and if you're serious about this at all, since
this doesn't look like a very serious submission (against 6.18, etc.),
but even if you do that, please ensure that _every_ patch sent to this
list is actually addressed for the kernel and using the right paths.
>
> mt76.h | 1 +
> mt7615/main.c | 6 ++--
> mt7615/pci_mac.c | 4 +--
> mt7615/usb.c | 2 +-
> mt76_connac_mcu.c | 13 ++++++-
> mt76x0/eeprom.c | 2 +-
> mt76x02_eeprom.c | 2 +-
> mt76x02_usb_core.c | 4 +--
> mt76x2/eeprom.c | 2 +-
> mt7921/main.c | 84 +++++++++++++++++++++++++++++++++++-----------
> mt7925/main.c | 4 +--
> mt792x_core.c | 6 ++--
> 12 files changed, 93 insertions(+), 37 deletions(-)
These are clearly not patches that can be applied to the kernel, and
they're erroneously routed to me.
johannes
prev parent reply other threads:[~2026-01-19 9:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 23:02 [PATCH 0/3] wifi: mt76: kernel 6.18 compatibility and txpower reporting fix Lucid Duck
2026-01-15 23:02 ` [PATCH 1/3] wifi: mt76: update timer APIs for kernel 6.18 Lucid Duck
2026-01-15 23:02 ` [PATCH 2/3] wifi: mt76: mt7921: convert to MLO callbacks and fix txpower reporting Lucid Duck
2026-01-19 9:06 ` Johannes Berg [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=bb4d01dc4cda7e2fdb85489e8e42f2bcfdc1fc96.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi83@gmail.com \
--cc=lucid_duck@justthetip.ca \
--cc=nbd@nbd.name \
/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