linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
To: Arnd Bergmann <arnd@arndb.de>, kernel test robot <lkp@intel.com>
Cc: "llvm@lists.linux.dev" <llvm@lists.linux.dev>,
	"oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: RE: [linux-next:master 4222/6614] rswitch.c:undefined reference to `ptp_clock_index'
Date: Thu, 10 Nov 2022 00:53:04 +0000	[thread overview]
Message-ID: <TYBPR01MB5341B9171A808C9C23EC63E7D8019@TYBPR01MB5341.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <aea446bf-0f06-4636-9ebc-acc2bdc0c30e@app.fastmail.com>

Hi Arnd,

> From: Arnd Bergmann, Sent: Thursday, November 10, 2022 1:34 AM
> 
> On Wed, Nov 9, 2022, at 15:21, kernel test robot wrote:
> > tree:
> >
> > master
> ):
> >
> >    s390x-linux-ld: DWARF error: could not find abbrev number 4453
> >    drivers/net/ethernet/renesas/rswitch.o: in function `rswitch_get_ts_info':
> >>> rswitch.c:(.text+0x2a28): undefined reference to `ptp_clock_index'
> >    s390x-linux-ld: DWARF error: could not find abbrev number 11
> >    drivers/net/ethernet/renesas/rcar_gen4_ptp.o: in function
> > `rcar_gen4_ptp_register':
> >>> rcar_gen4_ptp.c:(.text+0xd6): undefined reference to `ptp_clock_register'
> >    s390x-linux-ld: drivers/net/ethernet/renesas/rcar_gen4_ptp.o: in
> > function `rcar_gen4_ptp_unregister':
> >>> rcar_gen4_ptp.c:(.text+0x198): undefined reference to `ptp_clock_unregister'
> 
> This usually means the driver needs an extra Kconfig dependency:
> 
>        depends on PTP_1588_CLOCK_OPTIONAL

Thank you for your comment. I'll send a patch to fix the issue.

Best regards,
Yoshihiro Shimoda



      reply	other threads:[~2022-11-10  0:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09 14:21 kernel test robot
2022-11-09 16:33 ` Arnd Bergmann
2022-11-10  0:53   ` Yoshihiro Shimoda [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=TYBPR01MB5341B9171A808C9C23EC63E7D8019@TYBPR01MB5341.jpnprd01.prod.outlook.com \
    --to=yoshihiro.shimoda.uh@renesas.com \
    --cc=arnd@arndb.de \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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