All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Yashin <dmt.yashin@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Johannes Berg <johannes@sipsolutions.net>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Heiko Stuebner <heiko@sntech.de>,
	netdev@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org,
	Dmitry Yashin <dmt.yashin@gmail.com>
Subject: Re: [PATCH v2 1/5] dt-bindings: net: rfkill-gpio: document reset-gpios property
Date: Thu, 22 Oct 2026 14:38:07 +0500	[thread overview]
Message-ID: <W90ai6epRoWrikRmhqTrfA@gmail.com> (raw)
In-Reply-To: <20261019-aggressive-frigatebird-of-courage-9cc7d6@quoll>

On Monday, 19 October 2026 11:49:17 +05 Krzysztof Kozlowski wrote:
> That's the same pin. This was sent multiple times, why is this time
> different?

Indeed I overlooked previous discussion on the same change. Thank you.
I did a few more tests with the wwan modem. And since this approach to
handle modem reset more like a workaround, I'll just drop this patch
with rfkill node from V3.

-- 
Dmt-Y




WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Yashin <dmt.yashin@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Johannes Berg <johannes@sipsolutions.net>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Heiko Stuebner <heiko@sntech.de>,
	netdev@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org,
	Dmitry Yashin <dmt.yashin@gmail.com>
Subject: Re: [PATCH v2 1/5] dt-bindings: net: rfkill-gpio: document reset-gpios property
Date: Thu, 22 Oct 2026 14:38:07 +0500	[thread overview]
Message-ID: <W90ai6epRoWrikRmhqTrfA@gmail.com> (raw)
In-Reply-To: <20261019-aggressive-frigatebird-of-courage-9cc7d6@quoll>

On Monday, 19 October 2026 11:49:17 +05 Krzysztof Kozlowski wrote:
> That's the same pin. This was sent multiple times, why is this time
> different?

Indeed I overlooked previous discussion on the same change. Thank you.
I did a few more tests with the wwan modem. And since this approach to
handle modem reset more like a workaround, I'll just drop this patch
with rfkill node from V3.

-- 
Dmt-Y




_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

  reply	other threads:[~2026-10-22  9:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16 10:29 [PATCH v2 0/5] arm64: dts: rockchip: add Forlinx OK3568-C Dmitry Yashin
2026-10-16 10:29 ` Dmitry Yashin
2026-10-16 10:29 ` [PATCH v2 1/5] dt-bindings: net: rfkill-gpio: document reset-gpios property Dmitry Yashin
2026-10-16 10:29   ` Dmitry Yashin
2026-10-19  6:49   ` Krzysztof Kozlowski
2026-10-19  6:49     ` Krzysztof Kozlowski
2026-10-22  9:38     ` Dmitry Yashin [this message]
2026-10-22  9:38       ` Dmitry Yashin
2026-10-16 10:29 ` [PATCH v2 2/5] dt-bindings: arm: rockchip: add Forlinx FET3568-C Dmitry Yashin
2026-10-16 10:29   ` Dmitry Yashin
2026-10-16 10:29 ` [PATCH v2 3/5] arm64: dts: " Dmitry Yashin
2026-10-16 10:29   ` Dmitry Yashin
2026-10-16 10:29 ` [PATCH v2 4/5] arm64: dts: rockchip: add Forlinx OK3568-C Dmitry Yashin
2026-10-16 10:29   ` Dmitry Yashin
2026-10-16 10:29 ` [PATCH v2 5/5] arm64: dts: rockchip: add FIT-PCIE-SATA overlay Dmitry Yashin
2026-10-16 10:29   ` Dmitry Yashin

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=W90ai6epRoWrikRmhqTrfA@gmail.com \
    --to=dmt.yashin@gmail.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=heiko@sntech.de \
    --cc=johannes@sipsolutions.net \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=netdev@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --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.