From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: kernel test robot <lkp@intel.com>
Cc: Romain Gantois <romain.gantois@bootlin.com>,
Wolfram Sang <wsa-dev@sang-engineering.com>,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Andi Shyti <andi.shyti@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Derek Kiernan <derek.kiernan@amd.com>,
Dragan Cvetic <dragan.cvetic@amd.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
oe-kbuild-all@lists.linux.dev, linux-media@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Kory Maincent <kory.maincent@bootlin.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 9/9] misc: add FPC202 dual port controller driver
Date: Mon, 11 Nov 2024 09:56:55 +0100 [thread overview]
Message-ID: <20241111095655.2c77df7d@booty> (raw)
In-Reply-To: <202411100412.QeOt1w0W-lkp@intel.com>
On Sun, 10 Nov 2024 04:19:43 +0800
kernel test robot <lkp@intel.com> wrote:
> >> drivers/misc/ti_fpc202.c:270:20: sparse: sparse: symbol 'fpc202_atr_ops' was not declared. Should it be static?
And perhaps 'const' too.
> vim +/fpc202_atr_ops +270 drivers/misc/ti_fpc202.c
>
> 269
> > 270 struct i2c_atr_ops fpc202_atr_ops = {
> 271 .attach_addr = fpc202_attach_addr,
> 272 .detach_addr = fpc202_detach_addr,
> 273 };
> 274
>
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2024-11-11 8:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 15:36 [PATCH 0/9] misc: Support TI FPC202 dual-port controller Romain Gantois
2024-11-08 15:36 ` [PATCH 1/9] dt-bindings: misc: Describe TI FPC202 dual port controller Romain Gantois
2024-11-08 18:23 ` Conor Dooley
2024-11-13 9:46 ` Romain Gantois
2024-11-08 15:36 ` [PATCH 2/9] media: i2c: ds90ub960: Replace aliased clients list with bitmap Romain Gantois
2024-11-08 15:36 ` [PATCH 3/9] media: i2c: ds90ub960: Protect alias_use_mask with a mutex Romain Gantois
2024-11-08 15:36 ` [PATCH 4/9] i2c: use client addresses directly in ATR interface Romain Gantois
2024-11-08 15:36 ` [PATCH 5/9] i2c: move ATR alias pool to a separate struct Romain Gantois
2024-11-08 15:36 ` [PATCH 6/9] i2c: rename field 'alias_list' of struct i2c_atr_chan to 'alias_pairs' Romain Gantois
2024-11-08 15:36 ` [PATCH 7/9] i2c: support per-channel ATR alias pools Romain Gantois
2024-11-08 15:37 ` [PATCH 8/9] i2c: Support dynamic address translation Romain Gantois
2024-11-08 15:37 ` [PATCH 9/9] misc: add FPC202 dual port controller driver Romain Gantois
2024-11-09 20:19 ` kernel test robot
2024-11-11 8:56 ` Luca Ceresoli [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=20241111095655.2c77df7d@booty \
--to=luca.ceresoli@bootlin.com \
--cc=andi.shyti@kernel.org \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=derek.kiernan@amd.com \
--cc=devicetree@vger.kernel.org \
--cc=dragan.cvetic@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=kory.maincent@bootlin.com \
--cc=krzk@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mchehab@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.org \
--cc=romain.gantois@bootlin.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=wsa-dev@sang-engineering.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