From: Jeremy Kerr <jk@codeconstruct.com.au>
To: "Rob Herring" <robh@kernel.org>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
"Przemysław Gaj" <pgaj@cadence.com>
Cc: devicetree@vger.kernel.org, linux-i3c@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i3c: Explicitly include correct DT includes
Date: Sun, 16 Jul 2023 11:55:33 +0800 [thread overview]
Message-ID: <36c13d55cdb0a00bd4768b457987042cfc658349.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20230714174623.4057784-1-robh@kernel.org>
Hi Rob,
> In order to detangle these headers and replace the implicit includes
> with struct declarations
This refers to replacing the implicit includes within the of/ subsystem,
right?
> users need to explicitly include the correct includes.
LGTM, thanks!
Reviewed-by: Jeremy Kerr <jk@codeconstruct.com.au>
Cheers,
Jeremy
next prev parent reply other threads:[~2023-07-16 4:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 17:46 [PATCH] i3c: Explicitly include correct DT includes Rob Herring
2023-07-16 3:55 ` Jeremy Kerr [this message]
2023-07-27 21:24 ` Alexandre Belloni
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=36c13d55cdb0a00bd4768b457987042cfc658349.camel@codeconstruct.com.au \
--to=jk@codeconstruct.com.au \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pgaj@cadence.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).