From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Matt Johnston <matt@codeconstruct.com.au>,
linux-i3c@lists.infradead.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org
Cc: Eric Dumazet <edumazet@google.com>,
Jeremy Kerr <jk@codeconstruct.com.au>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH 2/3] i3c: Add support for bus enumeration & notification
Date: Mon, 3 Jul 2023 17:01:33 +0200 [thread overview]
Message-ID: <56c0783b-59b4-0eda-5a9a-ceed53ebf41d@linaro.org> (raw)
In-Reply-To: <20230703053048.275709-3-matt@codeconstruct.com.au>
On 03/07/2023 07:30, Matt Johnston wrote:
> From: Jeremy Kerr <jk@codeconstruct.com.au>
>
> This allows other drivers to be notified when new i3c busses are
> attached, referring to a whole i3c bus as opposed to individual
> devices.
>
> Signed-off-by: Jeremy Kerr <jk@codeconstruct.com.au>
Your SoB is missing.
Best regards,
Krzysztof
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next prev parent reply other threads:[~2023-07-03 20:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 5:30 [PATCH 0/3] I3C MCTP net driver Matt Johnston
2023-07-03 5:30 ` [PATCH 1/3] dt-bindings: i3c: Add mctp-controller property Matt Johnston
2023-07-03 7:15 ` Krzysztof Kozlowski
2023-07-03 8:03 ` Matt Johnston
2023-07-03 8:14 ` Matt Johnston
2023-07-03 14:16 ` Krzysztof Kozlowski
2023-07-04 6:34 ` Matt Johnston
2023-07-03 5:30 ` [PATCH 2/3] i3c: Add support for bus enumeration & notification Matt Johnston
2023-07-03 15:01 ` Krzysztof Kozlowski [this message]
2023-07-03 5:30 ` [PATCH 3/3] mctp i3c: MCTP I3C driver Matt Johnston
2023-07-03 11:48 ` David Miller
2023-07-03 14:43 ` Andrew Lunn
2023-07-04 6:49 ` Matt Johnston
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=56c0783b-59b4-0eda-5a9a-ceed53ebf41d@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=jk@codeconstruct.com.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox