All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	linux-arch@vger.kernel.org, mturquette@ti.com,
	Russell King <linux@arm.linux.org.uk>,
	linux-kbuild@vger.kernel.org, Michal Marek <mmarek@suse.cz>
Subject: Re: [PATCH] clkdev: Add default clkdev.h
Date: Tue, 3 Jul 2012 23:15:55 +1000	[thread overview]
Message-ID: <20120703231555.b675da0eb648cbb2c7fecf41@canb.auug.org.au> (raw)
In-Reply-To: <20120703123322.GK29030@opensource.wolfsonmicro.com>

[-- Attachment #1: Type: text/plain, Size: 915 bytes --]

Hi Mark,

On Tue, 3 Jul 2012 13:33:22 +0100 Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:
>
> On Tue, Jul 03, 2012 at 10:05:12PM +1000, Stephen Rothwell wrote:
> > On Tue, 3 Jul 2012 12:48:44 +0100 Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:
> 
> > > The reason I'm doing this is that the lack of a widely available clock
> > > API is a considerable pain point for a lot of the stuff I work on and
> > > this is the major blocker to just enabling the default implementation on
> > > architectures that don't support it already which would be a big step
> > > forwards.
> 
> > Agreed.  Please submit this patch and we can concentrate on this other
> > stuff later.
> 
> Perhaps if you give me a couple of hours...

Sorry, I wasn't meaning to rush you, just agreeing that the two things
are separate.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-07-03 13:16 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-02 18:04 [PATCH] clkdev: Add default clkdev.h Mark Brown
2012-07-03  2:00 ` Stephen Rothwell
2012-07-03 10:12   ` Mark Brown
2012-07-03 11:16     ` Arnd Bergmann
2012-07-03 11:48       ` Mark Brown
2012-07-03 12:05         ` Stephen Rothwell
2012-07-03 12:33           ` Mark Brown
2012-07-03 13:15             ` Stephen Rothwell [this message]
2012-07-03 13:39           ` Arnd Bergmann
2012-07-03 13:47             ` Mark Brown
2012-07-09 22:23               ` Mike Turquette
2012-07-09 23:30                 ` Russell King - ARM Linux
2012-07-10 17:22                   ` Mark Brown
2012-07-10 18:07                     ` Arnd Bergmann
2012-07-11  2:44                       ` Paul Mundt
2012-07-11  6:32                         ` Arnd Bergmann
  -- strict thread matches above, loose matches on Subject: below --
2012-09-05  4:04 Mark Brown
2012-08-28 18:56 Mark Brown
2012-08-25 18:16 Mark Brown
2012-07-03 17:04 Mark Brown
2012-07-03 22:07 ` Stephen Rothwell
2012-07-03 15:23 Mark Brown
2012-07-03 15:29 ` Stephen Rothwell
2012-07-04  8:00 ` Geert Uytterhoeven
2012-07-04  9:22   ` Mark Brown
2012-06-14 11:22 Mark Brown
2012-05-14 14:19 Mark Brown
2012-05-14 14:19 ` Mark Brown
2012-05-14 19:03 ` Arnd Bergmann
2012-05-14 19:03   ` Arnd Bergmann
2012-05-14 19:09   ` Mark Brown
2012-05-14 19:09     ` Mark Brown

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=20120703231555.b675da0eb648cbb2c7fecf41@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=arnd@arndb.de \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mmarek@suse.cz \
    --cc=mturquette@ti.com \
    /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.