linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nbowler@elliptictech.com (Nick Bowler)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] SP805 updates for Versatile Express
Date: Fri, 22 Jul 2011 15:01:50 -0400	[thread overview]
Message-ID: <20110722190150.GA24621@elliptictech.com> (raw)
In-Reply-To: <20110722183146.GE31767@infomag.iguana.be>

On 2011-07-22 20:31 +0200, Wim Van Sebroeck wrote:
> Hi Nick, Russel,
> > Indeed, there are likely several other ways in which this driver can be
> > improved.  My goal was to get it working on our board first. :)
> 
> Feel free to continue improving the driver like Russel suggested. :-)

I'll see what I can do :)

> > So if this series is fine, I'll submit #1 (the V2M patch) to Russel's
> > patch tracker.  I suppose #2 and #3 should go through the watchdog tree?
> 
> I added patch 2 and 3 to linux-2.6-watchdog-next. You can send #1 to 
> Russel's patch tracker.

OK, great.  I sent #1 to Russell's patch tracker a couple days ago.

Thanks,
-- 
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)

      reply	other threads:[~2011-07-22 19:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-15 15:03 [PATCH 0/3] SP805 updates for Versatile Express Nick Bowler
2011-07-15 15:04 ` [PATCH 1/3] ARM: vexpress: Add clock definition for the SP805 Nick Bowler
2011-07-15 15:04 ` [PATCH 2/3] watchdog: sp805: Don't write 0 to the load value register Nick Bowler
2011-07-15 15:04 ` [PATCH 3/3] watchdog: sp805: Flush posted writes in enable/disable Nick Bowler
2011-07-15 20:59 ` [PATCH 0/3] SP805 updates for Versatile Express Wim Van Sebroeck
2011-07-18  9:44   ` Russell King - ARM Linux
2011-07-19 13:15     ` Nick Bowler
2011-07-22 18:31       ` Wim Van Sebroeck
2011-07-22 19:01         ` Nick Bowler [this message]

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=20110722190150.GA24621@elliptictech.com \
    --to=nbowler@elliptictech.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).