linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Gix <brian.gix@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: brian.gix@intel.com, inga.stotland@intel.com,
	luiz.dentz@gmail.com, tedd.an@linux.intel.com,
	marcel@holtmann.org
Subject: [PATCH BlueZ 0/6] Cleanup: replace symbolic file permissions
Date: Tue, 23 Feb 2021 11:02:46 -0800	[thread overview]
Message-ID: <20210223190252.483784-1-brian.gix@intel.com> (raw)

The kernel has moved away from using Symbolic File Permission macros,
and this is reflected in our checkpatch usage which flags lines which
still use them.  The preferred method is to use the well known octal
notation, for instance 0755 meaning:

User has read/write/execute permissions
Group has read/execute permissions
Other has read/execute permissions

Brian Gix (6):
  mesh: Cleanup deprecated symbolic file permissions
  obexd: Cleanup deprecated symbolic file permissions
  peripheral: Cleanup deprecated symbolic file permissions
  profiles: Cleanup deprecated symbolic file permissions
  src: Cleanup deprecated symbolic file permissions
  tools: Cleanup deprecated symbolic file permissions

 mesh/rpl.c                     |  2 +-
 obexd/plugins/filesystem.c     | 18 +++++++++---------
 obexd/plugins/ftp.c            |  4 ++--
 peripheral/efivars.c           |  3 +--
 profiles/input/suspend-dummy.c |  2 +-
 src/adapter.c                  | 32 ++++++++++++++++----------------
 src/attrib-server.c            |  2 +-
 src/device.c                   | 16 ++++++++--------
 src/sdpd-server.c              |  2 +-
 src/shared/btsnoop.c           |  4 ++--
 src/textfile.c                 |  2 +-
 tools/btsnoop.c                |  3 +--
 tools/create-image.c           |  3 +--
 tools/hcidump.c                |  2 +-
 tools/rctest.c                 |  3 +--
 15 files changed, 47 insertions(+), 51 deletions(-)

-- 
2.25.4


             reply	other threads:[~2021-02-23 19:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23 19:02 Brian Gix [this message]
2021-02-23 19:02 ` [PATCH BlueZ 1/6] mesh: Cleanup deprecated symbolic file permissions Brian Gix
2021-02-23 19:37   ` Cleanup: replace " bluez.test.bot
2021-02-23 22:47     ` An, Tedd
2021-02-23 22:58   ` bluez.test.bot
2021-02-23 19:02 ` [PATCH BlueZ 2/6] obexd: Cleanup deprecated " Brian Gix
2021-02-23 19:02 ` [PATCH BlueZ 3/6] peripheral: " Brian Gix
2021-02-23 19:02 ` [PATCH BlueZ 4/6] profiles: " Brian Gix
2021-02-23 19:02 ` [PATCH BlueZ 5/6] src: " Brian Gix
2021-02-23 19:02 ` [PATCH BlueZ 6/6] tools: " Brian Gix

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=20210223190252.483784-1-brian.gix@intel.com \
    --to=brian.gix@intel.com \
    --cc=inga.stotland@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=tedd.an@linux.intel.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).