From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/2] watchdog: imx2_wdt: add external reset support via 'ext-reset-output' dt prop
Date: Thu, 31 Mar 2016 09:57:14 +0800 [thread overview]
Message-ID: <20160331015714.GM28207@tiger> (raw)
In-Reply-To: <20160330210916.GB21993@roeck-us.net>
On Wed, Mar 30, 2016 at 02:09:16PM -0700, Guenter Roeck wrote:
> The question was if the property name should be ext-reset-output or
> fsl,ext-reset-output. In my opinion, it should be fsl,ext-reset-output
> because it is not a generic property. Tim disagrees.
>
> So we have two options: Change the property name to fsl,ext-reset-output,
> which I would accept, or wait for a devicetree maintainer to make a decision.
Guenter,
I agree with you on this point. Before everyone agrees that this is a
generic binding, we should have vendor prefix for the property.
Tim,
This is a small change which, IMO, shouldn't hold an useful patch from being
merged. Care to resend with the suggested change?
Shawn
next prev parent reply other threads:[~2016-03-31 1:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 21:19 [PATCH v4 0/2] imx6: Implement external watchdog reset Akshay Bhat
2015-11-05 21:19 ` [PATCH v4 1/2] watchdog: imx2_wdt: add external reset support via 'ext-reset-output' dt prop Akshay Bhat
2015-11-05 22:23 ` Guenter Roeck
2015-11-06 19:53 ` Tim Harvey
2015-11-06 22:02 ` Guenter Roeck
2015-12-02 19:11 ` Akshay Bhat
2015-12-02 20:54 ` Tim Harvey
2015-12-17 15:02 ` Tim Harvey
2015-12-17 15:32 ` Guenter Roeck
[not found] ` <20151228162923.GA31680@spo001.leaseweb.nl>
2016-01-28 20:28 ` Akshay Bhat
2016-02-28 13:56 ` Fabio Estevam
2016-03-28 20:19 ` Akshay Bhat
2016-03-30 1:22 ` Shawn Guo
2016-03-30 21:09 ` Guenter Roeck
2016-03-31 1:57 ` Shawn Guo [this message]
2016-03-31 18:01 ` Tim Harvey
2016-04-01 1:39 ` Shawn Guo
2015-11-05 21:19 ` [PATCH v4 2/2] ARM: dts: ventana: Add ext-reset support Akshay Bhat
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=20160331015714.GM28207@tiger \
--to=shawnguo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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