From: Paul Mc Quade <paulmcquad@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: konrad.wilk@oracle.com, labbott@redhat.com,
gregkh@linuxfoundation.org, akpm@linux-foundation.org,
guptap@codeaurora.org, vbabka@suse.cz,
mgorman@techsingularity.net, hannes@cmpxchg.org,
rientjes@google.com, mhocko@suse.com, rppt@linux.vnet.ibm.com,
dave@stgolabs.net, hmclauchlan@fb.com, tglx@linutronix.de,
pombredanne@nexb.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH 1/3] mm: replace S_IRUGO with 0444
Date: Sat, 07 Apr 2018 20:37:52 +0000 [thread overview]
Message-ID: <CAKi5BqYCaxsuuOQtfXqyd+ddf=8ggLB89HQ5TWky6JOq_xxOKA@mail.gmail.com> (raw)
In-Reply-To: <03c43ed43d0ec3ab42940bfffd4c3778bf5d0f11.camel@perches.com>
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
Cool, thanks! I didn't know that.
On Sat 7 Apr 2018, 21:11 Joe Perches <joe@perches.com> wrote:
> On Sat, 2018-04-07 at 19:47 +0100, Paul McQuade wrote:
> > Fix checkpatch warnings about S_IRUGO being less readable than
> > providing the permissions octal as '0444'.
>
> Hey Paul.
>
> I sent a cleanup a couple weeks ago to Andrew Morton for the
> same thing.
>
> https://lkml.org/lkml/2018/3/26/638
>
> Andrew said he'd wait until after -rc1 is out.
>
> btw: checkpatch can do this substitution automatically
>
> cheers, Joe
>
[-- Attachment #2: Type: text/html, Size: 938 bytes --]
prev parent reply other threads:[~2018-04-07 20:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-07 18:47 Paul McQuade
2018-04-07 18:47 ` [PATCH 2/3] mm: Replace S_IWUSR with 0200 Paul McQuade
2018-04-07 18:47 ` [PATCH 3/3] mm: replace S_IRUSR | S_IWUSR with 0600 Paul McQuade
2018-04-07 20:11 ` [PATCH 1/3] mm: replace S_IRUGO with 0444 Joe Perches
2018-04-07 20:37 ` Paul Mc Quade [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='CAKi5BqYCaxsuuOQtfXqyd+ddf=8ggLB89HQ5TWky6JOq_xxOKA@mail.gmail.com' \
--to=paulmcquad@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dave@stgolabs.net \
--cc=gregkh@linuxfoundation.org \
--cc=guptap@codeaurora.org \
--cc=hannes@cmpxchg.org \
--cc=hmclauchlan@fb.com \
--cc=joe@perches.com \
--cc=konrad.wilk@oracle.com \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=pombredanne@nexb.com \
--cc=rientjes@google.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
/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