linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: csd@broadcom.com (Christian Daudt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM dts: bcm281xx: use preprocessor for device trees
Date: Tue, 11 Jun 2013 09:56:45 -0700	[thread overview]
Message-ID: <51B756CD.1070500@broadcom.com> (raw)
In-Reply-To: <20130611070344.GF6688@quad.lixom.net>

On 13-06-11 12:03 AM, Olof Johansson wrote:
> On Thu, Jun 06, 2013 at 01:41:33AM -0400, Matt Porter wrote:
>> This series follows the same approach as taken on Tegra and
>> OMAP DT files to use the C preprocessor in order to improve
>> readability. Since bcm281xx does not yet have gpio and pinctrl
>> support, this series just enables the C preprocessor and removes
>> the magic constants from existing irq properties. Any new
>> additions can come in using human readable definitions.
>>
>> The resulting dtb was diff-tested to validate it versus the non
>> preprocessed dts version.
>>
>> Matt Porter (2):
>>    ARM: dts: bcm281xx: use #include for device tree files
>>    ARM: dts: bcm281xx: use existing defines for irqs
> Acked-by: Olof Johansson <olof@lixom.net>
Acked-by: Christian Daudt <csd@broadcom.com>
>
> Not sure what else you'll have for 3.11 devicetree-wise, Christian -- your
> choice if you want to send a pull request or ack these and we'll apply them
> directly.
>
I can add them to my tree. I already have a pending dt commit to push.

  thanks,
    csd

  reply	other threads:[~2013-06-11 16:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-06  5:41 [PATCH 0/2] ARM dts: bcm281xx: use preprocessor for device trees Matt Porter
2013-06-06  5:41 ` [PATCH 1/2] ARM: dts: bcm281xx: use #include for device tree files Matt Porter
2013-06-06  5:41 ` [PATCH 2/2] ARM: dts: bcm281xx: use existing defines for irqs Matt Porter
2013-06-11  7:03 ` [PATCH 0/2] ARM dts: bcm281xx: use preprocessor for device trees Olof Johansson
2013-06-11 16:56   ` Christian Daudt [this message]
2013-06-11 23:40     ` Olof Johansson

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=51B756CD.1070500@broadcom.com \
    --to=csd@broadcom.com \
    --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;
as well as URLs for NNTP newsgroup(s).