[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87frlrowth.fsf@kernel.org>
Date: Fri, 10 Jan 2025 11:14:02 +0200
From: Kalle Valo <kvalo@...nel.org>
To: Catalin Popescu <catalin.popescu@...ca-geosystems.com>
Cc: andrew+netdev@...n.ch, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, robh@...nel.org,
netdev@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org,
m.felsch@...gutronix.de, bsp-development.geo@...ca-geosystems.com
Subject: Re: [PATCH net-next 1/2] dt-bindings: net: rfkill-gpio: enable
booting in blocked state
Catalin Popescu <catalin.popescu@...ca-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@...ca-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
Powered by blists - more mailing lists