public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [v2] batman-adv: Use octal permissions instead of macros
Date: Tue, 18 Oct 2016 14:48:04 +0200	[thread overview]
Message-ID: <2335223.4Edfx8Zmej@bentobox> (raw)
In-Reply-To: <20160901082512.16160-1-sven@narfation.org>

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

On Donnerstag, 1. September 2016 10:25:12 CEST Sven Eckelmann wrote:
> Linus prefers to have octal permission numbers instead of combinations of
> macro names ("random line noise"). Also old existing "bad symbolic
> permission bit macro use" should be converted to octal numbers.
> (http://lkml.kernel.org/r/CA+55aFw5v23T-zvDZp-MmD_EYxF8WbafwwB59934FV7g21uMG
> Q@mail.gmail.com)
> 
> Also remove the S_IFREG bit from the octal representation because it is
> filtered out by debugfs_create.
> 
> Signed-off-by: Sven Eckelmann <sven@narfation.org>
> ---
> v2:
>  - fix error in patch subject
> ---
>  net/batman-adv/icmp_socket.c    | 4 ++--
>  net/batman-adv/log.c            | 3 +--
>  net/batman-adv/network-coding.c | 7 +++----
>  3 files changed, 6 insertions(+), 8 deletions(-)

Applied in dec65f2333cb18c2cc28aa41709a7c35c89d1531 [1].

Kind regards,
	Sven

[1] https://git.open-mesh.org/batman-adv.git/commit/dec65f2333cb18c2cc28aa41709a7c35c89d1531

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

      reply	other threads:[~2016-10-18 12:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-01  8:25 [B.A.T.M.A.N.] [PATCH v2] batman-adv: Use octal permissions instead of macros Sven Eckelmann
2016-10-18 12:48 ` Sven Eckelmann [this message]

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=2335223.4Edfx8Zmej@bentobox \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /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