From: Krzysztof Kozlowski <krzk@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>,
Shengyu Qu <wiagn233@outlook.com>,
Chukun Pan <amadeus@jmu.edu.cn>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v2 1/1] dt-bindings: net: rfkill-gpio: document reset-gpios
Date: Mon, 14 Jul 2025 07:43:36 +0200 [thread overview]
Message-ID: <afef6851-5e2f-41f4-b8c0-bf9bd77f7eda@kernel.org> (raw)
In-Reply-To: <21d8f6388b98ec0fe8662606a3f1c3181466917d.camel@sipsolutions.net>
On 11/07/2025 09:14, Johannes Berg wrote:
> On Fri, 2025-07-11 at 12:37 +0800, Shengyu Qu wrote:
>> Hello,
>>
>> What is blocking this patch to get merged? I'm seeing more 5G modules
>> need this to work correctly, for example, FM350.
>>
>
> I guess I have no idea, fell through the cracks and so far nobody cared
> enough?
>
> DT folks, what tree should this kind of patch go through? I guess I can
> take it through wireless-next with other rfkill changes? Or should it go
> through some DT tree?
Preferably: net-next, wireless-next.
If you want it via DT, someone needs to explicitly ping Rob on IRC.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-14 5:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 14:30 [PATCH v2 1/1] dt-bindings: net: rfkill-gpio: document reset-gpios Chukun Pan
2024-05-28 14:35 ` [PATCH v2 0/1] " Chukun Pan
2024-05-28 14:36 ` Krzysztof Kozlowski
2024-05-28 14:36 ` [PATCH v2 1/1] " Krzysztof Kozlowski
2024-05-28 14:52 ` Chukun Pan
2024-05-28 15:08 ` Krzysztof Kozlowski
2025-07-11 4:37 ` Shengyu Qu
2025-07-11 7:14 ` Johannes Berg
2025-07-14 5:07 ` Shengyu Qu
2025-07-14 5:43 ` Krzysztof Kozlowski [this message]
2025-07-14 4:00 ` Chukun Pan
2025-07-15 11:29 ` Shengyu Qu
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=afef6851-5e2f-41f4-b8c0-bf9bd77f7eda@kernel.org \
--to=krzk@kernel.org \
--cc=amadeus@jmu.edu.cn \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johannes@sipsolutions.net \
--cc=krzk+dt@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=wiagn233@outlook.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;
as well as URLs for NNTP newsgroup(s).