From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg Ungerer <gerg@linux-m68k.org>,
Sasha Levin <sashal@kernel.org>, stable <stable@vger.kernel.org>
Subject: Re: [linux-stable-rc:linux-5.10.y 644/7104] synclink.c:undefined reference to `free_dma'
Date: Sat, 23 Jul 2022 17:08:27 +0200 [thread overview]
Message-ID: <YtwO6yaYaf5Eu1Md@kroah.com> (raw)
In-Reply-To: <CAK8P3a0vZrXxNp3YhrxFjFunHgxSZBKD9Y4darSODgeFAukCeQ@mail.gmail.com>
On Fri, Jul 22, 2022 at 02:58:32PM +0200, Arnd Bergmann wrote:
> Hi Greg,
>
> I looked at this report for 5.10.y:
>
> On Fri, Jul 22, 2022 at 12:20 AM kernel test robot <lkp@intel.com> wrote:
> >
> > Hi Arnd,
> >
> > FYI, the error/warning still remains.
> >
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
> > head: 7748091a31277b35d55bffa6fecda439d8526366
> > commit: 87ae522e467e17a13b796e2cb595f9c3943e4d5e [644/7104] m68knommu: only set CONFIG_ISA_DMA_API for ColdFire sub-arch
> > config: m68k-randconfig-r011-20220721 (https://download.01.org/0day-ci/archive/20220722/202207220652.CGm6UUjK-lkp@intel.com/config)
> > compiler: m68k-linux-gcc (GCC) 12.1.0
> > reproduce (this is a W=1 build):
> > wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> > chmod +x ~/bin/make.cross
> > # https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?id=87ae522e467e17a13b796e2cb595f9c3943e4d5e
> > git remote add linux-stable-rc https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> > git fetch --no-tags linux-stable-rc linux-5.10.y
> > git checkout 87ae522e467e17a13b796e2cb595f9c3943e4d5e
> > # save the config file
> > mkdir build_dir && cp config build_dir/.config
> > COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=m68k SHELL=/bin/bash
> >
> > If you fix the issue, kindly add following tag where applicable
> > Reported-by: kernel test robot <lkp@intel.com>
> >
> > All errors (new ones prefixed by >>):
> >
> > m68k-linux-ld: section .rodata VMA [0000000000002000,00000000005fa837] overlaps section .text VMA [0000000000000400,0000000000ffa6bf]
> > m68k-linux-ld: drivers/tty/synclink.o: in function `mgsl_release_resources':
> > >> synclink.c:(.text+0xd1a): undefined reference to `free_dma'
>
> This can be addressed by either backporting f95a387cdeb3 ("m68k: coldfire: drop
> ISA_DMA_API support") or by reverting the 87ae522e467e ("m68knommu: only
> set CONFIG_ISA_DMA_API for ColdFire sub-arch"), which is not actually needed
> on 5.10.
I've now reverted it, thanks.
greg k-h
prev parent reply other threads:[~2022-07-23 15:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 22:20 [linux-stable-rc:linux-5.10.y 644/7104] synclink.c:undefined reference to `free_dma' kernel test robot
2022-07-22 12:58 ` Arnd Bergmann
2022-07-23 15:08 ` Greg Kroah-Hartman [this message]
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=YtwO6yaYaf5Eu1Md@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=gerg@linux-m68k.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=sashal@kernel.org \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox