From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Generic RTC class support for ppc_md.[gs]et_rtc_time
Date: Tue, 04 Dec 2007 07:45:22 +1100 [thread overview]
Message-ID: <1196714722.13230.224.camel@pasglop> (raw)
In-Reply-To: <1196701493.13978.163.camel@pmac.infradead.org>
On Mon, 2007-12-03 at 17:04 +0000, David Woodhouse wrote:
> It would be good to migrate the platform code to register RTC devices
> directly, but for now this will make them functional enough for most
> purposes...
Wouldn't it be best to do the other way around at some stage ?
We need to solve the problem of ppc_md. stuff being called by the core
in atomic contexts first though.
Ben.
next prev parent reply other threads:[~2007-12-03 20:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 17:04 [PATCH] Generic RTC class support for ppc_md.[gs]et_rtc_time David Woodhouse
2007-12-03 20:45 ` Benjamin Herrenschmidt [this message]
2007-12-03 21:06 ` David Woodhouse
2007-12-03 22:36 ` Benjamin Herrenschmidt
2007-12-03 22:44 ` David Woodhouse
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=1196714722.13230.224.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=dwmw2@infradead.org \
--cc=linuxppc-dev@ozlabs.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).