From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Corentin Chary <corentin.chary@gmail.com>,
Hans de Goede <hdegoede@redhat.com>,
Mark Gross <mgross@linux.intel.com>,
Platform Driver <platform-driver-x86@vger.kernel.org>
Subject: Re: [PATCH] platform/x86: samsung-laptop: set debugfs blobs to read only
Date: Tue, 4 May 2021 16:09:51 +0300 [thread overview]
Message-ID: <CAHp75VfHsMg78vTxEw910ez+28OeNEhzwUQehOHkZxAqePkadQ@mail.gmail.com> (raw)
In-Reply-To: <20210504125130.GA43834@ninjato>
On Tue, May 4, 2021 at 3:51 PM Wolfram Sang
<wsa+renesas@sang-engineering.com> wrote:
> > > Those blobs can only be read. So, don't confuse users with 'writable'
> > > flags.
> >
> > Wouldn't it make sense at the same time to convert ugly namings to
> > octal permissions?
>
> I think this is out-of-scpoe for this patch. While I also use octals
> personally, I don't feel strongly about it and let others use what they
> prefer.
Linus has (had?) a strong opinion about it. My point is to reduce the
churn since two patches fixing the very same parameter in a row seems
too much to me.
https://lwn.net/Articles/696227/
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-05-04 13:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 12:31 [PATCH] platform/x86: samsung-laptop: set debugfs blobs to read only Wolfram Sang
2021-05-04 12:40 ` Andy Shevchenko
2021-05-04 12:51 ` Wolfram Sang
2021-05-04 13:09 ` Andy Shevchenko [this message]
2021-05-04 13:17 ` Wolfram Sang
2021-05-04 15:05 ` Andy Shevchenko
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=CAHp75VfHsMg78vTxEw910ez+28OeNEhzwUQehOHkZxAqePkadQ@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=corentin.chary@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgross@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.