From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: David Howells <dhowells@redhat.com>
Cc: Joe Perches <joe@perches.com>,
linux-integrity@vger.kernel.org, keyrings@vger.kernel.org,
Mimi Zohar <zohar@linux.ibm.com>,
James Bottomley <jejb@linux.ibm.com>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Add a git and a maintainer entry to keyring subsystems
Date: Mon, 16 Sep 2019 18:23:32 +0000 [thread overview]
Message-ID: <20190916182332.GC16093@linux.intel.com> (raw)
In-Reply-To: <32692.1568623971@warthog.procyon.org.uk>
On Mon, Sep 16, 2019 at 09:52:51AM +0100, David Howells wrote:
> Joe Perches <joe@perches.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
WARNING: multiple messages have this Message-ID (diff)
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: David Howells <dhowells@redhat.com>
Cc: Joe Perches <joe@perches.com>,
linux-integrity@vger.kernel.org, keyrings@vger.kernel.org,
Mimi Zohar <zohar@linux.ibm.com>,
James Bottomley <jejb@linux.ibm.com>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Add a git and a maintainer entry to keyring subsystems
Date: Mon, 16 Sep 2019 21:23:32 +0300 [thread overview]
Message-ID: <20190916182332.GC16093@linux.intel.com> (raw)
In-Reply-To: <32692.1568623971@warthog.procyon.org.uk>
On Mon, Sep 16, 2019 at 09:52:51AM +0100, David Howells wrote:
> Joe Perches <joe@perches.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
next prev parent reply other threads:[~2019-09-16 18:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 14:32 [PATCH] MAINTAINERS: Add a git and a maintainer entry to keyring subsystems Jarkko Sakkinen
2019-09-10 14:32 ` Jarkko Sakkinen
2019-09-13 15:03 ` David Howells
2019-09-13 15:03 ` David Howells
2019-09-13 17:36 ` Joe Perches
2019-09-13 17:36 ` Joe Perches
2019-09-14 12:54 ` Jarkko Sakkinen
2019-09-14 12:54 ` Jarkko Sakkinen
2019-09-16 8:52 ` David Howells
2019-09-16 8:52 ` David Howells
2019-09-16 18:23 ` Jarkko Sakkinen [this message]
2019-09-16 18:23 ` Jarkko Sakkinen
2019-09-14 12:53 ` Jarkko Sakkinen
2019-09-14 12:53 ` 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=20190916182332.GC16093@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=gregkh@linuxfoundation.org \
--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=mchehab+samsung@kernel.org \
--cc=nicolas.ferre@microchip.com \
--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
Be 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.