From: Mark Brown <broonie@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Christer Weinigel <christer@weinigel.se>,
Frank Rowand <frowand.list@gmail.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: Wed, 25 May 2016 14:08:18 +0100 [thread overview]
Message-ID: <20160525130818.GY8206@sirena.org.uk> (raw)
In-Reply-To: <20160525123423.GL1337@leverpostej>
[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]
On Wed, May 25, 2016 at 01:34:24PM +0100, Mark Rutland wrote:
> On Wed, May 25, 2016 at 01:20:04PM +0200, Christer Weinigel wrote:
> > Does everything have to be so damn difficult?
> With the varied hardware that exists, and the constant expansion of the
> set of things which exist, there is very little that is simple any more.
> Things which are simple today can become alarming non-simple tomorrow,
> with only minor changes. So unfortunately, yes.
> I appreciate that it can feel like all the feedback has been negative,
> and that can be especially annoying given that you did not write the
> code in question. Please be aware that we are trying to work in your
> best interests, along with the best interests of many others who are
> using this code and binding today, or may in future.
> Specification work is a difficult, tiring process for all involved, for
> anything meaningful.
Right, this is one of the costs that the community decided to take on
when it decided to move away from platform devices to push everything
into DT as an ABI. Things that are fine as platform data internal to
the kernel aren't so good as OS neutral ABIs.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-05-25 13:08 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 16:39 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 [this message]
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
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=20160525130818.GY8206@sirena.org.uk \
--to=broonie@kernel.org \
--cc=christer@weinigel.se \
--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
all inboxes | Powered by JetHome®