From: Mark Brown <broonie@kernel.org> To: Mark Rutland <mark.rutland@arm.com> Cc: Frank Rowand <frowand.list@gmail.com>, Christer Weinigel <christer@weinigel.se>, 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 11:38:10 +0100 [thread overview] Message-ID: <20160525103810.GU8206@sirena.org.uk> (raw) In-Reply-To: <20160525092034.GE1337@leverpostej> [-- Attachment #1: Type: text/plain, Size: 953 bytes --] On Wed, May 25, 2016 at 10:20:34AM +0100, Mark Rutland wrote: > On Tue, May 24, 2016 at 01:41:26PM -0700, Frank Rowand wrote: > > The code and behavior is in the Linux kernel. It should be visible in > > the documentation instead of being a big mystery of how it works. > As above, I don't entirely agree. Mindlessly documenting existing Linux > behaviour can have the unfortuante effect of moving people towards the > wrong tool for the job. Yes, this is exactly my concern - the articulated use case (which didn't suprise me at all) is for using spidev which is itself not just Linux specific but this particular version of Linux right now specific. There are lots of things that happen to work but are in fact terrible ideas that leave messes for our future selves. We need to distinguish between things that are real, meaningful system descriptions and things that are implementation details resulting from the rush to force everyone on to DT. [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 473 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> To: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org> Cc: Frank Rowand <frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>, Christer Weinigel <christer-rKHMIqA5R6gwFerOooGFRg@public.gmane.org>, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Subject: Re: [PATCH] devicetree - document using aliases to set spi bus number. Date: Wed, 25 May 2016 11:38:10 +0100 [thread overview] Message-ID: <20160525103810.GU8206@sirena.org.uk> (raw) In-Reply-To: <20160525092034.GE1337@leverpostej> [-- Attachment #1: Type: text/plain, Size: 953 bytes --] On Wed, May 25, 2016 at 10:20:34AM +0100, Mark Rutland wrote: > On Tue, May 24, 2016 at 01:41:26PM -0700, Frank Rowand wrote: > > The code and behavior is in the Linux kernel. It should be visible in > > the documentation instead of being a big mystery of how it works. > As above, I don't entirely agree. Mindlessly documenting existing Linux > behaviour can have the unfortuante effect of moving people towards the > wrong tool for the job. Yes, this is exactly my concern - the articulated use case (which didn't suprise me at all) is for using spidev which is itself not just Linux specific but this particular version of Linux right now specific. There are lots of things that happen to work but are in fact terrible ideas that leave messes for our future selves. We need to distinguish between things that are real, meaningful system descriptions and things that are implementation details resulting from the rush to force everyone on to DT. [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-05-25 10:38 UTC|newest] Thread overview: 69+ 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 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-24 18:57 ` Christer Weinigel 2016-05-25 12:19 ` Mark Rutland 2016-05-25 12:19 ` Mark Rutland 2016-05-25 12:50 ` Mark Brown 2016-05-25 12:33 ` Mark Brown 2016-05-25 12:33 ` Mark Brown 2016-05-24 23:34 ` Frank Rowand 2016-05-24 23:34 ` Frank Rowand 2016-05-25 0:18 ` 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:44 ` Rob Herring 2016-05-26 1:56 ` Christer Weinigel 2016-05-26 10:07 ` Mark Brown 2016-05-26 10:07 ` Mark Brown 2016-05-26 10:58 ` Christer Weinigel 2016-05-26 18:47 ` Mark Brown 2016-05-26 18:47 ` Mark Brown 2016-05-26 21:04 ` Christer Weinigel 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 9:20 ` Mark Rutland 2016-05-25 10:38 ` Mark Brown [this message] 2016-05-25 10:38 ` Mark Brown 2016-05-25 11:20 ` Christer Weinigel 2016-05-25 12:34 ` Mark Rutland 2016-05-25 12:34 ` Mark Rutland 2016-05-25 13:08 ` Mark Brown 2016-05-25 13:08 ` Mark Brown 2016-05-25 15:32 ` Frank Rowand 2016-05-25 15:32 ` Frank Rowand 2016-05-25 15:59 ` Mark Rutland 2016-05-25 15:59 ` Mark Rutland 2016-05-25 16:21 ` Frank Rowand 2016-05-25 16:21 ` Frank Rowand 2016-05-25 18:02 ` Mark Brown 2016-05-25 17:48 ` 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-27 18:36 ` Mark Brown 2016-05-28 20:57 ` Christer Weinigel 2016-05-30 16:13 ` Mark Brown 2016-05-30 16:13 ` Mark Brown 2016-05-25 15:25 ` Frank Rowand 2016-05-25 15:25 ` Frank Rowand 2016-05-25 16:06 ` Mark Rutland 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:44 ` Rob Herring 2016-05-25 18:48 ` Mark Brown 2016-05-25 18:48 ` Mark Brown 2016-05-26 8:21 ` Geert Uytterhoeven 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=20160525103810.GU8206@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.