netdev - Re: [PATCH 2/4] wireless: Use octal not symbolic permissions

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:   Sat, 24 Mar 2018 05:49:29 -0700
From:   Joe Perches <joe@...ches.com>
To:     Kalle Valo <kvalo@...eaurora.org>
Cc:     Jiri Slaby <jirislaby@...il.com>,
        Nick Kossifidis <mickflemm@...il.com>,
        "Luis R. Rodriguez" <mcgrof@...not-panic.com>,
        QCA ath9k Development <ath9k-devel@....qualcomm.com>,
        Christian Lamparter <chunkeey@...glemail.com>,
        Eugene Krasnikov <k.eugene.e@...il.com>,
        Stanislav Yakovlev <stas.yakovlev@...il.com>,
        Stanislaw Gruszka <sgruszka@...hat.com>,
        Johannes Berg <johannes.berg@...el.com>,
        Emmanuel Grumbach <emmanuel.grumbach@...el.com>,
        Luca Coelho <luciano.coelho@...el.com>,
        Intel Linux Wireless <linuxwifi@...el.com>,
        Jakub Kicinski <kubakici@...pl>,
        Helmut Schaa <helmut.schaa@...glemail.com>,
        Solomon Peachy <pizza@...ftnet.org>,
        Matthias Brugger <matthias.bgg@...il.com>,
        Arend van Spriel <arend.vanspriel@...adcom.com>,
        Franky Lin <franky.lin@...adcom.com>,
        Hante Meuleman <hante.meuleman@...adcom.com>,
        Chi-Hsien Lin <chi-hsien.lin@...ress.com>,
        Wright Feng <wright.feng@...ress.com>,
        linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
        linux-kernel@...r.ke
Subject: Re: [PATCH 2/4] wireless: Use octal not symbolic permissions

On Sat, 2018-03-24 at 12:09 +0200, Kalle Valo wrote:
> Joe Perches <joe@...ches.com> writes:
> > Prefer the direct use of octal for permissions.
[]
> I don't know what tree are you planning to send these to, but I would
> prefer to take this to wireless-drivers-next to minimise any conflicts.

Fine by me.  Done against -next.