archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <>
To: kernel test robot <>
Cc:, Vaibhav Gupta <>,,,,,
	"David S. Miller" <>
Subject: Re: [Linux-kernel-mentees] [PATCH v1 1/4] ide: use generic power management
Date: Fri, 26 Jun 2020 10:35:00 -0500	[thread overview]
Message-ID: <20200626153500.GA2895752@bjorn-Precision-5520> (raw)
In-Reply-To: <>

On Thu, Jun 25, 2020 at 06:14:09AM +0800, kernel test robot wrote:
> Hi Vaibhav,
> Thank you for the patch! Yet something to improve:
> [auto build test ERROR on ide/master]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use  as documented in
> url:
> base: master
> config: x86_64-randconfig-a004-20200624 (attached as .config)

This auto build testing is a great service, but is there any way to
tweak the info above to make it easier to reproduce the problem?

I tried to checkout the source that caused these errors, but failed.
This is probably because I'm not a git expert, but maybe others are in
the same boat.  For example, I tried:

  $ git remote add kbuild
  $ git fetch kbuild
  fatal: repository '' not found

I also visited the github URL in a browser, and I'm sure there must be
information there that would let me fetch the source, but I don't know
enough about github to find it.

The report doesn't include a SHA1, so even if I *did* manage to fetch
the sources, I wouldn't be able to validate they were the *correct*

> compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
> reproduce (this is a W=1 build):
>         # save the attached .config to linux build tree
>         make W=1 ARCH=x86_64 
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <>
> All errors (new ones prefixed by >>, old ones prefixed by <<):
> >> ERROR: modpost: "ide_pci_pm_ops" [drivers/ide/ide-pci-generic.ko] undefined!
> >> ERROR: modpost: "ide_pci_pm_ops" [drivers/ide/serverworks.ko] undefined!
> >> ERROR: modpost: "ide_pci_pm_ops" [drivers/ide/piix.ko] undefined!
> >> ERROR: modpost: "ide_pci_pm_ops" [drivers/ide/pdc202xx_old.ko] undefined!
> >> ERROR: modpost: "ide_pci_pm_ops" [drivers/ide/ns87415.ko] undefined!
> >> ERROR: modpost: "ide_pci_pm_ops" [drivers/ide/hpt366.ko] undefined!
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation

Linux-kernel-mentees mailing list

  reply	other threads:[~2020-06-26 15:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-24 17:28 [Linux-kernel-mentees] [PATCH v1 0/4] drivers: ide: use generic power management Vaibhav Gupta
2020-06-24 17:28 ` [Linux-kernel-mentees] [PATCH v1 1/4] " Vaibhav Gupta
2020-06-24 22:14   ` kernel test robot
2020-06-26 15:35     ` Bjorn Helgaas [this message]
2020-06-29 13:53       ` [Linux-kernel-mentees] [kbuild-all] " Xia, Hui
2020-06-24 17:28 ` [Linux-kernel-mentees] [PATCH v1 2/4] ide: triflex: " Vaibhav Gupta
2020-06-24 17:28 ` [Linux-kernel-mentees] [PATCH v1 3/4] ide: sc1200: " Vaibhav Gupta
2020-06-24 17:28 ` [Linux-kernel-mentees] [PATCH v1 4/4] ide: delkin_cb: " Vaibhav Gupta

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200626153500.GA2895752@bjorn-Precision-5520 \ \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).