Devicetree
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: devicetree@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: deprecate trivial-devices.txt for i2c
Date: Wed, 1 Feb 2017 07:48:52 -0600	[thread overview]
Message-ID: <20170201134852.o5qbd73plz6ds66j@rob-hp-laptop> (raw)
In-Reply-To: <20170126225544.5431-2-wsa@the-dreams.de>

On Thu, Jan 26, 2017 at 11:55:43PM +0100, Wolfram Sang wrote:
> The idea to collect trivial devices in a seperate file is coming from
> the early DT days and turned out to be a bad decision. It regularly
> creates maintenance pain and the information is not where users would
> expect it (i2c folder is for i2c bus drivers not clients). Also, we do
> not maintain such a file for other subsystems, so we should put an end
> to this as well. First step is to deprecate it and mention that it
> should be refactored into proper bindings.
> 
> Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
> ---
>  Documentation/devicetree/bindings/i2c/trivial-devices.txt | 10 +++++++---
>  1 file changed, 7 insertions(+), 3 deletions(-)

Actually, I prefer to keep it. Move it up a level and I will take 
patches for it.

Rob

  reply	other threads:[~2017-02-01 13:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-26 22:55 [PATCH 0/2] dt-bindings: deprecate and move i2c/trivial-devices.txt Wolfram Sang
2017-01-26 22:55 ` [PATCH 1/2] dt-bindings: deprecate trivial-devices.txt for i2c Wolfram Sang
2017-02-01 13:48   ` Rob Herring [this message]
     [not found] ` <20170126225544.5431-1-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2017-01-26 22:55   ` [PATCH 2/2] dt-bindings: move trivial devices out of i2c subdir Wolfram Sang
2017-02-01 13:50     ` Rob Herring
2017-02-01 18:35       ` Wolfram Sang
2017-02-07 11:08         ` Wolfram Sang
2017-02-07 15:46           ` Rob Herring

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=20170201134852.o5qbd73plz6ds66j@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=wsa@the-dreams.de \
    /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