From: Guenter Roeck <linux@roeck-us.net>
To: Logan Gunthorpe <logang@deltatee.com>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
linux-ntb@googlegroups.com, linux-crypto@vger.kernel.org,
"Andrew Morton" <akpm@linux-foundation.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Horia Geantă" <horia.geanta@nxp.com>,
"Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
"Paul Mackerras" <paulus@samba.org>,
"Michael Ellerman" <mpe@ellerman.id.au>,
"Suresh Warrier" <warrier@linux.vnet.ibm.com>,
"Nicholas Piggin" <npiggin@gmail.com>
Subject: Re: [v18,3/7] iomap: introduce io{read|write}64_{lo_hi|hi_lo}
Date: Fri, 13 Jul 2018 18:12:43 -0700 [thread overview]
Message-ID: <cc6cfb2a-d1d4-3328-3f49-07f7cec09faf@roeck-us.net> (raw)
In-Reply-To: <0a32dbb8-a1fa-f691-1d4a-9851b1496b9a@deltatee.com>
On 07/13/2018 05:20 PM, Logan Gunthorpe wrote:
>
>
> On 13/07/18 05:38 PM, Guenter Roeck wrote:
>> This patch causes a build failure in -next when building
>> ppc:corenet64_smp_defconfig.
>
> Thanks for the report. This 64bit IO stuff is a bit of a mess. It looks
> like your corner case arch and config was never covered by the kbuild
> robot which has run extensively on this patchset.
>
> Anyway, I think the fix is to put back the ioread64/write64 prototypes
> (even though they are only used in this one corner).
>
> Can you try it with the following patch to ensure it fixes things for you?
>
It does.
Guenter
> Logan
>
> --
>
> diff --git a/include/asm-generic/iomap.h b/include/asm-generic/iomap.h
> index 5a4af0199b32..9f11a79e0d7a 100644
> --- a/include/asm-generic/iomap.h
> +++ b/include/asm-generic/iomap.h
> @@ -32,6 +32,11 @@ extern unsigned int ioread16be(void __iomem *);
> extern unsigned int ioread32(void __iomem *);
> extern unsigned int ioread32be(void __iomem *);
>
> +#ifdef CONFIG_64BIT
> +extern u64 ioread64(void __iomem *);
> +extern u64 ioread64be(void __iomem *);
> +#endif
> +
> #ifdef readq
> #define ioread64_lo_hi ioread64_lo_hi
> #define ioread64_hi_lo ioread64_hi_lo
> @@ -49,6 +54,11 @@ extern void iowrite16be(u16, void __iomem *);
> extern void iowrite32(u32, void __iomem *);
> extern void iowrite32be(u32, void __iomem *);
>
> +#ifdef CONFIG_64BIT
> +extern void iowrite64(u64, void __iomem *);
> +extern void iowrite64be(u64, void __iomem *);
> +#endif
> +
> #ifdef writeq
> #define iowrite64_lo_hi iowrite64_lo_hi
> #define iowrite64_hi_lo iowrite64_hi_lo
>
next prev parent reply other threads:[~2018-07-14 1:13 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 19:47 [PATCH v18 0/7] Add io{read|write}64 to io-64-atomic headers Logan Gunthorpe
2018-06-22 19:47 ` [PATCH v18 1/7] iomap: Use non-raw io functions for io{read|write}XXbe Logan Gunthorpe
2018-06-22 19:47 ` [PATCH v18 2/7] parisc: iomap: introduce io{read|write}64 Logan Gunthorpe
2018-06-22 19:47 ` [PATCH v18 3/7] iomap: introduce io{read|write}64_{lo_hi|hi_lo} Logan Gunthorpe
2018-07-13 23:38 ` [v18,3/7] " Guenter Roeck
2018-07-14 0:20 ` Logan Gunthorpe
2018-07-14 1:12 ` Guenter Roeck [this message]
2018-06-22 19:47 ` [PATCH v18 4/7] io-64-nonatomic: add io{read|write}64[be]{_lo_hi|_hi_lo} macros Logan Gunthorpe
2018-06-22 19:47 ` [PATCH v18 5/7] ntb: ntb_hw_intel: use io-64-nonatomic instead of in-driver hacks Logan Gunthorpe
2018-06-22 19:47 ` [PATCH v18 6/7] crypto: caam: cleanup CONFIG_64BIT ifdefs when using io{read|write}64 Logan Gunthorpe
2018-07-03 15:31 ` Fabio Estevam
2018-07-03 17:36 ` Andy Shevchenko
2018-07-03 17:44 ` Fabio Estevam
2018-07-03 18:01 ` Logan Gunthorpe
2018-07-03 18:06 ` Fabio Estevam
2018-07-03 18:09 ` Andy Shevchenko
2018-07-03 18:11 ` Fabio Estevam
2018-07-03 18:47 ` Logan Gunthorpe
2018-07-03 19:40 ` Fabio Estevam
2018-07-03 19:58 ` Andy Shevchenko
2018-07-03 20:10 ` Fabio Estevam
2018-07-03 20:40 ` Andy Shevchenko
2018-07-03 20:42 ` Andy Shevchenko
2018-07-03 23:55 ` Fabio Estevam
2018-07-03 21:16 ` Logan Gunthorpe
2018-07-03 23:56 ` Fabio Estevam
2018-07-03 21:20 ` Logan Gunthorpe
2018-07-03 22:21 ` Andy Shevchenko
2018-07-03 23:20 ` Logan Gunthorpe
2018-07-03 23:52 ` Fabio Estevam
2018-07-03 23:57 ` Logan Gunthorpe
2018-07-04 0:02 ` Logan Gunthorpe
2018-07-04 0:06 ` Fabio Estevam
2018-07-04 11:45 ` Horia Geanta
2018-07-04 15:06 ` Fabio Estevam
2018-07-04 15:59 ` Horia Geanta
2018-07-04 16:16 ` Fabio Estevam
2018-07-04 17:01 ` Logan Gunthorpe
2018-07-04 17:10 ` Andy Shevchenko
2018-07-04 17:13 ` Logan Gunthorpe
2018-07-04 17:16 ` Andy Shevchenko
2018-07-04 17:21 ` Logan Gunthorpe
2018-07-04 17:21 ` Andy Shevchenko
2018-07-04 17:23 ` Logan Gunthorpe
2018-07-04 17:25 ` Andy Shevchenko
2018-07-04 17:32 ` Andy Shevchenko
2018-07-04 17:36 ` Logan Gunthorpe
2018-07-03 18:06 ` Andy Shevchenko
2018-06-22 19:47 ` [PATCH v18 7/7] ntb: ntb_hw_switchtec: Cleanup 64bit IO defines to use the common header Logan Gunthorpe
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=cc6cfb2a-d1d4-3328-3f49-07f7cec09faf@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=gregkh@linuxfoundation.org \
--cc=horia.geanta@nxp.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntb@googlegroups.com \
--cc=logang@deltatee.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=paulus@samba.org \
--cc=warrier@linux.vnet.ibm.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®