From: Lee Jones <lee.jones@linaro.org>
To: Joe Perches <joe@perches.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Soham Biswas" <sohambiswas41@gmail.com>,
thierry.reding@gmail.com, linux-pwm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pwm: core: Use octal permission
Date: Wed, 18 Nov 2020 09:49:38 +0000 [thread overview]
Message-ID: <20201118094938.GP1869941@dell> (raw)
In-Reply-To: <ebe315dae8855ed2c55d6ce48f84aa4edd93e5fd.camel@perches.com>
On Wed, 18 Nov 2020, Joe Perches wrote:
> On Wed, 2020-11-18 at 10:35 +0100, Uwe Kleine-König wrote:
>
> > Actually I'd prefer keeping the symbolic name because this is easier to
> > grep for. So to convince me a better reason than "checkpatch says so" is
> > needed.
>
> https://lore.kernel.org/lkml/CA+55aFw5v23T-zvDZp-MmD_EYxF8WbafwwB59934FV7g21uMGQ@mail.gmail.com/
> -------------------------------------------------------------------
> From: Linus Torvalds <torvalds@linux-foundation.org>
> Date: Tue, 2 Aug 2016 16:58:29 -0400
>
> The symbolic names are good for the *other* bits (ie sticky bit, and
> the inode mode _type_ numbers etc), but for the permission bits, the
> symbolic names are just insane crap. Nobody sane should ever use them.
> Not in the kernel, not in user space.
>
> Linus
I was waiting for this!
I see your "checkpatch" filter is working well Joe. :)
--
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2020-11-18 9:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 17:54 [PATCH] pwm: core: Use octal permission Soham Biswas
2020-11-17 18:12 ` Lee Jones
2020-11-17 18:21 ` Soham Biswas
2020-11-18 8:51 ` Lee Jones
2020-11-18 9:35 ` Uwe Kleine-König
2020-11-18 9:41 ` Joe Perches
2020-11-18 9:49 ` Lee Jones [this message]
2020-11-18 9:50 ` Uwe Kleine-König
2020-11-18 10:47 ` Soham Biswas
2020-11-18 12:43 ` [PATCH v2] " Uwe Kleine-König
2020-11-18 13:41 ` Soham Biswas
2020-11-18 13:48 ` Uwe Kleine-König
2020-11-18 13:49 ` Lee Jones
2020-11-18 13:58 ` [PATCH] " Soham Biswas
2020-11-18 14:06 ` Soham Biswas
2020-11-18 14:21 ` Uwe Kleine-König
2020-11-18 14:46 ` Lee Jones
2020-11-18 16:56 ` Uwe Kleine-König
2020-11-18 17:39 ` Soham Biswas
2020-11-18 14:51 ` [PATCH v3] " Soham Biswas
2020-11-18 14:55 ` Soham Biswas
2020-11-18 17:59 ` Thierry Reding
2020-11-18 18:39 ` Soham Biswas
2020-11-18 19:48 ` Uwe Kleine-König
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=20201118094938.GP1869941@dell \
--to=lee.jones@linaro.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=sohambiswas41@gmail.com \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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