From: l.stach@pengutronix.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: imx6: tag boards that have the HW workaround for ERR006687
Date: Thu, 02 Jun 2016 10:25:06 +0200 [thread overview]
Message-ID: <1464855906.9501.1.camel@pengutronix.de> (raw)
In-Reply-To: <20160601161729.GB19428@n2100.arm.linux.org.uk>
Am Mittwoch, den 01.06.2016, 17:17 +0100 schrieb Russell King - ARM
Linux:
> On Wed, Jun 01, 2016 at 05:29:43PM +0200, Lucas Stach wrote:
> > @@ -97,6 +97,7 @@
> > phy-reset-gpios = <&gpio3 31 0>;
> > interrupts-extended = <&gpio1 6 IRQ_TYPE_LEVEL_HIGH>,
> > <&intc 0 119 IRQ_TYPE_LEVEL_HIGH>;
> > + fsl,err006687-war-present;
>
> war? Any reason not to spell it out, or use the more natural
> abbreviation "wa"?
>
Apparently I've read too many documents where WAR is the abbreviation
for workaround, so it felt completely natural to me. I agree that it
would make sense to just spell it out to avoid any confusion.
Regards,
Lucas
WARNING: multiple messages have this Message-ID (diff)
From: Lucas Stach <l.stach-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Russell King - ARM Linux <linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org>
Cc: Shawn Guo <shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Fugang Duan <fugang.duan-3arQi8VN3Tc@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
patchwork-lst-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org,
kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 2/2] ARM: dts: imx6: tag boards that have the HW workaround for ERR006687
Date: Thu, 02 Jun 2016 10:25:06 +0200 [thread overview]
Message-ID: <1464855906.9501.1.camel@pengutronix.de> (raw)
In-Reply-To: <20160601161729.GB19428-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
Am Mittwoch, den 01.06.2016, 17:17 +0100 schrieb Russell King - ARM
Linux:
> On Wed, Jun 01, 2016 at 05:29:43PM +0200, Lucas Stach wrote:
> > @@ -97,6 +97,7 @@
> > phy-reset-gpios = <&gpio3 31 0>;
> > interrupts-extended = <&gpio1 6 IRQ_TYPE_LEVEL_HIGH>,
> > <&intc 0 119 IRQ_TYPE_LEVEL_HIGH>;
> > + fsl,err006687-war-present;
>
> war? Any reason not to spell it out, or use the more natural
> abbreviation "wa"?
>
Apparently I've read too many documents where WAR is the abbreviation
for workaround, so it felt completely natural to me. I agree that it
would make sense to just spell it out to avoid any confusion.
Regards,
Lucas
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-06-02 8:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 15:29 [PATCH 0/2] Software workaround for i.MX6Q/DL ERR006687 Lucas Stach
2016-06-01 15:29 ` Lucas Stach
2016-06-01 15:29 ` [PATCH 1/2] ARM: imx6: disable deeper idle states when FEC is active w/o HW workaround Lucas Stach
2016-06-01 15:29 ` Lucas Stach
2016-06-16 15:47 ` Arnd Bergmann
2016-06-16 15:47 ` Arnd Bergmann
2016-06-21 2:40 ` Shawn Guo
2016-06-21 2:40 ` Shawn Guo
2016-06-01 15:29 ` [PATCH 2/2] ARM: dts: imx6: tag boards that have the HW workaround for ERR006687 Lucas Stach
2016-06-01 15:29 ` Lucas Stach
2016-06-01 16:17 ` Russell King - ARM Linux
2016-06-01 16:17 ` Russell King - ARM Linux
2016-06-02 8:25 ` Lucas Stach [this message]
2016-06-02 8:25 ` Lucas Stach
2016-06-07 19:46 ` Joshua Clayton
2016-06-07 19:46 ` Joshua Clayton
2016-06-13 11:03 ` Lucas Stach
2016-06-13 11:03 ` Lucas Stach
2016-06-02 19:10 ` [PATCH 0/2] Software workaround for i.MX6Q/DL ERR006687 David Miller
2016-06-02 19:10 ` David Miller
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=1464855906.9501.1.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--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 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.