linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Greg Ungerer <gerg@snapgear.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Greg Ungerer <gerg@uclinux.org>,
	uClinux development list <uclinux-dev@uclinux.org>
Subject: Re: [PATCH 6/8] clocksource: m86k: Convert to clocksource_register_hz/khz
Date: Wed, 26 Oct 2011 10:57:40 -0700	[thread overview]
Message-ID: <1319651860.23224.3.camel@work-vm> (raw)
In-Reply-To: <4EA79629.3040403@snapgear.com>

On Wed, 2011-10-26 at 15:10 +1000, Greg Ungerer wrote:
> Hi John,
> 
> On 26/10/11 04:46, john stultz wrote:
> > Updated to merge the valid bits of the two m68k patches.
> >
> > This converts the m86k clocksources to use clocksource_register_hz/khz
> >
> > This is untested, so any assistance in testing would be appreciated!
> 
> This looks good. I test compiled across all targets these files affect.
> And run tested on ColdFire/5208 (which uses pit.c).

Thanks for testing! I really appreciate it!

> 
> > CC: Geert Uytterhoeven<geert@linux-m68k.org>
> > CC: Greg Ungerer<gerg@uclinux.org>
> > Signed-off-by: John Stultz<johnstul@us.ibm.com>
> 
> Acked-by: Greg Ungerer <gerg@uclinux.org>
> 
> Do you want me to push these via the m68knommu git tree?

I'd prefer it go through either one of the m68k trees.

thanks
-john


  reply	other threads:[~2011-10-26 17:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4ea6fbe8.43310e0a.592c.5416SMTPIN_ADDED@mx.google.com>
2011-10-25 18:35 ` [PATCH 6/8] clocksource: m86knommu: Convert to clocksource_register_hz/khz Geert Uytterhoeven
2011-10-25 18:39   ` john stultz
2011-10-25 18:46   ` [PATCH 6/8] clocksource: m86k: " john stultz
2011-10-26  5:10     ` Greg Ungerer
2011-10-26 17:57       ` john stultz [this message]
2011-10-27  4:15         ` Greg Ungerer

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=1319651860.23224.3.camel@work-vm \
    --to=johnstul@us.ibm.com \
    --cc=geert@linux-m68k.org \
    --cc=gerg@snapgear.com \
    --cc=gerg@uclinux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=uclinux-dev@uclinux.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).