From: Christer Weinigel <christer@weinigel.se>
To: Mark Brown <broonie@kernel.org>, Frank Rowand <frowand.list@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH] devicetree - document using aliases to set spi bus number.
Date: Sat, 28 May 2016 22:57:33 +0200 [thread overview]
Message-ID: <574A063D.5030700@weinigel.se> (raw)
In-Reply-To: <20160527183629.GO16172@sirena.org.uk>
On 05/27/2016 08:36 PM, Mark Brown wrote:
> Personally the way I parse this situation is that the kernel is taking
> a look at what's in the DT and making an effort to present it usefully
> in the running systems. Fixing our current interpretation in stone as
> a supported thing when we don't have to makes it more cumbersome to
> improve and discourages any efforts to do similar things in the
> future. It is reasonable to provide and document something here but
> when there's some fairly simple and obvious better things we could be
> doing it should be those rather than the legacy stuff.
So what are the "simple and obvious better things" that one can use instead?
/Christer
--
Have laptop, will travel. I'm a consultant looking for interesting
jobs anywhere in the world. I'm an experienced software engineer with
a solid understanding of hardware. Specialities: Linux, device
drivers and embedded systems in general. Find me at www.weinigel.se.
next prev parent reply other threads:[~2016-05-28 20:57 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 16:39 [PATCH] devicetree - document using aliases to set spi bus number Christer Weinigel
2016-05-24 17:20 ` Mark Brown
2016-05-24 18:03 ` Christer Weinigel
2016-05-24 18:32 ` Mark Brown
2016-05-24 18:57 ` Christer Weinigel
2016-05-25 12:19 ` Mark Rutland
2016-05-25 12:50 ` Mark Brown
2016-05-25 12:33 ` Mark Brown
2016-05-24 23:34 ` Frank Rowand
2016-05-25 0:18 ` Frank Rowand
2016-05-25 17:49 ` Rob Herring
2016-05-25 18:03 ` Mark Brown
2016-05-25 18:06 ` Frank Rowand
2016-05-25 18:44 ` Mark Brown
2016-05-26 1:10 ` Christer Weinigel
2016-05-26 1:44 ` Rob Herring
2016-05-26 1:56 ` Christer Weinigel
2016-05-26 10:07 ` Mark Brown
2016-05-26 10:58 ` Christer Weinigel
2016-05-26 18:47 ` Mark Brown
2016-05-26 21:04 ` Christer Weinigel
2016-05-27 16:43 ` Mark Brown
2016-05-24 17:41 ` Mark Rutland
2016-05-24 20:41 ` Frank Rowand
2016-05-25 9:20 ` Mark Rutland
2016-05-25 10:38 ` Mark Brown
2016-05-25 11:20 ` Christer Weinigel
2016-05-25 12:34 ` Mark Rutland
2016-05-25 13:08 ` Mark Brown
2016-05-25 15:32 ` Frank Rowand
2016-05-25 15:59 ` Mark Rutland
2016-05-25 16:21 ` Frank Rowand
2016-05-25 18:02 ` Mark Brown
2016-05-25 17:48 ` Mark Brown
2016-05-25 18:46 ` Frank Rowand
2016-05-27 18:36 ` Mark Brown
2016-05-28 20:57 ` Christer Weinigel [this message]
2016-05-30 16:13 ` Mark Brown
2016-05-25 15:25 ` Frank Rowand
2016-05-25 16:06 ` Mark Rutland
2016-05-25 16:31 ` Frank Rowand
2016-05-25 18:44 ` Rob Herring
2016-05-25 18:48 ` Mark Brown
2016-05-26 8:21 ` Geert Uytterhoeven
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=574A063D.5030700@weinigel.se \
--to=christer@weinigel.se \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mark.rutland@arm.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