From: Kalle Valo <kvalo@kernel.org>
To: Catalin Popescu <catalin.popescu@leica-geosystems.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
robh@kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, m.felsch@pengutronix.de,
bsp-development.geo@leica-geosystems.com
Subject: Re: [PATCH net-next 1/2] dt-bindings: net: rfkill-gpio: enable booting in blocked state
Date: Fri, 10 Jan 2025 11:14:02 +0200 [thread overview]
Message-ID: <87frlrowth.fsf@kernel.org> (raw)
In-Reply-To: <20250110081902.1846296-1-catalin.popescu@leica-geosystems.com> (Catalin Popescu's message of "Fri, 10 Jan 2025 09:19:01 +0100")
Catalin Popescu <catalin.popescu@leica-geosystems.com> writes:
> By default, rfkill state is set to unblocked. Sometimes, we want to boot
> in blocked state and let the application unblock the rfkill.
>
> Signed-off-by: Catalin Popescu <catalin.popescu@leica-geosystems.com>
Don't rfkill patches go via wireless-next, not net-next?
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2025-01-10 9:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 8:19 [PATCH net-next 1/2] dt-bindings: net: rfkill-gpio: enable booting in blocked state Catalin Popescu
2025-01-10 8:19 ` [PATCH net-next 2/2] net: rfkill: gpio: allow " Catalin Popescu
2025-01-10 8:32 ` POPESCU Catalin
2025-01-10 8:31 ` [PATCH net-next 1/2] dt-bindings: net: rfkill-gpio: enable " POPESCU Catalin
2025-01-10 9:14 ` Kalle Valo [this message]
2025-01-13 18:32 ` Conor Dooley
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=87frlrowth.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bsp-development.geo@leica-geosystems.com \
--cc=catalin.popescu@leica-geosystems.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.