All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Tony Luck <tony.luck@intel.com>,
	Fenghua Yu <fenghua.yu@intel.com>,
	linux-ia64@vger.kernel.org, linux-alpha@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] ia64: use asm-generic/io.h
Date: Fri, 27 Jul 2018 07:31:37 +0200	[thread overview]
Message-ID: <20180727073137.58668bf2@bbrezillon> (raw)
In-Reply-To: <20180711120824.3882108-1-arnd@arndb.de>

Hi Arnd,

On Wed, 11 Jul 2018 14:08:05 +0200
Arnd Bergmann <arnd@arndb.de> wrote:

> asm-generic/io.h provides a generic implementation of all I/O accessors,
> which the architectures can override.
> 
> Since ia64 does not provide readsl/writesl etc, any driver using those
> fails to build, and including asm-generic/io.h will provide the
> missing interfaces, as well as any other future interfaces that get
> added there. We need to #define a couple of symbols to themselves
> in the ia64 to ensure that we use the ia64 specific version of those
> rather than the generic one.
> 
> There should be no other effect than adding {read,write}s{b,w,l}()
> as well as {in,out}s{b,w,l}_p(), which were also not provided
> by ia64 but are provided by the generic header for historic reasons.
> 

Kbuild robots reported the same problem on parisc an alpha :-/.

Regards,

Boris

WARNING: multiple messages have this Message-ID (diff)
From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Tony Luck <tony.luck@intel.com>,
	Fenghua Yu <fenghua.yu@intel.com>,
	linux-ia64@vger.kernel.org, linux-alpha@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] ia64: use asm-generic/io.h
Date: Fri, 27 Jul 2018 05:31:37 +0000	[thread overview]
Message-ID: <20180727073137.58668bf2@bbrezillon> (raw)
In-Reply-To: <20180711120824.3882108-1-arnd@arndb.de>

Hi Arnd,

On Wed, 11 Jul 2018 14:08:05 +0200
Arnd Bergmann <arnd@arndb.de> wrote:

> asm-generic/io.h provides a generic implementation of all I/O accessors,
> which the architectures can override.
> 
> Since ia64 does not provide readsl/writesl etc, any driver using those
> fails to build, and including asm-generic/io.h will provide the
> missing interfaces, as well as any other future interfaces that get
> added there. We need to #define a couple of symbols to themselves
> in the ia64 to ensure that we use the ia64 specific version of those
> rather than the generic one.
> 
> There should be no other effect than adding {read,write}s{b,w,l}()
> as well as {in,out}s{b,w,l}_p(), which were also not provided
> by ia64 but are provided by the generic header for historic reasons.
> 

Kbuild robots reported the same problem on parisc an alpha :-/.

Regards,

Boris

  parent reply	other threads:[~2018-07-27  5:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-11 12:08 [PATCH 1/2] ia64: use asm-generic/io.h Arnd Bergmann
2018-07-11 12:08 ` Arnd Bergmann
2018-07-11 12:08 ` [PATCH 2/2] sparc64: add reads{b,w,l}/writes{b,w,l} Arnd Bergmann
2018-07-11 12:08   ` Arnd Bergmann
2018-07-12  2:52   ` David Miller
2018-07-12  2:52     ` David Miller
2018-07-20  8:23   ` Boris Brezillon
2018-07-20  8:23     ` Boris Brezillon
2018-07-26 23:27     ` Miquel Raynal
2018-07-26 23:27       ` Miquel Raynal
2018-07-26 23:27       ` Miquel Raynal
2018-07-26 23:27       ` Miquel Raynal
2018-07-20  9:10 ` [PATCH 1/2] ia64: use asm-generic/io.h Boris Brezillon
2018-07-20  9:10   ` Boris Brezillon
2018-07-26 23:28   ` Miquel Raynal
2018-07-26 23:28     ` Miquel Raynal
2018-07-26 23:28     ` Miquel Raynal
2018-07-27  5:31 ` Boris Brezillon [this message]
2018-07-27  5:31   ` Boris Brezillon
2018-08-15 23:34 ` Luck, Tony
2018-08-15 23:34   ` Luck, Tony

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=20180727073137.58668bf2@bbrezillon \
    --to=boris.brezillon@bootlin.com \
    --cc=arnd@arndb.de \
    --cc=fenghua.yu@intel.com \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.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.