From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Rob Herring" <robh@kernel.org>,
"Peter Huewe" <peterhuewe@gmx.de>,
"Jason Gunthorpe" <jgg@ziepe.ca>
Cc: <linux-integrity@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Add TPM DT bindings to TPM maintainers
Date: Tue, 27 Feb 2024 22:31:52 +0200 [thread overview]
Message-ID: <CZG5AX6QHHQW.YPMIE23V9P2B@kernel.org> (raw)
In-Reply-To: <CAL_JsqJetnzuBcKQMoswuL1X-uwi=meL1EaMOD2LVBg_T_Zn3A@mail.gmail.com>
On Tue Feb 27, 2024 at 4:54 PM EET, Rob Herring wrote:
> On Tue, Jan 30, 2024 at 3:59 PM Rob Herring <robh@kernel.org> wrote:
> >
> > Bindings for a given device class generally go to the respective
> > subsystem maintainers. Add the TPM bindings to the TPM
> > maintainers entry.
> >
> > Signed-off-by: Rob Herring <robh@kernel.org>
> > ---
> > MAINTAINERS | 1 +
> > 1 file changed, 1 insertion(+)
>
> Ping!
>
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 97f51d5ec1cf..e5e3dd672018 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -22040,6 +22040,7 @@ S: Maintained
> > W: https://kernsec.org/wiki/index.php/Linux_Kernel_Integrity
> > Q: https://patchwork.kernel.org/project/linux-integrity/list/
> > T: git git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git
> > +F: Documentation/devicetree/bindings/tpm/
> > F: drivers/char/tpm/
> >
> > TPS546D24 DRIVER
> > --
> > 2.43.0
> >
Somehow went out of my radar, sorry.
Thanks, it does make sense. I can pick the patches but it would be
good if you can check them still.
Reviewed-by: Jarkko Sakkinen <jarkko@kernel.ogr>
BR, Jarkko
prev parent reply other threads:[~2024-02-27 20:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 21:59 [PATCH] MAINTAINERS: Add TPM DT bindings to TPM maintainers Rob Herring
2024-02-27 14:54 ` Rob Herring
2024-02-27 20:31 ` Jarkko Sakkinen [this message]
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=CZG5AX6QHHQW.YPMIE23V9P2B@kernel.org \
--to=jarkko@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).