All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh+dt@kernel.org>
To: Stefan Berger <stefanb@linux.ibm.com>,
	Palmer Dabbelt <palmer@rivosinc.com>
Cc: Nayna Jain <nayna@linux.ibm.com>,
	nasastry@in.ibm.com, Michael Ellerman <mpe@ellerman.id.au>,
	"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-integrity <linux-integrity@vger.kernel.org>
Subject: Re: [PATCH v8 0/4] tpm: Preserve TPM measurement log across kexec (ppc64)
Date: Wed, 14 Sep 2022 15:18:42 -0500	[thread overview]
Message-ID: <CAL_JsqLN-7LHJuMhR+kbGb_n09K8usmcfKVzA_fV40FHmqaaDw@mail.gmail.com> (raw)
In-Reply-To: <f8c8b3dd-f77b-7917-6029-a288255fee8a@linux.ibm.com>

On Wed, Sep 14, 2022 at 2:46 PM Stefan Berger <stefanb@linux.ibm.com> wrote:
>
>
>
> On 9/14/22 14:01, Rob Herring wrote:
> > On Mon, Sep 12, 2022 at 8:01 AM Stefan Berger <stefanb@linux.ibm.com> wrote:
> >>
> >>
> >> Hi Rob,
> >>
> >>     can you take this series in your tree?
> >
> > IMO, it should be someone that cares about TPM, kexec, or powerpc.
> > Yes, there's code in drivers/of/, but that is purely to avoid
> > duplication of code across powerpc and arm64.
>
> What about 1/4? Can someone else take it into their tree?

I thought that was taken long ago now by Palmer in the riscv tree, but
it seems not.

In any case, it has my Ack, so yes, someone else can take it. It *can*
go in via 2 different trees (as git won't care), but we generally try
to avoid that.

Rob

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh+dt@kernel.org>
To: Stefan Berger <stefanb@linux.ibm.com>,
	Palmer Dabbelt <palmer@rivosinc.com>
Cc: Nayna Jain <nayna@linux.ibm.com>,
	nasastry@in.ibm.com,  Michael Ellerman <mpe@ellerman.id.au>,
	 "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	 "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	 Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	 linux-integrity <linux-integrity@vger.kernel.org>
Subject: Re: [PATCH v8 0/4] tpm: Preserve TPM measurement log across kexec (ppc64)
Date: Wed, 14 Sep 2022 15:18:42 -0500	[thread overview]
Message-ID: <CAL_JsqLN-7LHJuMhR+kbGb_n09K8usmcfKVzA_fV40FHmqaaDw@mail.gmail.com> (raw)
In-Reply-To: <f8c8b3dd-f77b-7917-6029-a288255fee8a@linux.ibm.com>

On Wed, Sep 14, 2022 at 2:46 PM Stefan Berger <stefanb@linux.ibm.com> wrote:
>
>
>
> On 9/14/22 14:01, Rob Herring wrote:
> > On Mon, Sep 12, 2022 at 8:01 AM Stefan Berger <stefanb@linux.ibm.com> wrote:
> >>
> >>
> >> Hi Rob,
> >>
> >>     can you take this series in your tree?
> >
> > IMO, it should be someone that cares about TPM, kexec, or powerpc.
> > Yes, there's code in drivers/of/, but that is purely to avoid
> > duplication of code across powerpc and arm64.
>
> What about 1/4? Can someone else take it into their tree?

I thought that was taken long ago now by Palmer in the riscv tree, but
it seems not.

In any case, it has my Ack, so yes, someone else can take it. It *can*
go in via 2 different trees (as git won't care), but we generally try
to avoid that.

Rob

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2022-09-14 20:19 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01 21:46 [PATCH v8 0/4] tpm: Preserve TPM measurement log across kexec (ppc64) Stefan Berger
2022-09-01 21:46 ` Stefan Berger
2022-09-01 21:46 ` Stefan Berger
2022-09-01 21:46 ` [PATCH v8 1/4] drivers: of: kexec ima: Support 32-bit platforms Stefan Berger
2022-09-01 21:46   ` Stefan Berger
2022-09-01 21:46   ` Stefan Berger
2022-09-01 21:46 ` [PATCH v8 2/4] tpm: of: Make of-tree specific function commonly available Stefan Berger
2022-09-01 21:46   ` Stefan Berger
2022-09-01 21:46   ` Stefan Berger
2022-09-02  3:20   ` Jarkko Sakkinen
2022-09-02  3:20     ` Jarkko Sakkinen
2022-09-02  3:20     ` Jarkko Sakkinen
2022-09-01 21:46 ` [PATCH v8 3/4] of: kexec: Refactor IMA buffer related functions to make them reusable Stefan Berger
2022-09-01 21:46   ` Stefan Berger
2022-09-01 21:46   ` Stefan Berger
2022-09-01 21:46 ` [PATCH v8 4/4] tpm/kexec: Duplicate TPM measurement log in of-tree for kexec Stefan Berger
2022-09-01 21:46   ` Stefan Berger
2022-09-01 21:46   ` Stefan Berger
2022-09-12 13:00 ` [PATCH v8 0/4] tpm: Preserve TPM measurement log across kexec (ppc64) Stefan Berger
2022-09-12 13:00   ` Stefan Berger
2022-09-14 18:01   ` Rob Herring
2022-09-14 18:01     ` Rob Herring
2022-09-14 19:46     ` Stefan Berger
2022-09-14 19:46       ` Stefan Berger
2022-09-14 20:18       ` Rob Herring [this message]
2022-09-14 20:18         ` Rob Herring
2022-09-15  1:20     ` Baoquan He
2022-09-15  1:20       ` Baoquan He
2022-11-11  2:21 ` Coiby Xu
2022-11-11  2:21   ` Coiby Xu
2022-11-11  2:21   ` Coiby Xu
2022-11-11 12:12   ` Stefan Berger
2022-11-11 12:12     ` Stefan Berger
2022-11-11 12:12     ` Stefan Berger

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=CAL_JsqLN-7LHJuMhR+kbGb_n09K8usmcfKVzA_fV40FHmqaaDw@mail.gmail.com \
    --to=robh+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kexec@lists.infradead.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=nasastry@in.ibm.com \
    --cc=nayna@linux.ibm.com \
    --cc=palmer@rivosinc.com \
    --cc=stefanb@linux.ibm.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.