From: Nathan Chancellor <nathan@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: masahiroy@kernel.org, llvm@lists.linux.dev,
oe-kbuild-all@lists.linux.dev, ndesaulniers@google.com,
keescook@chromium.org, samitolvanen@google.com,
nicolas@fjasle.eu, trix@redhat.com, linux-kbuild@vger.kernel.org,
patches@lists.linux.dev
Subject: Re: [PATCH] kbuild: Enable -Wincompatible-function-pointer-types-strict in W=1
Date: Tue, 3 Oct 2023 11:38:18 -0700 [thread overview]
Message-ID: <20231003183818.GA1211904@dev-arch.thelio-3990X> (raw)
In-Reply-To: <202310031340.v1vPh207-lkp@intel.com>
On Tue, Oct 03, 2023 at 01:53:34PM +0800, kernel test robot wrote:
> Hi Nathan,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on ce9ecca0238b140b88f43859b211c9fdfd8e5b70]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Nathan-Chancellor/kbuild-Enable-Wincompatible-function-pointer-types-strict-in-W-1/20231003-062107
> base: ce9ecca0238b140b88f43859b211c9fdfd8e5b70
> patch link: https://lore.kernel.org/r/20231002-enable-wincompatible-function-pointer-types-strict-w-1-v1-1-808ab955d42d%40kernel.org
> patch subject: [PATCH] kbuild: Enable -Wincompatible-function-pointer-types-strict in W=1
> config: um-allnoconfig (https://download.01.org/0day-ci/archive/20231003/202310031340.v1vPh207-lkp@intel.com/config)
> compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231003/202310031340.v1vPh207-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/202310031340.v1vPh207-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
...
> >> arch/um/drivers/net_kern.c:353:21: warning: incompatible function pointer types initializing 'netdev_tx_t (*)(struct sk_buff *, struct net_device *)' (aka 'enum netdev_tx (*)(struct sk_buff *, struct net_device *)') with an expression of type 'int (struct sk_buff *, struct net_device *)' [-Wincompatible-function-pointer-types-strict]
> 353 | .ndo_start_xmit = uml_net_start_xmit,
> | ^~~~~~~~~~~~~~~~~~
> 13 warnings generated.
I have sent a patch to resolve this, thanks for the report!
https://lore.kernel.org/20231003-um-net-wifpts-v1-1-02888c634ee7@kernel.org/
Cheers,
Nathan
next prev parent reply other threads:[~2023-10-03 18:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 22:19 [PATCH] kbuild: Enable -Wincompatible-function-pointer-types-strict in W=1 Nathan Chancellor
2023-10-03 5:53 ` kernel test robot
2023-10-03 18:38 ` Nathan Chancellor [this message]
2023-10-05 18:38 ` Nick Desaulniers
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=20231003183818.GA1211904@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=patches@lists.linux.dev \
--cc=samitolvanen@google.com \
--cc=trix@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).