dmaengine.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
	Vinod Koul <vinod.koul@intel.com>
Cc: Yang Shunyong <shunyong.yang@hxt-semitech.com>,
	Dan Williams <dan.j.williams@intel.com>,
	dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [1/2] dmaengine: dmatest: change symbolic permissions to octal values
Date: Wed, 31 Jan 2018 19:57:00 -0800	[thread overview]
Message-ID: <1517457420.7489.24.camel@perches.com> (raw)

On Thu, 2018-02-01 at 09:16 +0530, Viresh Kumar wrote:
> On Thu, Feb 1, 2018 at 9:15 AM, Vinod Koul <vinod.koul@intel.com> wrote:
> > Right but lets no go changing to octals everywhere, new code sure :)
> > I don't see plans to remove representations entirely from kernel yet.
> 
> Sure. I was just pointing out to the discussion where the *preferred* thing
> happened.

Not really true.  Linus prefers actual octal
and suggested treewide conversions.

https://lwn.net/Articles/696229/
---
To unsubscribe from this list: send the line "unsubscribe dmaengine" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2018-02-01  3:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-01  3:57 Joe Perches [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-02-01  3:46 [1/2] dmaengine: dmatest: change symbolic permissions to octal values Viresh Kumar
2018-02-01  3:45 Vinod Koul
2018-01-31 10:01 Viresh Kumar
2018-01-30 10:04 Vinod Koul
2018-01-29  6:26 Yang Shunyong
2018-01-29  4:48 Vinod Koul
2018-01-22 10:44 Yang Shunyong

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=1517457420.7489.24.camel@perches.com \
    --to=joe@perches.com \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shunyong.yang@hxt-semitech.com \
    --cc=vinod.koul@intel.com \
    --cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).