From: fixed-term.Oleksij.Rempel <fixed-term.Oleksij.Rempel@de.bosch.com>
To: Mark Brown <broonie@kernel.org>, Oleksij Rempel <linux@rempel-privat.de>
Cc: geert@linux-m68k.org, dirk.behme@de.bosch.com,
linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
robh+dt@kernel.org
Subject: Re: [PATCH 3/6] DT: add documentation for spi-fc-test driver
Date: Wed, 2 Mar 2016 07:24:00 +0100 [thread overview]
Message-ID: <56D68700.1020302@de.bosch.com> (raw)
In-Reply-To: <20160302021755.GQ18327@sirena.org.uk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 02.03.2016 03:17, Mark Brown wrote:
> On Tue, Mar 01, 2016 at 03:43:17PM +0100, Oleksij Rempel wrote:
>
>> .../devicetree/bindings/spi/spi-fc-test.txt | 30
>> ++++++++++++++++++++++
>
> We should not be supporting DT bindings for a test device that
> doesn't represent physical hardware, this is an invitation to abuse
> by people writing bad DT bindings for actual hardware.
>
Ok, i'll try to reimplement it with module parameters.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iF4EAREIAAYFAlbWhwAACgkQHwImuRkmbWlOOwEAgarzmDA119XNTrZOKDB4OtJW
J8j0WM80sbRwK9DvNQkA/2lYbFeQgS2hhcirvxB6vMr6/5C77sm0evfv/UAZrDqA
=d2kY
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2016-03-02 6:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 12:04 [PATCH RFC] spi: add flow controll support Oleksij Rempel
[not found] ` <1456747459-8559-1-git-send-email-linux-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
2016-02-29 12:14 ` Geert Uytterhoeven
[not found] ` <56D448E1.6090006@de.bosch.com>
[not found] ` <56D448E1.6090006-V5te9oGctAVWk0Htik3J/w@public.gmane.org>
2016-02-29 13:46 ` Geert Uytterhoeven
2016-03-01 14:43 ` [PATCH 1/6] " Oleksij Rempel
[not found] ` <1456843400-20696-1-git-send-email-linux-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
2016-03-01 14:43 ` [PATCH 2/6] spi: add add flow control test driver Oleksij Rempel
2016-03-01 14:43 ` [PATCH 3/6] DT: add documentation for spi-fc-test driver Oleksij Rempel
[not found] ` <1456843400-20696-3-git-send-email-linux-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
2016-03-02 2:17 ` Mark Brown
2016-03-02 6:24 ` fixed-term.Oleksij.Rempel [this message]
2016-03-01 14:43 ` [PATCH 4/6] spi: davinci: set new SPI_FC_* flags Oleksij Rempel
[not found] ` <1456843400-20696-4-git-send-email-linux-YEK0n+YFykbzxQdaRaTXBw@public.gmane.org>
2016-03-02 2:16 ` Mark Brown
2016-03-02 6:25 ` fixed-term.Oleksij.Rempel
[not found] ` <56D68754.3090405-V5te9oGctAVWk0Htik3J/w@public.gmane.org>
2016-03-02 10:48 ` Mark Brown
2016-03-02 6:57 ` fixed-term.Oleksij.Rempel
2016-03-01 14:43 ` [PATCH 5/6] spi: sun4i: " Oleksij Rempel
2016-03-01 14:43 ` [PATCH 6/6] spi: bitbang: " Oleksij Rempel
2016-03-02 1:32 ` [PATCH 1/6] spi: add flow controll support Mark Brown
2016-03-02 2:46 ` Mark Brown
2016-03-02 6:48 ` fixed-term.Oleksij.Rempel
[not found] ` <56D68CD7.8000203-V5te9oGctAVWk0Htik3J/w@public.gmane.org>
2016-03-02 10:55 ` Mark Brown
2016-03-02 11:21 ` fixed-term.Oleksij.Rempel
2016-03-02 12:26 ` Martin Sperl
2016-03-02 14:26 ` fixed-term.Oleksij.Rempel
2016-02-29 13:11 ` [PATCH RFC] " Martin Sperl
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=56D68700.1020302@de.bosch.com \
--to=fixed-term.oleksij.rempel@de.bosch.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dirk.behme@de.bosch.com \
--cc=geert@linux-m68k.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=robh+dt@kernel.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 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.