From: Matthew Garrett <matthew.garrett@nebula.com>
To: "gsi@denx.de" <gsi@denx.de>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kishon@ti.com" <kishon@ti.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH] net/dt: Add support for overriding phy configuration from device tree
Date: Thu, 16 Jan 2014 14:40:04 +0000 [thread overview]
Message-ID: <1389883203.3720.7.camel@x230> (raw)
In-Reply-To: <20140116135905.GV20094@book.gsilab.sittig.org>
On Thu, 2014-01-16 at 14:59 +0100, Gerhard Sittig wrote:
> These properties are booleans, and optional? Does it mean that
> you cannot _disable_ broken features? Or does it mean that you
> _must_ specify the non-broken features and thus break backwards
> compatibility? Or are these properties not boolean (they are not
> used in the example either, unfortunately), and the binding text
> would need an update for clarity? What am I missing?
They're not booleans. I'll update the text to make that clear.
--
Matthew Garrett <matthew.garrett@nebula.com>
next prev parent reply other threads:[~2014-01-16 14:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 21:38 [PATCH] net/dt: Add support for overriding phy configuration from device tree Matthew Garrett
2014-01-16 13:59 ` Gerhard Sittig
2014-01-16 14:40 ` Matthew Garrett [this message]
[not found] ` <20140116135905.GV20094-kDjWylLy9wD0K7fsECOQyeGNnDKD8DIp@public.gmane.org>
2014-01-16 14:47 ` [PATCH V2] " Matthew Garrett
[not found] ` <1389883631-1480-1-git-send-email-matthew.garrett-05XSO3Yj/JvQT0dZR+AlfA@public.gmane.org>
2014-01-16 15:16 ` Arnd Bergmann
[not found] ` < 1389999459-9483-1-git-send-email-matthew.garrett@nebula.com>
2014-01-17 22:57 ` [PATCH V3] " Matthew Garrett
2014-01-19 15:34 ` Ben Hutchings
[not found] ` <1390145654.16433.102.camel-nDn/Rdv9kqW9Jme8/bJn5UCKIB8iOfG2tUK59QYPAWc@public.gmane.org>
2014-02-04 19:01 ` Florian Fainelli
2014-02-04 17:15 ` Grant Likely
2014-02-04 20:39 ` Florian Fainelli
2014-02-04 21:40 ` Ben Hutchings
2014-02-04 22:48 ` Florian Fainelli
2014-02-05 9:47 ` Grant Likely
2014-02-05 9:51 ` David Laight
[not found] ` <063D6719AE5E284EB5DD2968C1650D6D0F6B8BCA-VkEWCZq2GCInGFn1LkZF6NBPR1lH4CV8@public.gmane.org>
2014-02-07 22:43 ` Florian Fainelli
2014-02-10 16:14 ` Gerlando Falauto
[not found] ` <52F8FB03.6040606-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
2014-02-10 17:09 ` Florian Fainelli
2014-02-11 9:09 ` Gerlando Falauto
[not found] ` <52F9E8E6.1090006-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
2014-02-11 17:43 ` Florian Fainelli
2014-02-12 8:57 ` Gerlando Falauto
2014-07-10 12:37 ` Gerlando Falauto
[not found] ` <53BE8912.4090804-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
2014-07-22 23:40 ` Florian Fainelli
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=1389883203.3720.7.camel@x230 \
--to=matthew.garrett@nebula.com \
--cc=devicetree@vger.kernel.org \
--cc=gsi@denx.de \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).