From: Kalle Valo <kvalo@codeaurora.org>
To: Joe Perches <joe@perches.com>
Cc: Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Stanislaw Gruszka <sgruszka@redhat.com>,
Jiri Slaby <jirislaby@gmail.com>,
Chi-Hsien Lin <chi-hsien.lin@cypress.com>,
Helmut Schaa <helmut.schaa@googlemail.com>,
Kalle Valo <kvalo@qca.qualcomm.com>,
Luca Coelho <luciano.coelho@intel.com>,
Solomon Peachy <pizza@shaftnet.org>,
Christian Lamparter <chunkeey@googlemail.com>,
wcn36xx@lists.infradead.org, brcm80211-dev-list@cypress.com,
Jakub Kicinski <kubakici@wp.pl>,
Nick Kossifidis <mickflemm@gmail.com>,
Stanislav Yakovlev <stas.yakovlev@gmail.com>,
Arend van Spriel <arend.vanspriel@broadcom.com>,
Johannes Berg <johannes.berg@intel.com>,
Intel Linux Wireless <linuxwifi@intel.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
linux-mediatek@lists.infradead.org,
Wright Feng <wright.feng@cypress.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-arm-kernel@lists.infradea
Subject: Re: [2/4] wireless: Use octal not symbolic permissions
Date: Tue, 27 Mar 2018 08:02:04 +0000 (UTC) [thread overview]
Message-ID: <20180327080205.07AD26030F@smtp.codeaurora.org> (raw)
In-Reply-To: <a368e1c4878619172f3da4849cb211b4dfad0a58.1521845237.git.joe@perches.com>
Joe Perches <joe@perches.com> wrote:
> Prefer the direct use of octal for permissions.
>
> Done with checkpatch -f --types=SYMBOLIC_PERMS --fix-inplace
> and some typing.
>
> Miscellanea:
>
> o Whitespace neatening around these conversions.
>
> Signed-off-by: Joe Perches <joe@perches.com>
Patch applied to wireless-drivers-next.git, thanks.
2ef00c53049b wireless: Use octal not symbolic permissions
--
https://patchwork.kernel.org/patch/10305719/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2018-03-27 8:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 22:54 [PATCH 0/4] net: drivers/net: Use octal permissions Joe Perches
2018-03-23 22:54 ` [PATCH 1/4] ethernet: Use octal not symbolic permissions Joe Perches
2018-03-26 16:08 ` David Miller
2018-03-23 22:54 ` [PATCH 2/4] wireless: " Joe Perches
[not found] ` <87zi2xss27.fsf@purkki.adurom.net>
[not found] ` <87zi2xss27.fsf-5ukZ45wKbUHoml4zekdYB16hYfS7NtTn@public.gmane.org>
2018-03-24 12:49 ` Joe Perches
2018-03-27 8:02 ` Kalle Valo [this message]
2018-03-27 8:02 ` [2/4] " Kalle Valo
2018-03-23 22:54 ` [PATCH 3/4] net: " Joe Perches
2018-03-26 16:08 ` David Miller
2018-03-23 22:54 ` [PATCH 4/4] drivers/net: " Joe Perches
2018-03-26 14:07 ` Wei Liu
2018-03-26 16:08 ` David Miller
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=20180327080205.07AD26030F@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=chi-hsien.lin@cypress.com \
--cc=chunkeey@googlemail.com \
--cc=emmanuel.grumbach@intel.com \
--cc=hante.meuleman@broadcom.com \
--cc=helmut.schaa@googlemail.com \
--cc=jirislaby@gmail.com \
--cc=joe@perches.com \
--cc=johannes.berg@intel.com \
--cc=kubakici@wp.pl \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-arm-kernel@lists.infradea \
--cc=linux-mediatek@lists.infradead.org \
--cc=linuxwifi@intel.com \
--cc=luciano.coelho@intel.com \
--cc=matthias.bgg@gmail.com \
--cc=mickflemm@gmail.com \
--cc=pizza@shaftnet.org \
--cc=sgruszka@redhat.com \
--cc=stas.yakovlev@gmail.com \
--cc=wcn36xx@lists.infradead.org \
--cc=wright.feng@cypress.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;
as well as URLs for NNTP newsgroup(s).