The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: "open list:KERNEL SELFTEST FRAMEWORK"
	<linux-kselftest@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	lkft-triage@lists.linaro.org,
	Linux Regressions <regressions@lists.linux.dev>,
	Shuah Khan <shuah@kernel.org>, Jens Axboe <axboe@kernel.dk>,
	kbusch@kernel.org, Anders Roxell <anders.roxell@linaro.org>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: selftests ublk UBLK_IO_F_NEED_REG_BUF undeclared
Date: Tue, 17 Jun 2025 19:05:20 +0800	[thread overview]
Message-ID: <aFFL8DQufPXnerlm@fedora> (raw)
In-Reply-To: <CA+G9fYsiWN1gWhHBk9uruDBzVHvLYCTL-VcxU2iiPMcS1EXyBg@mail.gmail.com>

On Tue, Jun 17, 2025 at 04:27:31PM +0530, Naresh Kamboju wrote:
> The following build warnings / errors noticed while building the selftest/ublk
> with gcc-13 and clang-nightly toolchains on Linux next tree.
> 
> Please suggest if I am missing something in my build setup.
> 
> Regressions found on arm arm64 x86_64
>   -  selftests ublk
> 
> Regression Analysis:
>  - New regression? Yes
>  - Reproducibility? Yes
> 
> Build regression: selftests ublk UBLK_IO_F_NEED_REG_BUF undeclared
> 
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> 
> ## Build log
> 
>  CC       kublk

Please run 'make headers_install' before running the test.


Thanks,
Ming


      reply	other threads:[~2025-06-17 11:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-17 10:57 selftests ublk UBLK_IO_F_NEED_REG_BUF undeclared Naresh Kamboju
2025-06-17 11:05 ` Ming Lei [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=aFFL8DQufPXnerlm@fedora \
    --to=ming.lei@redhat.com \
    --cc=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=axboe@kernel.dk \
    --cc=dan.carpenter@linaro.org \
    --cc=kbusch@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=regressions@lists.linux.dev \
    --cc=shuah@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