From: Shay Drory <shayd@nvidia.com>
To: kernel test robot <lkp@intel.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
<kunit-dev@googlegroups.com>, <kvmarm@lists.linux.dev>,
<linux-arm-kernel@lists.infradead.org>,
<linux-arm-msm@vger.kernel.org>,
<linux-bluetooth@vger.kernel.org>,
<linux-kselftest@vger.kernel.org>, <linux-parisc@vger.kernel.org>,
<linux-rdma@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
<linux-usb@vger.kernel.org>, <netdev@vger.kernel.org>
Subject: Re: [linux-next:master] BUILD REGRESSION 296d53d8f84ce50ffaee7d575487058c8d437335
Date: Tue, 4 Jul 2023 13:30:43 +0300 [thread overview]
Message-ID: <5621fe4a-5c21-b407-91a1-4cc299f5abb0@nvidia.com> (raw)
In-Reply-To: <202307032309.v4K1IBoR-lkp@intel.com>
On 03/07/2023 18:11, kernel test robot wrote:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> branch HEAD: 296d53d8f84ce50ffaee7d575487058c8d437335 Add linux-next specific files for 20230703
[...]
> Unverified Error/Warning (likely false positive, please contact us if interested):
>
> drivers/net/ethernet/mellanox/mlx5/core/lib/devcom.c:98 mlx5_devcom_register_device() error: uninitialized symbol 'tmp_dev'.
This *is* a false positive. there is a comment explaining it.
prev parent reply other threads:[~2023-07-04 10:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 15:11 kernel test robot
2023-07-04 7:15 ` Marc Zyngier
2023-07-04 14:11 ` Bart Van Assche
2023-07-10 5:51 ` Yujie Liu
2023-07-04 10:30 ` Shay Drory [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=5621fe4a-5c21-b407-91a1-4cc299f5abb0@nvidia.com \
--to=shayd@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=kunit-dev@googlegroups.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.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