From: Ivan Vecera <ivecera@redhat.com>
To: kernel test robot <lkp@intel.com>, netdev@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Eric Dumazet <edumazet@google.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Leon Romanovsky <leon@kernel.org>,
Alexander Lobakin <aleksander.lobakin@intel.com>,
linux-rdma@vger.kernel.org,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
Aleksandr Loktionov <aleksandr.loktionov@intel.com>,
intel-wired-lan@lists.osuosl.org,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Jiri Pirko <jiri@resnulli.us>,
Richard Cochran <richardcochran@gmail.com>,
Prathosh Satish <Prathosh.Satish@microchip.com>,
Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Mark Bloch <mbloch@nvidia.com>,
linux-kernel@vger.kernel.org, Tariq Toukan <tariqt@nvidia.com>,
Jonathan Lemon <jonathan.lemon@gmail.com>,
Saeed Mahameed <saeedm@nvidia.com>
Subject: Re: [Intel-wired-lan] [PATCH net-next v4 7/9] dpll: Add reference count tracking support
Date: Tue, 3 Feb 2026 11:21:16 +0100 [thread overview]
Message-ID: <67478aa2-54f5-4a3f-8063-ab6e877693e4@redhat.com> (raw)
In-Reply-To: <202602030538.6ok1xugA-lkp@intel.com>
On 2/2/26 10:48 PM, kernel test robot wrote:
> Hi Ivan,
>
> kernel test robot noticed the following build errors:
>
> [auto build test ERROR on net-next/main]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Ivan-Vecera/dpll-Allow-associating-dpll-pin-with-a-firmware-node/20260203-012705
> base: net-next/main
> patch link: https://lore.kernel.org/r/20260202171638.17427-8-ivecera%40redhat.com
> patch subject: [Intel-wired-lan] [PATCH net-next v4 7/9] dpll: Add reference count tracking support
> config: i386-randconfig-141-20260203 (https://download.01.org/0day-ci/archive/20260203/202602030538.6ok1xugA-lkp@intel.com/config)
> compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
> smatch version: v0.5.0-8994-gd50c5a4c
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260203/202602030538.6ok1xugA-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/202602030538.6ok1xugA-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> In file included from net/core/rtnetlink.c:61:
>>> include/linux/dpll.h:235:1: error: expected identifier or '('
> 235 | {
> | ^
> 1 error generated.
>
>
> vim +235 include/linux/dpll.h
>
> 877c40367bc8a7 Ivan Vecera 2026-02-02 232
> 877c40367bc8a7 Ivan Vecera 2026-02-02 233 static inline struct dpll_pin *
> bed78c2008cb37 Ivan Vecera 2026-02-02 234 fwnode_dpll_pin_find(struct fwnode_handle *fwnode, dpll_tracker *tracker);
Oh god, extra semicolon in this stub :-(
Will submit the fix after 24h grace period.
I.
> 877c40367bc8a7 Ivan Vecera 2026-02-02 @235 {
> 877c40367bc8a7 Ivan Vecera 2026-02-02 236 return NULL;
> 877c40367bc8a7 Ivan Vecera 2026-02-02 237 }
> 5f18426928800c Jiri Pirko 2023-09-13 238 #endif
> 5f18426928800c Jiri Pirko 2023-09-13 239
next prev parent reply other threads:[~2026-02-03 10:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 17:16 [PATCH net-next v4 0/9] dpll: Core improvements and ice E825-C SyncE support Ivan Vecera
2026-02-02 17:16 ` [PATCH net-next v4 1/9] dpll: Allow associating dpll pin with a firmware node Ivan Vecera
2026-02-02 17:16 ` [PATCH net-next v4 2/9] dpll: zl3073x: Associate pin with fwnode handle Ivan Vecera
2026-02-02 17:16 ` [PATCH net-next v4 3/9] dpll: Add notifier chain for dpll events Ivan Vecera
2026-02-02 17:16 ` [PATCH net-next v4 4/9] dpll: Support dynamic pin index allocation Ivan Vecera
2026-02-02 17:16 ` [PATCH net-next v4 5/9] dpll: zl3073x: Add support for mux pin type Ivan Vecera
2026-02-02 17:16 ` [PATCH net-next v4 6/9] dpll: Enhance and consolidate reference counting logic Ivan Vecera
2026-02-02 17:16 ` [PATCH net-next v4 7/9] dpll: Add reference count tracking support Ivan Vecera
2026-02-02 21:48 ` [Intel-wired-lan] " kernel test robot
2026-02-03 10:21 ` Ivan Vecera [this message]
2026-02-02 23:55 ` kernel test robot
2026-02-03 16:11 ` [net-next,v4,7/9] " Simon Horman
2026-02-03 17:08 ` Ivan Vecera
2026-02-02 17:16 ` [PATCH net-next v4 8/9] drivers: Add support for DPLL reference count tracking Ivan Vecera
2026-02-02 17:16 ` [PATCH net-next v4 9/9] ice: dpll: Support E825-C SyncE and dynamic pin discovery Ivan Vecera
2026-02-03 16:11 ` [net-next,v4,9/9] " Simon Horman
2026-02-03 17:16 ` Ivan Vecera
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=67478aa2-54f5-4a3f-8063-ab6e877693e4@redhat.com \
--to=ivecera@redhat.com \
--cc=Prathosh.Satish@microchip.com \
--cc=aleksander.lobakin@intel.com \
--cc=aleksandr.loktionov@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jiri@resnulli.us \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=richardcochran@gmail.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=vadim.fedorenko@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