From: Lukas Bulwahn <lukas.bulwahn@gmail.com> To: Sumit Garg <sumit.garg@linaro.org>, James Bottomley <jejb@linux.ibm.com>, Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>, Mimi Zohar <zohar@linux.ibm.com> Cc: linux-integrity@vger.kernel.org, keyrings@vger.kernel.org, Sebastian Duda <sebastian.duda@fau.de>, Joe Perches <joe@perches.com>, kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org, Lukas Bulwahn <lukas.bulwahn@gmail.com> Subject: [PATCH v3] MAINTAINERS: adjust to trusted keys subsystem creation Date: Thu, 05 Mar 2020 20:30:13 +0000 [thread overview] Message-ID: <20200305203013.6189-1-lukas.bulwahn@gmail.com> (raw) 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/trusted-keys/ are identified as part of KEYS-TRUSTED. Co-developed-by: Sebastian Duda <sebastian.duda@fau.de> Signed-off-by: Sebastian Duda <sebastian.duda@fau.de> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com> --- Changes to v1: - use a global pattern for matching the whole security/keys/trusted-keys/ directory. Changes to v2: - name the correct directory in the commit message Sumit, please ack. Jarkko, please pick this patch v3. MAINTAINERS | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/MAINTAINERS b/MAINTAINERS index 5c755e03ddee..7f11ac752b91 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -9276,8 +9276,8 @@ L: keyrings@vger.kernel.org S: Supported F: Documentation/security/keys/trusted-encrypted.rst F: include/keys/trusted-type.h -F: security/keys/trusted.c -F: include/keys/trusted.h +F: include/keys/trusted_tpm.h +F: security/keys/trusted-keys/ KEYS/KEYRINGS M: David Howells <dhowells@redhat.com> -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Lukas Bulwahn <lukas.bulwahn@gmail.com> To: Sumit Garg <sumit.garg@linaro.org>, James Bottomley <jejb@linux.ibm.com>, Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>, Mimi Zohar <zohar@linux.ibm.com> Cc: linux-integrity@vger.kernel.org, keyrings@vger.kernel.org, Sebastian Duda <sebastian.duda@fau.de>, Joe Perches <joe@perches.com>, kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org, Lukas Bulwahn <lukas.bulwahn@gmail.com> Subject: [PATCH v3] MAINTAINERS: adjust to trusted keys subsystem creation Date: Thu, 5 Mar 2020 21:30:13 +0100 [thread overview] Message-ID: <20200305203013.6189-1-lukas.bulwahn@gmail.com> (raw) 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/trusted-keys/ are identified as part of KEYS-TRUSTED. Co-developed-by: Sebastian Duda <sebastian.duda@fau.de> Signed-off-by: Sebastian Duda <sebastian.duda@fau.de> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com> --- Changes to v1: - use a global pattern for matching the whole security/keys/trusted-keys/ directory. Changes to v2: - name the correct directory in the commit message Sumit, please ack. Jarkko, please pick this patch v3. MAINTAINERS | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/MAINTAINERS b/MAINTAINERS index 5c755e03ddee..7f11ac752b91 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -9276,8 +9276,8 @@ L: keyrings@vger.kernel.org S: Supported F: Documentation/security/keys/trusted-encrypted.rst F: include/keys/trusted-type.h -F: security/keys/trusted.c -F: include/keys/trusted.h +F: include/keys/trusted_tpm.h +F: security/keys/trusted-keys/ KEYS/KEYRINGS M: David Howells <dhowells@redhat.com> -- 2.17.1
next reply other threads:[~2020-03-05 20:30 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-05 20:30 Lukas Bulwahn [this message] 2020-03-05 20:30 ` [PATCH v3] MAINTAINERS: adjust to trusted keys subsystem creation Lukas Bulwahn 2020-03-06 5:03 ` Sumit Garg 2020-03-06 5:15 ` Sumit Garg 2020-03-06 19:31 ` Jarkko Sakkinen 2020-03-06 19:31 ` Jarkko Sakkinen 2020-03-06 20:50 ` Lukas Bulwahn 2020-03-06 20:50 ` Lukas Bulwahn 2020-03-06 22:40 ` Jarkko Sakkinen 2020-03-06 22:40 ` Jarkko Sakkinen
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=20200305203013.6189-1-lukas.bulwahn@gmail.com \ --to=lukas.bulwahn@gmail.com \ --cc=jarkko.sakkinen@linux.intel.com \ --cc=jejb@linux.ibm.com \ --cc=joe@perches.com \ --cc=kernel-janitors@vger.kernel.org \ --cc=keyrings@vger.kernel.org \ --cc=linux-integrity@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=sebastian.duda@fau.de \ --cc=sumit.garg@linaro.org \ --cc=zohar@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: linkBe 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.