public inbox for rust-for-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Zijing Zhang <zijing.zhang@ry.rs>,
	dakr@kernel.org, linux-pci@vger.kernel.org,
	rust-for-linux@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, bhelgaas@google.com,
	kwilczynski@kernel.org, ojeda@kernel.org, gary@garyguo.net,
	Zijing Zhang <zijing.zhang@ry.rs>
Subject: Re: [PATCH 2/2] samples: rust: pci: exercise capability lookup
Date: Sat, 31 Jan 2026 10:17:30 +0100	[thread overview]
Message-ID: <202601311056.PVHRBER5-lkp@intel.com> (raw)
In-Reply-To: <20260131040200.1242566-3-zijing.zhang@ry.rs>

Hi Zijing,

kernel test robot noticed the following build errors:

[auto build test ERROR on next-20260130]
[cannot apply to pci/next pci/for-linus v6.19-rc7 v6.19-rc6 v6.19-rc5 linus/master v6.16-rc1]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Zijing-Zhang/rust-pci-add-capability-lookup-helpers/20260131-120935
base:   next-20260130
patch link:    https://lore.kernel.org/r/20260131040200.1242566-3-zijing.zhang%40ry.rs
patch subject: [PATCH 2/2] samples: rust: pci: exercise capability lookup
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20260131/202601311056.PVHRBER5-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260131/202601311056.PVHRBER5-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202601311056.PVHRBER5-lkp@intel.com/

All errors (new ones prefixed by >>):

   PATH=/opt/cross/clang-20/bin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
   INFO PATH=/opt/cross/rustc-1.88.0-bindgen-0.72.1/cargo/bin:/opt/cross/clang-20/bin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
   /usr/bin/timeout -k 100 12h /usr/bin/make KCFLAGS= -fno-crash-diagnostics -Wno-error=return-type -Wreturn-type -funsigned-char -Wundef -falign-functions=64 W=1 --keep-going LLVM=1 -j32 -C source O=/kbuild/obj/consumer/x86_64-rhel-9.4-rust ARCH=x86_64 SHELL=/bin/bash rustfmtcheck
   make: Entering directory '/kbuild/src/consumer'
   make[1]: Entering directory '/kbuild/obj/consumer/x86_64-rhel-9.4-rust'
>> Diff in samples/rust/rust_driver_pci.rs:138:
                ("SR-IOV", bindings::PCI_EXT_CAP_ID_SRIOV as u16),
            ] {
                if let Some(pos) = pdev.find_ext_capability(id) {
   -                dev_info!(pdev.as_ref(), "pci-testdev {name} ext cap @ 0x{:04x}\n", pos);
   +                dev_info!(
   +                    pdev.as_ref(),
   +                    "pci-testdev {name} ext cap @ 0x{:04x}\n",
   +                    pos
   +                );
                } else {
                    dev_info!(pdev.as_ref(), "pci-testdev has no {name} ext capability\n");
                }
   Diff in samples/rust/rust_driver_pci.rs:177:
                    );
                }
            } else {
   -            dev_info!(pdev.as_ref(), "pci-testdev selfcheck: no ext config space\n");
   +            dev_info!(
   +                pdev.as_ref(),
   +                "pci-testdev selfcheck: no ext config space\n"
   +            );
            }
        }
    }
   make[2]: *** [Makefile:1902: rustfmt] Error 123
   make[2]: Target 'rustfmtcheck' not remade because of errors.
   make[1]: Leaving directory '/kbuild/obj/consumer/x86_64-rhel-9.4-rust'
   make[1]: *** [Makefile:248: __sub-make] Error 2
   make[1]: Target 'rustfmtcheck' not remade because of errors.
   make: *** [Makefile:248: __sub-make] Error 2
   make: Target 'rustfmtcheck' not remade because of errors.
   make: Leaving directory '/kbuild/src/consumer'

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2026-01-31  9:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-31  4:01 [PATCH 0/2] rust: pci: add capability lookup helpers Zijing Zhang
2026-01-31  4:01 ` [PATCH 1/2] " Zijing Zhang
2026-01-31  4:02 ` [PATCH 2/2] samples: rust: pci: exercise capability lookup Zijing Zhang
2026-01-31  9:17   ` kernel test robot [this message]
2026-01-31 13:34   ` Dirk Behme
2026-01-31 14:22     ` Zijing Zhang
2026-01-31  9:51 ` [PATCH v2 0/2] rust: pci: add capability lookup helpers Zijing Zhang
2026-01-31  9:51   ` [PATCH v2 1/2] " Zijing Zhang
2026-01-31  9:51   ` [PATCH v2 2/2] samples: rust: pci: exercise capability lookup Zijing Zhang
2026-01-31 15:17 ` [PATCH v3 0/2] rust: pci: add capability lookup helpers Zijing Zhang
2026-01-31 15:17   ` [PATCH v3 1/2] " Zijing Zhang
2026-02-01  6:24     ` Dirk Behme
2026-01-31 15:17   ` [PATCH v3 2/2] samples: rust: pci: exercise capability lookup Zijing Zhang

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=202601311056.PVHRBER5-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bhelgaas@google.com \
    --cc=dakr@kernel.org \
    --cc=gary@garyguo.net \
    --cc=kwilczynski@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=zijing.zhang@ry.rs \
    /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