public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH RESEND v4] MAINTAINERS: fix lots of alphabetic ordering
Date: Wed, 19 Jul 2017 14:49:52 -0700	[thread overview]
Message-ID: <1500500992.25934.43.camel@perches.com> (raw)
In-Reply-To: <d006d424-5676-6e3d-2cc7-4f3f0b868fd2@infradead.org>

On Wed, 2017-07-19 at 14:40 -0700, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
> 
> Fix major alphabetic errors. No attempt to fix items that all begin
> with the same word (like ARM, BROADCOM, DRM, EDAC, FREESCALE, INTEL,
> OMAP, PCI, SAMSUNG, TI, USB, etc.).

[]

> -APPARMOR SECURITY MODULE
> -M:	John Johansen <john.johansen@canonical.com>
> -L:	apparmor@lists.ubuntu.com (subscribers-only, general discussion)
> -W:	apparmor.wiki.kernel.org
> -T:	git git://git.kernel.org/pub/scm/linux/kernel/git/jj/apparmor-dev.git
> -S:	Supported
> -F:	security/apparmor/
> -F:	Documentation/admin-guide/LSM/apparmor.rst
> -
> -LOADPIN SECURITY MODULE
> -M:	Kees Cook <keescook@chromium.org>
> -T:	git git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git lsm/loadpin
> -S:	Supported
> -F:	security/loadpin/
> -F:	Documentation/admin-guide/LSM/LoadPin.rst
> -
> -YAMA SECURITY MODULE
> -M:	Kees Cook <keescook@chromium.org>
> -T:	git git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git yama/tip
> -S:	Supported
> -F:	security/yama/
> -F:	Documentation/admin-guide/LSM/Yama.rst

Instead of reordering these, perhaps it'd
be getter to rename them.

SECURITY MODULE - APPARMOR

SECURITY MODULE - LOADPIN

SECURITY MODULE - YAMA

      parent reply	other threads:[~2017-07-19 21:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-19 21:40 [PATCH RESEND v4] MAINTAINERS: fix lots of alphabetic ordering Randy Dunlap
2017-07-19 21:44 ` Andrew Morton
2017-07-20  0:08   ` Linus Torvalds
2017-07-20  0:18     ` Randy Dunlap
2017-07-20  0:18     ` Linus Torvalds
2017-07-20  0:19     ` Randy Dunlap
2017-07-20  0:26       ` Linus Torvalds
2017-07-20  0:35         ` Linus Torvalds
2017-07-20  0:53           ` Linus Torvalds
2017-07-20  1:04             ` Randy Dunlap
2017-07-20  1:05     ` Joe Perches
2017-07-20  3:12       ` Joe Perches
2017-07-20  4:24       ` Linus Torvalds
2017-07-20  4:36         ` Theodore Ts'o
2017-07-20  4:53           ` Linus Torvalds
2017-07-20  4:43         ` Joe Perches
2017-07-20  4:57           ` Linus Torvalds
2017-07-20 10:54           ` Michael Ellerman
2017-07-20 16:48             ` Joe Perches
2017-07-20 18:03               ` Linus Torvalds
2017-07-20 22:50                 ` Joe Perches
2017-07-19 21:49 ` Joe Perches [this message]

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=1500500992.25934.43.camel@perches.com \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=torvalds@linux-foundation.org \
    /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