[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.2003052130520.5431@felia>
Date: Thu, 5 Mar 2020 21:32:23 +0100 (CET)
From: Lukas Bulwahn <lukas.bulwahn@...il.com>
To: Sumit Garg <sumit.garg@...aro.org>
cc: Lukas Bulwahn <lukas.bulwahn@...il.com>,
James Bottomley <jejb@...ux.ibm.com>,
Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
Mimi Zohar <zohar@...ux.ibm.com>,
linux-integrity@...r.kernel.org,
"open list:ASYMMETRIC KEYS" <keyrings@...r.kernel.org>,
Sebastian Duda <sebastian.duda@....de>,
Joe Perches <joe@...ches.com>, kernel-janitors@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] MAINTAINERS: adjust to trusted keys subsystem
creation
On Thu, 5 Mar 2020, Sumit Garg wrote:
> On Thu, 5 Mar 2020 at 02:43, Lukas Bulwahn <lukas.bulwahn@...il.com> wrote:
> >
> > Commit 47f9c2796891 ("KEYS: trusted: Create trusted keys subsystem")
> > renamed trusted.h to trusted_tpm.h in include/keys/, and moved trusted.c
> > to trusted-keys/trusted_tpm1.c in security/keys/.
> >
> > Since then, ./scripts/get_maintainer.pl --self-test complains:
> >
> > warning: no file matches F: security/keys/trusted.c
> > warning: no file matches F: include/keys/trusted.h
> >
> > Rectify the KEYS-TRUSTED entry in MAINTAINERS now and ensure that all
> > files in security/keys/ are identified as part of KEYS-TRUSTED.
> >
>
> I guess you meant here security/keys/trusted-keys/ instead of security/keys/.
>
Yes, that is what I meant. I rushed the patch v2 last night.
Here is hopefully now a PATCH v3 you can ack:
https://lore.kernel.org/linux-integrity/20200305203013.6189-1-lukas.bulwahn@gmail.com/T/#u
Lukas
Powered by blists - more mailing lists