linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org,
	James Bottomley <jejb@linux.ibm.com>,
	Mimi Zohar <zohar@linux.ibm.com>,
	linux-integrity@vger.kernel.org, keyrings@vger.kernel.org,
	Mimi Zohar <zohar@us.ibm.com>,
	David Howells <dhowells@redhat.com>,
	James Morris <jmorris@namei.org>,
	Denis Kenzior <denkenz@gmail.com>,
	Marcel Holtmann <marcel@holtmann.org>,
	James Morris <james.morris@microsoft.com>
Subject: Re: Bad file pattern in MAINTAINERS section 'KEYS-TRUSTED'
Date: Tue, 26 Mar 2019 13:37:25 +0200	[thread overview]
Message-ID: <20190326113725.GA10898@linux.intel.com> (raw)
In-Reply-To: <20190325212705.26837-1-joe@perches.com>

Mimi,

Can you fix this and I can ack and send PR through my tree?

/Jarkko

On Mon, Mar 25, 2019 at 02:27:05PM -0700, Joe Perches wrote:
> A file pattern line in this section of the MAINTAINERS file in linux-next
> does not have a match in the linux source files.
> 
> This could occur because a matching filename was never added, was deleted
> or renamed in some other commit.
> 
> The commits that added and if found renamed or removed the file pattern
> are shown below.
> 
> Please fix this defect appropriately.
> 
> 1: ---------------------------------------------------------------------------
> 
> linux-next MAINTAINERS section:
> 
> 	8587	KEYS-TRUSTED
> 	8588	M:	James Bottomley <jejb@linux.ibm.com>
> 	8589	M:      Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> 	8590	M:	Mimi Zohar <zohar@linux.ibm.com>
> 	8591	L:	linux-integrity@vger.kernel.org
> 	8592	L:	keyrings@vger.kernel.org
> 	8593	S:	Supported
> 	8594	F:	Documentation/security/keys/trusted-encrypted.rst
> 	8595	F:	include/keys/trusted-type.h
> 	8596	F:	security/keys/trusted.c
> -->	8597	F:	security/keys/trusted.h
> 
> 2: ---------------------------------------------------------------------------
> 
> The most recent commit that added or modified file pattern 'security/keys/trusted.h':
> 
> commit 7f3c68bee977ab872827e44de017216736fe21d7
> Author: Mimi Zohar <zohar@linux.vnet.ibm.com>
> Date:   Tue Jan 18 09:07:13 2011 -0500
> 
>     keys: add trusted and encrypted maintainers
>     
>     Add myself and David Safford as maintainers for trusted/encrypted keys.
>     
>     Signed-off-by: Mimi Zohar <zohar@us.ibm.com>
>     Acked-by: David Howells <dhowells@redhat.com>
>     Signed-off-by: James Morris <jmorris@namei.org>
> 
>  MAINTAINERS | 22 ++++++++++++++++++++++
>  1 file changed, 22 insertions(+)
> 
> 3: ---------------------------------------------------------------------------
> 
> The last commit with a real presence of file pattern 'security/keys/trusted.h':
> 
> commit 22447981fc050b5f1bdd0e7cbee89b4152a2b2d8
> Author: Denis Kenzior <denkenz@gmail.com>
> Date:   Tue Oct 9 17:48:49 2018 +0100
> 
>     KEYS: Move trusted.h to include/keys [ver #2]
>     
>     Signed-off-by: Denis Kenzior <denkenz@gmail.com>
>     Signed-off-by: David Howells <dhowells@redhat.com>
>     Tested-by: Marcel Holtmann <marcel@holtmann.org>
>     Reviewed-by: Marcel Holtmann <marcel@holtmann.org>
>     Signed-off-by: James Morris <james.morris@microsoft.com>
> 
>  {security => include}/keys/trusted.h | 0
>  security/keys/trusted.c              | 2 +-
>  2 files changed, 1 insertion(+), 1 deletion(-)

  reply	other threads:[~2019-03-26 11:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7cd8d12f59bcacd18a78f599b46dac555f7f16c0.camel@perches.com>
2019-03-25 21:27 ` Bad file pattern in MAINTAINERS section 'KEYS-TRUSTED' Joe Perches
2019-03-26 11:37   ` Jarkko Sakkinen [this message]
2019-03-26 12:10     ` Mimi Zohar
2019-03-26 14:25       ` James Bottomley
2019-03-26 14:59         ` Denis Kenzior
2019-03-26 16:25           ` James Bottomley
2019-03-27  4:58           ` Jarkko Sakkinen
2019-03-27  4:54         ` Jarkko Sakkinen
2019-08-13  6:57   ` Denis Efremov
2019-08-15 21:57     ` Jarkko Sakkinen
2019-08-15 22:12       ` [RESEND PATCH] MAINTAINERS: keys: Update path to trusted.h Denis Efremov
2019-08-16 18:58         ` Jarkko Sakkinen
2019-09-10 11:50           ` Denis Efremov
2019-09-14 13:50             ` 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=20190326113725.GA10898@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=denkenz@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=james.morris@microsoft.com \
    --cc=jejb@linux.ibm.com \
    --cc=jmorris@namei.org \
    --cc=joe@perches.com \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=zohar@linux.ibm.com \
    --cc=zohar@us.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 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 NNTP newsgroup(s).