From: "Arnd Bergmann" <arnd@arndb.de>
To: "Baoquan He" <bhe@redhat.com>, "Frank Li" <Frank.Li@nxp.com>
Cc: "Vinod Koul" <vkoul@kernel.org>,
dmaengine@vger.kernel.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
imx@lists.linux.dev, linux-kernel@vger.kernel.org,
"kernel test robot" <lkp@intel.com>,
oe-kbuild-all@lists.linux.dev,
"Rafael J . Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH 1/1] fs: debugfs: fix build error at powerpc platform
Date: Sun, 01 Oct 2023 11:42:04 -0400 [thread overview]
Message-ID: <b795ed61-0174-487f-a263-8431e7c76af5@app.fastmail.com> (raw)
In-Reply-To: <ZRlWeeq/AOjyTtnV@MiWiFi-R3L-srv>
On Sun, Oct 1, 2023, at 07:22, Baoquan He wrote:
> On 09/29/23 at 12:49pm, Frank Li wrote:
>> ld: fs/debugfs/file.o: in function `debugfs_print_regs':
>> file.c:(.text+0x95a): undefined reference to `ioread64be'
>> >> ld: file.c:(.text+0x9dd): undefined reference to `ioread64'
>
> From your reproducer, on x86_64, GENERIC_IOMAP is selected. So the
> default version of ioread64 and ioread64be in asm-generic/io.h are
> bypassed. Except of those arch where ioread64 and ioread64be are
> implemented specifically like alpha, arm64, parisc, power, we may need
> include include/linux/io-64-nonatomic-hi-lo.h or
> include/linux/io-64-nonatomic-lo-hi.h to fix above linking issue?
>
> From my side, below change can fix the issue. However, I am not quite
> sure which one is chosen between io-64-nonatomic-hi-lo.h and
> io-64-nonatomic-hi-lo.h.
It looks like the latest version of the patch only calls
it for 64-bit targets, so this question should not come up.
On 32-bit targets, it is driver specific which one you need,
so having it generic code would require passing a flag from
a driver, but I think that adds more complexity than it help.
Arnd
next prev parent reply other threads:[~2023-10-01 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 16:49 [PATCH 1/1] fs: debugfs: fix build error at powerpc platform Frank Li
2023-09-30 7:11 ` Greg KH
2023-09-30 21:04 ` Frank Li
2023-10-01 11:22 ` Baoquan He
2023-10-01 15:42 ` Arnd Bergmann [this message]
2023-10-02 14:54 ` Frank Li
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=b795ed61-0174-487f-a263-8431e7c76af5@app.fastmail.com \
--to=arnd@arndb.de \
--cc=Frank.Li@nxp.com \
--cc=bhe@redhat.com \
--cc=dmaengine@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rafael@kernel.org \
--cc=vkoul@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox