From: rob@landley.net (Rob Landley)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND] Documentation: devicetree: Fix value format description
Date: Sat, 05 May 2012 13:44:20 -0500 [thread overview]
Message-ID: <4FA57504.2070308@landley.net> (raw)
In-Reply-To: <1336217886-27224-1-git-send-email-stigge@antcom.de>
On 05/05/2012 06:38 AM, Roland Stigge wrote:
> Numeric values in dts files can be specified in decimal and hex (the latter
> prefixed 0x). The current documentation is updated with this patch to prevent
> confusion about what is meant with values without "0x" (previously hex, now
> dec).
This updates the documentation to consistently say 0x in front of hex
values, but doesn't change the device tree _parser_. What did the parser
previously do with this input?
> Signed-off-by: Roland Stigge <stigge@antcom.de>
Acked-by: Rob Landley <rob@landley.net>
Should I track this one, or is Grant taking it in the device device tree
tree?
Rob
--
GNU/Linux isn't: Linux=GPLv2, GNU=GPLv3+, they can't share code.
Either it's "mere aggregation", or a license violation. Pick one.
WARNING: multiple messages have this Message-ID (diff)
From: Rob Landley <rob-VoJi6FS/r0vR7s880joybQ@public.gmane.org>
To: Roland Stigge <stigge-uj/7R2tJ6VmzQB+pC5nmwQ@public.gmane.org>
Cc: linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org,
rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH RESEND] Documentation: devicetree: Fix value format description
Date: Sat, 05 May 2012 13:44:20 -0500 [thread overview]
Message-ID: <4FA57504.2070308@landley.net> (raw)
In-Reply-To: <1336217886-27224-1-git-send-email-stigge-uj/7R2tJ6VmzQB+pC5nmwQ@public.gmane.org>
On 05/05/2012 06:38 AM, Roland Stigge wrote:
> Numeric values in dts files can be specified in decimal and hex (the latter
> prefixed 0x). The current documentation is updated with this patch to prevent
> confusion about what is meant with values without "0x" (previously hex, now
> dec).
This updates the documentation to consistently say 0x in front of hex
values, but doesn't change the device tree _parser_. What did the parser
previously do with this input?
> Signed-off-by: Roland Stigge <stigge-uj/7R2tJ6VmzQB+pC5nmwQ@public.gmane.org>
Acked-by: Rob Landley <rob-VoJi6FS/r0vR7s880joybQ@public.gmane.org>
Should I track this one, or is Grant taking it in the device device tree
tree?
Rob
--
GNU/Linux isn't: Linux=GPLv2, GNU=GPLv3+, they can't share code.
Either it's "mere aggregation", or a license violation. Pick one.
WARNING: multiple messages have this Message-ID (diff)
From: Rob Landley <rob@landley.net>
To: Roland Stigge <stigge@antcom.de>
Cc: devicetree-discuss@lists.ozlabs.org, grant.likely@secretlab.ca,
rob.herring@calxeda.com, rdunlap@xenotime.net,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
w.sang@pengutronix.de, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RESEND] Documentation: devicetree: Fix value format description
Date: Sat, 05 May 2012 13:44:20 -0500 [thread overview]
Message-ID: <4FA57504.2070308@landley.net> (raw)
In-Reply-To: <1336217886-27224-1-git-send-email-stigge@antcom.de>
On 05/05/2012 06:38 AM, Roland Stigge wrote:
> Numeric values in dts files can be specified in decimal and hex (the latter
> prefixed 0x). The current documentation is updated with this patch to prevent
> confusion about what is meant with values without "0x" (previously hex, now
> dec).
This updates the documentation to consistently say 0x in front of hex
values, but doesn't change the device tree _parser_. What did the parser
previously do with this input?
> Signed-off-by: Roland Stigge <stigge@antcom.de>
Acked-by: Rob Landley <rob@landley.net>
Should I track this one, or is Grant taking it in the device device tree
tree?
Rob
--
GNU/Linux isn't: Linux=GPLv2, GNU=GPLv3+, they can't share code.
Either it's "mere aggregation", or a license violation. Pick one.
next prev parent reply other threads:[~2012-05-05 18:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-05 11:38 [PATCH RESEND] Documentation: devicetree: Fix value format description Roland Stigge
2012-05-05 11:38 ` Roland Stigge
2012-05-05 11:38 ` Roland Stigge
2012-05-05 18:44 ` Rob Landley [this message]
2012-05-05 18:44 ` Rob Landley
2012-05-05 18:44 ` Rob Landley
2012-05-06 8:02 ` Roland Stigge
2012-05-06 8:02 ` Roland Stigge
-- strict thread matches above, loose matches on Subject: below --
2012-05-16 20:33 Roland Stigge
2012-05-16 20:33 ` Roland Stigge
2012-05-17 1:09 ` Rob Landley
2012-05-17 1:09 ` Rob Landley
2012-05-19 21:03 ` Grant Likely
2012-05-19 21:03 ` Grant Likely
2012-05-19 21:03 ` Grant Likely
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=4FA57504.2070308@landley.net \
--to=rob@landley.net \
--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.