linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Oliver O'Halloran" <oohall@gmail.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Russell Currey <ruscur@russell.cc>,
	Cyril Bur <cyrilbur@gmail.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc: Use octal numbers for file permissions
Date: Tue, 17 Jan 2017 21:54:29 +1100	[thread overview]
Message-ID: <CAOSf1CFwZS1a3zpWafYL0ZMtk0AtWkea_Rkx_s1mgWxQpAD5Kg@mail.gmail.com> (raw)
In-Reply-To: <CAOSf1CGDkoTjZS6NxV42GfP=oGCvF4cdC4Dsv79WkZAXVZV3NA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1441 bytes --]

It has been pointed out that this actually occured in 2017. My apologies.

On 17/01/2017 9:50 PM, "Oliver O'Halloran" <oohall@gmail.com> wrote:

> "It's possible I missed one, but I did genuinely review all of it"
>
> Cyril Bur, 2016
> In a hobart pub, specifically The Winston
>
> On 17/01/2017 8:53 PM, "Michael Ellerman" <mpe@ellerman.id.au> wrote:
>
>> Cyril Bur <cyrilbur@gmail.com> writes:
>>
>> > On Thu, 2017-01-12 at 14:54 +1100, Russell Currey wrote:
>> >> Symbolic macros are unintuitive and hard to read, whereas octal
>> constants
>> >> are much easier to interpret.  Replace macros for the basic permission
>> >> flags (user/group/other read/write/execute) with numeric constants
>> >> instead, across the whole powerpc tree.
>> >>
>> >> Introducing a significant number of changes across the tree for no
>> runtime
>> >> benefit isn't exactly desirable, but so long as these macros are still
>> >> used in the tree people will keep sending patches that add them.  Not
>> only
>> >> are they hard to parse at a glance, there are multiple ways of coming
>> to
>> >> the same value (as you can see with 0444 and 0644 in this patch) which
>> >> hurts readability.
>> >>
>> >> Signed-off-by: Russell Currey <ruscur@russell.cc>
>> >
>> > Reviewed-by: Cyril Bur <cyrilbur@gmail.com>
>>
>> Did you really really review every single change?
>>
>> Because if you did then I don't have to, and that would be *great* :)
>>
>> cheers
>>
>

[-- Attachment #2: Type: text/html, Size: 2300 bytes --]

  reply	other threads:[~2017-01-17 10:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12  3:54 [PATCH] powerpc: Use octal numbers for file permissions Russell Currey
2017-01-13  7:51 ` Cyril Bur
2017-01-17  9:52   ` Michael Ellerman
2017-01-17 10:50     ` Oliver O'Halloran
2017-01-17 10:54       ` Oliver O'Halloran [this message]
2017-01-18  0:05     ` Cyril Bur
2017-01-13  8:11 ` Balbir Singh
2017-01-16  0:21   ` Russell Currey
2017-01-17  7:28     ` Balbir Singh
2018-01-22  3:34 ` Michael Ellerman

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=CAOSf1CFwZS1a3zpWafYL0ZMtk0AtWkea_Rkx_s1mgWxQpAD5Kg@mail.gmail.com \
    --to=oohall@gmail.com \
    --cc=cyrilbur@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=ruscur@russell.cc \
    /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;
as well as URLs for NNTP newsgroup(s).