From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux-Arch <linux-arch@vger.kernel.org>
Subject: Re: [PATCH v3 01/15] h8300: Assembly headers.
Date: Tue, 17 Feb 2015 16:39:42 +0900 [thread overview]
Message-ID: <87sie5kmv5.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <CAMuHMdVyquFQJAiSqyP7iuP+7gxfNOgGv6OjT3b4B2d6TJfJPw@mail.gmail.com>
At Sun, 15 Feb 2015 10:11:58 +0100,
Geert Uytterhoeven wrote:
>
> Hi Sato-san,
>
> On Sun, Feb 15, 2015 at 8:49 AM, Yoshinori Sato
> <ysato@users.sourceforge.jp> wrote:
> > --- /dev/null
> > +++ b/arch/h8300/include/asm/io.h
> > @@ -0,0 +1,372 @@
> > +#ifndef _H8300_IO_H
> > +#define _H8300_IO_H
> > +
> > +#ifdef __KERNEL__
> > +
> > +#include <linux/types.h>
> > +
> > +/*
> > + * These are for ISA/PCI shared memory _only_ and should never be used
> > + * on any other type of memory, including Zorro memory. They are meant to
> > + * access the bus in the bus byte order which is little-endian!.
> > + *
> > + * readX/writeX() are used to access memory mapped devices. On some
> > + * architectures the memory mapped IO stuff needs to be accessed
> > + * differently. On the m68k architecture, we just read/write the
> > + * memory location directly.
> > + */
> > +/* ++roman: The assignments to temp. vars avoid that gcc sometimes generates
> > + * two accesses to memory, which may be undesirable for some devices.
> > + */
>
> While some of the above applies to h8300, I think you should remove
> the parts that don't apply.
It's necessary by several drivers, so it has been left.
An unnecessary part is also included, so I have to remove the part.
> 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
--
Yoshinori Sato
<ysato@users.sourceforge.jp>
next prev parent reply other threads:[~2015-02-17 7:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-15 7:49 [PATCH v3 00/15] Revert h8300 archtecture Yoshinori Sato
2015-02-15 7:49 ` [PATCH v3 01/15] h8300: Assembly headers Yoshinori Sato
2015-02-15 9:11 ` Geert Uytterhoeven
2015-02-17 7:39 ` Yoshinori Sato [this message]
2015-02-15 7:49 ` [PATCH v3 02/15] h8300: UAPI headers Yoshinori Sato
2015-02-15 7:49 ` [PATCH v3 03/15] h8300: Exception and Interrupt handling Yoshinori Sato
2015-02-15 7:49 ` [PATCH v3 04/15] h8300: kernel booting Yoshinori Sato
2015-02-15 7:49 ` [PATCH v3 05/15] h8300: Process and signal Yoshinori Sato
2015-02-15 8:11 ` Yoshinori Sato
2015-02-15 10:33 ` Paul Bolle
2015-02-17 7:07 ` Yoshinori Sato
2015-02-15 19:38 ` Richard Weinberger
2015-02-17 7:09 ` Yoshinori Sato
2015-02-15 7:49 ` [PATCH v3 06/15] h8300 CPU depend helpers Yoshinori Sato
2015-02-15 7:49 ` [PATCH v3 07/15] h8300: miscellaneous functions Yoshinori Sato
2015-02-15 7:49 ` [PATCH v3 08/15] h8300: Memory management Yoshinori Sato
2015-02-15 7:49 ` [PATCH v3 09/15] h8300: library functions Yoshinori Sato
2015-02-15 7:49 ` [PATCH v3 10/15] h8300: Build scripts Yoshinori Sato
2015-02-15 19:23 ` Paul Bolle
2015-02-17 7:39 ` Yoshinori Sato
2015-02-17 9:46 ` Paul Bolle
2015-02-18 8:08 ` Yoshinori Sato
2015-02-15 7:49 ` [PATCH v3 11/15] h8300: clock driver Yoshinori Sato
2015-02-15 7:49 ` [PATCH v3 12/15] h8300: clocksource Yoshinori Sato
2015-02-15 7:49 ` [PATCH v3 13/15] h8300: configs Yoshinori Sato
2015-02-15 7:49 ` [PATCH v3 14/15] serial: Add h8300 Yoshinori Sato
2015-02-15 7:49 ` [PATCH v3 15/15] Add ELF machine Yoshinori Sato
2015-02-15 10:59 ` [PATCH v3 00/15] Revert h8300 archtecture Paul Bolle
2015-02-17 7:39 ` Yoshinori Sato
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=87sie5kmv5.wl-ysato@users.sourceforge.jp \
--to=ysato@users.sourceforge.jp \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 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.