From: Greg KH <gregkh@linuxfoundation.org>
To: Frank Li <Frank.Li@nxp.com>
Cc: vkoul@kernel.org, bhe@redhat.com, dmaengine@vger.kernel.org,
imx@lists.linux.dev, linux-kernel@vger.kernel.org, lkp@intel.com,
oe-kbuild-all@lists.linux.dev, rafael@kernel.org
Subject: Re: [PATCH 1/1] fs: debugfs: fix build error at powerpc platform
Date: Sat, 30 Sep 2023 09:11:04 +0200 [thread overview]
Message-ID: <2023093029-chalice-violation-c349@gregkh> (raw)
In-Reply-To: <20230929164920.314849-1-Frank.Li@nxp.com>
On Fri, Sep 29, 2023 at 12:49:20PM -0400, 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'
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202309291322.3pZiyosI-lkp@intel.com/
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
What commit id does this fix?
> ---
> fs/debugfs/file.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/debugfs/file.c b/fs/debugfs/file.c
> index 5b8d4fd7c747..b406283806d9 100644
> --- a/fs/debugfs/file.c
> +++ b/fs/debugfs/file.c
> @@ -1179,7 +1179,7 @@ void debugfs_print_regs(struct seq_file *s, const struct debugfs_reg *regs,
> seq_printf(s, "%s = 0x%04x\n", regs->name,
> b ? ioread16be(reg) : ioread16(reg));
> break;
> -#ifdef CONFIG_64BIT
> +#if defined(ioread64) && defined (ioread64be)
Are you sure this is equivalent? What if these are functions?
thanks,
greg k-h
next prev parent reply other threads:[~2023-09-30 7:11 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 [this message]
2023-09-30 21:04 ` Frank Li
2023-10-01 11:22 ` Baoquan He
2023-10-01 15:42 ` Arnd Bergmann
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=2023093029-chalice-violation-c349@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Frank.Li@nxp.com \
--cc=bhe@redhat.com \
--cc=dmaengine@vger.kernel.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 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.