From: Jakub Kicinski <kuba@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: "Rob Herring" <robh@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
"Jérôme Pouiller" <jerome.pouiller@silabs.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Ajay Singh" <ajay.kathat@microchip.com>,
linux-wireless@vger.kernel.org, devicetree@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
"Rob Herring" <robh+dt@kernel.org>,
"Tony Lindgren" <tony@atomide.com>,
"Kalle Valo" <kvalo@kernel.org>,
"Eric Dumazet" <edumazet@google.com>,
"Adham Abozaeid" <adham.abozaeid@microchip.com>,
"Mark Greer" <mgreer@animalcreek.com>
Subject: Re: [PATCH 1/2] dt-bindings: nfc: use spi-peripheral-props.yaml
Date: Thu, 28 Jul 2022 22:27:47 -0700 [thread overview]
Message-ID: <20220728222747.1a791bc6@kernel.org> (raw)
In-Reply-To: <ea684136-bdbb-1b2c-35d3-64fdbd1d1764@linaro.org>
On Thu, 28 Jul 2022 18:31:32 +0200 Krzysztof Kozlowski wrote:
> Yeah, I wanted to express it that almost no impact is expected if it
> goes independently. I could be more explicit here.
I'm taking the nfc one, and leaving the wireless change for Kalle.
next prev parent reply other threads:[~2022-07-29 5:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 16:41 [PATCH 1/2] dt-bindings: nfc: use spi-peripheral-props.yaml Krzysztof Kozlowski
2022-07-27 16:41 ` [PATCH 2/2] dt-bindings: wireless: " Krzysztof Kozlowski
2022-07-28 15:18 ` Rob Herring
2022-08-09 5:58 ` Kalle Valo
2022-07-28 15:18 ` [PATCH 1/2] dt-bindings: nfc: " Rob Herring
2022-07-28 16:31 ` Krzysztof Kozlowski
2022-07-29 5:27 ` Jakub Kicinski [this message]
2022-07-29 5:30 ` patchwork-bot+netdevbpf
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=20220728222747.1a791bc6@kernel.org \
--to=kuba@kernel.org \
--cc=adham.abozaeid@microchip.com \
--cc=ajay.kathat@microchip.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=jerome.pouiller@silabs.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mgreer@animalcreek.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=tony@atomide.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 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.