From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B9F15C6FA8A for ; Thu, 15 Sep 2022 01:20:36 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229678AbiIOBUf (ORCPT ); Wed, 14 Sep 2022 21:20:35 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34860 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229936AbiIOBUb (ORCPT ); Wed, 14 Sep 2022 21:20:31 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A1CF336DC1 for ; Wed, 14 Sep 2022 18:20:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1663204829; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=0bjgK+lBiTyGtI8DZXw0xpj/MCgq70rfPwVLT8sgAVc=; b=V3nI21NnaAzYEFySyHJss9FWQpsyvrunybdsx6dBCqu4CkWbgVYfD9I32G1/lY9Mt95PZ5 7inhU3OFQYIhZV9hJCwiO5SXuyH+A8N6pAlDpAv2y/v7SzlD1y0peoY6Uusn2aATW6wUCL w/0aKkHpfGCkDg3CtMCDyAvWh06vCls= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-594-nDvdEKQIPbKHKqYFLvmIfg-1; Wed, 14 Sep 2022 21:20:27 -0400 X-MC-Unique: nDvdEKQIPbKHKqYFLvmIfg-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 5C6B83C0D85A; Thu, 15 Sep 2022 01:20:27 +0000 (UTC) Received: from localhost (ovpn-12-63.pek2.redhat.com [10.72.12.63]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 786D31121314; Thu, 15 Sep 2022 01:20:26 +0000 (UTC) Date: Thu, 15 Sep 2022 09:20:22 +0800 From: Baoquan He To: Rob Herring Cc: Stefan Berger , Nayna Jain , akpm@linux-foundation.org, nasastry@in.ibm.com, Michael Ellerman , "kexec@lists.infradead.org" , "devicetree@vger.kernel.org" , Linux Kernel Mailing List , linux-integrity Subject: Re: [PATCH v8 0/4] tpm: Preserve TPM measurement log across kexec (ppc64) Message-ID: References: <20220901214610.768645-1-stefanb@linux.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Scanned-By: MIMEDefang 3.1 on 10.11.54.3 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/14/22 at 01:01pm, Rob Herring wrote: > On Mon, Sep 12, 2022 at 8:01 AM Stefan Berger 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. Looks like a PPC specific improvement, is it possible to have TPM on other ARCHes? For generic code patch, Andrew kindly help pick them into his tree if cooked. If it's an arch or component specific code, we usually ask arch or component maintainer to take it. For this patchset, it should be merged into ppc tree? Thanks Baoquan