From: jamie@jamieiles.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Add device tree based initialisation for VIC
Date: Mon, 25 Jul 2011 23:20:42 +0100 [thread overview]
Message-ID: <20110725222041.GA3001@gallagher> (raw)
In-Reply-To: <20110725195423.GA26735@ponder.secretlab.ca>
On Mon, Jul 25, 2011 at 01:54:23PM -0600, Grant Likely wrote:
> 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? :-)
The conversion for versatile could go into one patch, but I'm not sure it
would bisect as easily (I guess that's more important though).
Jamie
WARNING: multiple messages have this Message-ID (diff)
From: Jamie Iles <jamie@jamieiles.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Jamie Iles <jamie@jamieiles.com>,
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 23:20:42 +0100 [thread overview]
Message-ID: <20110725222041.GA3001@gallagher> (raw)
In-Reply-To: <20110725195423.GA26735@ponder.secretlab.ca>
On Mon, Jul 25, 2011 at 01:54:23PM -0600, Grant Likely wrote:
> 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? :-)
The conversion for versatile could go into one patch, but I'm not sure it
would bisect as easily (I guess that's more important though).
Jamie
next prev parent reply other threads:[~2011-07-25 22:20 UTC|newest]
Thread overview: 20+ 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
2011-07-25 16:09 ` Jamie Iles
2011-07-25 16:09 ` [PATCH 1/3] vic: add device tree bindings Jamie Iles
2011-07-25 16:09 ` Jamie Iles
2011-07-25 20:04 ` Grant Likely
2011-07-25 20:04 ` Grant Likely
2011-07-25 22:31 ` Jamie Iles
2011-07-25 22:31 ` Jamie Iles
2011-07-31 4:11 ` Grant Likely
2011-07-31 4:11 ` Grant Likely
2011-07-31 15:27 ` Jamie Iles
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:09 ` Jamie Iles
2011-07-25 16:10 ` [PATCH 3/3] versatile: convert to common VIC DT probing Jamie Iles
2011-07-25 16:10 ` Jamie Iles
2011-07-25 19:54 ` [PATCH 0/3] Add device tree based initialisation for VIC Grant Likely
2011-07-25 19:54 ` Grant Likely
2011-07-25 22:20 ` Jamie Iles [this message]
2011-07-25 22:20 ` 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=20110725222041.GA3001@gallagher \
--to=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 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.