From: Joe Perches <joe@perches.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Hugh Dickins <hughd@google.com>, Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Minchan Kim <minchan@kernel.org>, Nitin Gupta <ngupta@vflare.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Seth Jennings <sjenning@redhat.com>,
Dan Streetman <ddstreet@ieee.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm: Use octal not symbolic permissions
Date: Mon, 26 Mar 2018 15:50:33 -0700 [thread overview]
Message-ID: <1522104633.12357.36.camel@perches.com> (raw)
In-Reply-To: <20180326154149.4045ec03645d6983de6f11b3@linux-foundation.org>
On Mon, 2018-03-26 at 15:41 -0700, Andrew Morton wrote:
> On Mon, 26 Mar 2018 15:22:32 -0700 Joe Perches <joe@perches.com> wrote:
>
> > mm/*.c files use symbolic and octal styles for permissions.
> >
> > Using octal and not symbolic permissions is preferred by many as more
> > readable.
> >
> > https://lkml.org/lkml/2016/8/2/1945
> >
> > Prefer the direct use of octal for permissions.
>
> Thanks. I'll park this until after -rc1 because the
> benefit-to-potential-for-whoopsies ratio is rather low.
No worries. Whenever.
If you don't like the whitespace changes, or the
sources change so much the patch doesn't apply
cleanly, use the command line below when convenient.
$ ./scripts/checkpatch.pl -f --fix-inplace --types=symbolic_perms mm/*.c
next prev parent reply other threads:[~2018-03-26 22:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 22:22 Joe Perches
2018-03-26 22:36 ` David Rientjes
2018-03-26 23:05 ` Joe Perches
2018-03-26 22:41 ` Andrew Morton
2018-03-26 22:50 ` Joe Perches [this message]
2018-03-28 13:06 ` Michal Hocko
2018-03-28 15:44 ` Joe Perches
2018-03-28 19:07 ` Michal Hocko
2018-03-28 19:26 ` Joe Perches
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=1522104633.12357.36.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=ddstreet@ieee.org \
--cc=hughd@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sjenning@redhat.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
all inboxes | Powered by JetHome®