From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Roel Kluin <roel.kluin@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"Peter 'p2' De Schrijver" <p2@debian.org>,
"Linux/m68k" <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH] m68k,m68knommu: missing asterisk?
Date: Tue, 23 Feb 2010 07:13:33 +0100 [thread overview]
Message-ID: <10f740e81002222213n3ef9608frd81422cd9a74c04@mail.gmail.com> (raw)
In-Reply-To: <4B7F2EC7.6000305@gmail.com>
On Sat, Feb 20, 2010 at 01:37, Roel Kluin <roel.kluin@gmail.com> wrote:
> An asterisk was missing.
>
> Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
> ---
> Correct?
No, see arch/m68k/apollo/config.c:dn_dummy_hwclk().
Andrew: please dequeue.
> arch/m68k/include/asm/apollohw.h | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/m68k/include/asm/apollohw.h b/arch/m68k/include/asm/apollohw.h
> index a1373b9..87e0cc4 100644
> --- a/arch/m68k/include/asm/apollohw.h
> +++ b/arch/m68k/include/asm/apollohw.h
> @@ -94,7 +94,7 @@ extern u_long timer_physaddr;
>
> #define sio01 ((*(volatile struct SCN2681 *)(IO_BASE + sio01_physaddr)))
> #define sio23 ((*(volatile struct SCN2681 *)(IO_BASE + sio23_physaddr)))
> -#define rtc (((volatile struct mc146818 *)(IO_BASE + rtc_physaddr)))
> +#define rtc ((*(volatile struct mc146818 *)(IO_BASE + rtc_physaddr)))
> #define cpuctrl (*(volatile unsigned int *)(IO_BASE + cpuctrl_physaddr))
> #define pica (IO_BASE + pica_physaddr)
> #define picb (IO_BASE + picb_physaddr)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2010-02-23 6:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-20 0:37 Roel Kluin
2010-02-23 6:13 ` Geert Uytterhoeven [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=10f740e81002222213n3ef9608frd81422cd9a74c04@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=p2@debian.org \
--cc=roel.kluin@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®