Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Alexandre Courbot <acourbot@nvidia.com>,
	kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [linux-next:master 13730/14185] warning: unused import: `Spec`
Date: Sat, 3 Oct 2026 17:13:59 +0200	[thread overview]
Message-ID: <220704b7-c361-43da-bb67-3c19bfedc82e@nvidia.com> (raw)
In-Reply-To: <DLVATA7ILWLB.27BB2BXCREDOT@nvidia.com>

On 10/3/26 5:12 PM, Alexandre Courbot wrote:
> On Sun Oct 4, 2026 at 12:09 AM JST, kernel test robot wrote:
>> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>> head:   f0406245cb9855e6318335a8a223551354291a46
>> commit: 9cb3f5d56e81fd97a82ef361b210bc2322daaaa7 [13730/14185] gpu: nova-core: add an interrupt delivery self-test
>> config: um-randconfig-2000-20261003 (https://download.01.org/0day-ci/archive/20261003/202610031630.JOlyp48X-lkp@intel.com/config)
>> compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project d7e4505dd447d115d85fdea45cd71030ac1d86ee)
>> rustc: rustc 1.96.0 (ac68faa20 2026-05-25)
>> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261003/202610031630.JOlyp48X-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/202610031630.JOlyp48X-lkp@intel.com/
>>
>> All warnings (new ones prefixed by >>):
>>
>>>> warning: unused import: `Spec`
>>    --> drivers/gpu/nova-core/driver.rs:29:9
>>    |
>>    29 |         Spec, //
>>    |         ^^^^
>>    |
>>    = note: `#[warn(unused_imports)]` (part of `#[warn(unused)]`) on by default
> 
> Mmm, this indeed can happen when `CONFIG_NOVA_CORE_SELFTESTS` is not
> set. We should not import the symbol and instead fully qualify it on its
> use site. I'll send a patch to fix this.


Oh thanks for jumping on this, I was just starting to work through
it when you answered it already. :)


thanks,
-- 
John Hubbard


      reply	other threads:[~2026-10-03 15:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-03 15:09 [linux-next:master 13730/14185] warning: unused import: `Spec` kernel test robot
2026-10-03 15:12 ` Alexandre Courbot
2026-10-03 15:13   ` John Hubbard [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=220704b7-c361-43da-bb67-3c19bfedc82e@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=acourbot@nvidia.com \
    --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