[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VchzVZVs=6dpG38_fFvApJ-1oiKSEBMVYm+W_5FS-2pCQ@mail.gmail.com>
Date: Thu, 21 Dec 2017 16:09:55 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Bartosz Golaszewski <brgl@...ev.pl>
Cc: Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Javier Martinez Canillas <javier@...hile0.org>,
David Lechner <david@...hnology.com>,
Divagar Mohandass <divagar.mohandass@...el.com>,
linux-i2c <linux-i2c@...r.kernel.org>,
devicetree <devicetree@...r.kernel.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/5] dt-bindings: at24: consistently document the
compatible property
On Thu, Dec 21, 2017 at 3:48 PM, Bartosz Golaszewski <brgl@...ev.pl> wrote:
> Current description of the compatible property for at24 is quite vague.
>
> Specify an exact list of accepted compatibles and document the - now
> deprecated - strings which were previously used in device tree files.
> + will still work, but are now deprecated.
I would rather reprase it to make people not think that's okay to
still use deprecated strings.
Something like
"are now deprecated, please do not use in new code or drivers".
Supporting old but deprecated is implied by DT globally.
(We don't break user space, remember?)
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists