Linux-Integrity Archive on lore.kernel.org
 help / color / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Denis Efremov <efremov@linux.com>
Cc: linux-kernel@vger.kernel.org, Joe Perches <joe@perches.com>,
	James Bottomley <jejb@linux.ibm.com>,
	Mimi Zohar <zohar@linux.ibm.com>,
	linux-integrity@vger.kernel.org, keyrings@vger.kernel.org,
	Denis Kenzior <denkenz@gmail.com>
Subject: Re: Bad file pattern in MAINTAINERS section 'KEYS-TRUSTED'
Date: Fri, 16 Aug 2019 00:57:12 +0300
Message-ID: <20190815215712.tho3fdfk43rs45ej@linux.intel.com> (raw)
In-Reply-To: <7152d1c2-14bc-87ae-618b-830a1fa008b0@linux.com>

On Tue, Aug 13, 2019 at 09:57:59AM +0300, Denis Efremov wrote:
> Hi All,
> 
> Initially, I've prepared a patch and only after found this discussion. So, please,
> look at this patch no more than just a simple reminder that get_maintainers.pl
> still emits this warning.

Can you resend this as a proper patch that can be applied. No other
complains.

/Jarkko

  reply index

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7cd8d12f59bcacd18a78f599b46dac555f7f16c0.camel@perches.com>
2019-03-25 21:27 ` Joe Perches
2019-03-26 11:37   ` Jarkko Sakkinen
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 [this message]
2019-08-15 22:12       ` [RESEND PATCH] MAINTAINERS: keys: Update path to trusted.h Denis Efremov
2019-08-16 18:58         ` Jarkko Sakkinen

Reply instructions:

You may reply publically 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=20190815215712.tho3fdfk43rs45ej@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=denkenz@gmail.com \
    --cc=efremov@linux.com \
    --cc=jejb@linux.ibm.com \
    --cc=joe@perches.com \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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: link

Linux-Integrity Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-integrity/0 linux-integrity/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-integrity linux-integrity/ https://lore.kernel.org/linux-integrity \
		linux-integrity@vger.kernel.org linux-integrity@archiver.kernel.org
	public-inbox-index linux-integrity


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-integrity


AGPL code for this site: git clone https://public-inbox.org/ public-inbox