devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Jamie Iles <jamie@jamieiles.com>
Cc: devicetree-discuss@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] Add device tree based initialisation for VIC
Date: Mon, 25 Jul 2011 13:54:23 -0600	[thread overview]
Message-ID: <20110725195423.GA26735@ponder.secretlab.ca> (raw)
In-Reply-To: <1311610200-12408-1-git-send-email-jamie@jamieiles.com>

On Mon, Jul 25, 2011 at 05:09:57PM +0100, Jamie Iles wrote:
> This series aims to allow VIC devices to be probed from the device tree.
> Currently the only in-tree device tree enabled user of the VIC is versatile,
> but I'll shortly submit patches for picoxcell on device tree that uses 2
> VIC's.
> 
> I've split this into 3 patches for bisectability, but this could be fairly
> squashed into 2.

I always prefer fewer patches.  Which 2 patches would you squash
together?  :-)

> 
> Jamie Iles (3):
>   vic: add device tree bindings
>   versatile dt: set the irq-start property for the vic
>   versatile: convert to common VIC DT probing
> 
>  Documentation/devicetree/bindings/arm/vic.txt |   21 +++++++++++++++
>  arch/arm/boot/dts/versatile-ab.dts            |    1 +
>  arch/arm/common/vic.c                         |   35 +++++++++++++++++++++++++
>  arch/arm/include/asm/hardware/vic.h           |    5 +++
>  arch/arm/mach-versatile/core.c                |    9 +-----
>  5 files changed, 63 insertions(+), 8 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/arm/vic.txt
> 
> -- 
> 1.7.4.1
> 
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2011-07-25 19:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-25 16:09 [PATCH 0/3] Add device tree based initialisation for VIC Jamie Iles
     [not found] ` <1311610200-12408-1-git-send-email-jamie-wmLquQDDieKakBO8gow8eQ@public.gmane.org>
2011-07-25 16:09   ` [PATCH 1/3] vic: add device tree bindings Jamie Iles
     [not found]     ` <1311610200-12408-2-git-send-email-jamie-wmLquQDDieKakBO8gow8eQ@public.gmane.org>
2011-07-25 20:04       ` Grant Likely
     [not found]         ` <20110725200434.GB26735-e0URQFbLeQY2iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
2011-07-25 22:31           ` Jamie Iles
2011-07-31  4:11             ` Grant Likely
     [not found]               ` <20110731041107.GN24334-e0URQFbLeQY2iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
2011-07-31 15:27                 ` Jamie Iles
2011-07-25 16:09   ` [PATCH 2/3] versatile dt: set the irq-start property for the vic Jamie Iles
2011-07-25 16:10   ` [PATCH 3/3] versatile: convert to common VIC DT probing Jamie Iles
2011-07-25 19:54 ` Grant Likely [this message]
2011-07-25 22:20   ` [PATCH 0/3] Add device tree based initialisation for VIC Jamie Iles

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=20110725195423.GA26735@ponder.secretlab.ca \
    --to=grant.likely@secretlab.ca \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=jamie@jamieiles.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).