From: Dan Malek <dan@mvista.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: "David M?ller (ELSOFT AG)" <d.mueller@elsoft.ch>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: [PATCH] Various patches against linuxppc_dev-2.4.14-pre7
Date: Mon, 05 Nov 2001 12:05:41 -0500 [thread overview]
Message-ID: <3BE6C6E5.7070505@mvista.com> (raw)
In-Reply-To: 20011102092032.F26147@cpe-24-221-152-185.az.sprintbbd.net
Tom Rini wrote:
> Shouldn't board_setup_rtc_access() do all of the RTC stuff,
Please try to coordinate your RTC stuff with Armin. I don't have
enough knowledge of the details to discuss this, and it appears there
is a very standard way of working with the RTC, which is board
specific.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-11-05 17:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-02 15:49 [PATCH] Various patches against linuxppc_dev-2.4.14-pre7 David Müller (ELSOFT AG)
2001-11-02 16:20 ` Tom Rini
2001-11-03 8:19 ` David Müller (ELSOFT AG)
2001-11-05 17:05 ` Dan Malek [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=3BE6C6E5.7070505@mvista.com \
--to=dan@mvista.com \
--cc=d.mueller@elsoft.ch \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=trini@kernel.crashing.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).