[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190916182332.GC16093@linux.intel.com>
Date: Mon, 16 Sep 2019 21:23:32 +0300
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: David Howells <dhowells@...hat.com>
Cc: Joe Perches <joe@...ches.com>, linux-integrity@...r.kernel.org,
keyrings@...r.kernel.org, Mimi Zohar <zohar@...ux.ibm.com>,
James Bottomley <jejb@...ux.ibm.com>,
Mauro Carvalho Chehab <mchehab+samsung@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Nicolas Ferre <nicolas.ferre@...rochip.com>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Add a git and a maintainer entry to keyring
subsystems
On Mon, Sep 16, 2019 at 09:52:51AM +0100, David Howells wrote:
> Joe Perches <joe@...ches.com> wrote:
>
> > > I would recommend splitting the patch in two and putting something like:
> > >
> > > keys: Add Jarkko Sakkinen as co-maintainer
> > >
> > > as the subject of the keyrings maintainership one.
> >
> > Why is there utility in micro splitting such a trivial patch?
>
> Because the keyrings maintainership piece is addressing a major procedural
> concern on Linus's part - and I think it needs to go in its own patch with the
> subject I suggested.
I'll send separate patches tomorrow.
/Jarkko
Powered by blists - more mailing lists