From: Krzysztof Kozlowski <krzk@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>,
Felix Fietkau <nbd@nbd.name>,
linux-wireless <linux-wireless@vger.kernel.org>
Cc: Ryder Lee <ryder.lee@mediatek.com>,
devicetree@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Subject: Re: pull request: mt76-next 2026-03-23
Date: Wed, 25 Mar 2026 08:27:51 +0100 [thread overview]
Message-ID: <6bd3cee4-5f9a-4af9-af42-c1ea3cbe54c3@kernel.org> (raw)
In-Reply-To: <3d2f9e4d3f06f93e8eb191ade69f4b43752a36bf.camel@sipsolutions.net>
On 24/03/2026 16:24, Johannes Berg wrote:
> On Mon, 2026-03-23 at 10:33 +0100, Felix Fietkau wrote:
>
>> The following changes since commit 9ac76f3d0bb2940db3a9684d596b9c8f301ef315:
>>
>> Merge tag 'wireless-next-2026-03-19' of https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next (2026-03-19 15:30:20 +0100)
>>
>> are available in the Git repository at:
>>
>> https://github.com/nbd168/wireless tags/mt76-next-2026-03-23
>
> [...]
>
>> dt-bindings: net: wireless: mt76: add mt79 PCI devices
>> dt-bindings: net: wireless: mt76: clarify backoff limit usage
>
> OK I have no idea what happened here, apparently Ryder has a super
> messed up email setup that ended up sending different versions with the
> same Message-Id, so the lore archive is a big mess ... whatever is going
> on there, please fix that.
>
> But given what I _can_ see about these patches in the archive, I don't
> want to pull this now unless I get a clear ACK from DT maintainers.
I don't get what is the question to DT maintainers here.... but there
are no such two commits in the next and I do not see Acks from DT
maintainers on the list.
Why were they applied without Acks? And why the nbd168 tree where they
are applied is not in the next?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-25 7:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 9:33 pull request: mt76-next 2026-03-23 Felix Fietkau
2026-03-24 15:24 ` Johannes Berg
2026-03-25 7:27 ` Krzysztof Kozlowski [this message]
2026-03-25 8:26 ` Felix Fietkau
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=6bd3cee4-5f9a-4af9-af42-c1ea3cbe54c3@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johannes@sipsolutions.net \
--cc=krzk+dt@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=ryder.lee@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