From: kernel test robot <lkp@intel.com>
To: "Svyatoslav Ryhel" <clamor95@gmail.com>,
"Lee Jones" <lee@kernel.org>, "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Pavel Machek" <pavel@kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Sebastian Reichel" <sre@kernel.org>,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
"Ion Agorria" <ion@agorria.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org, linux-leds@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v1 4/9] mfd: Add driver for Asus Transformer embedded controller
Date: Mon, 2 Feb 2026 01:51:13 +0800 [thread overview]
Message-ID: <202602020110.y4aJbWNb-lkp@intel.com> (raw)
In-Reply-To: <20260201104343.79231-5-clamor95@gmail.com>
Hi Svyatoslav,
kernel test robot noticed the following build warnings:
[auto build test WARNING on next-20260130]
[also build test WARNING on linus/master v6.19-rc7]
[cannot apply to lee-mfd/for-mfd-next lee-mfd/for-mfd-fixes dtor-input/next dtor-input/for-linus sre-power-supply/for-next v6.19-rc7 v6.19-rc6 v6.19-rc5]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Svyatoslav-Ryhel/dt-bindings-misc-document-ASUS-Transformers-EC-Dockram/20260201-184740
base: next-20260130
patch link: https://lore.kernel.org/r/20260201104343.79231-5-clamor95%40gmail.com
patch subject: [PATCH v1 4/9] mfd: Add driver for Asus Transformer embedded controller
config: s390-allmodconfig (https://download.01.org/0day-ci/archive/20260202/202602020110.y4aJbWNb-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260202/202602020110.y4aJbWNb-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/202602020110.y4aJbWNb-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/mfd/asus-ec.c:107:40: warning: field width should have type 'int', but argument has type 'unsigned long' [-Wformat]
107 | dev_dbg(&priv->self->dev, "EC read: %*ph, ret = %d%s\n",
| ~~^
108 | sizeof(priv->ec_data), priv->ec_data,
| ~~~~~~~~~~~~~~~~~~~~~
include/linux/dev_printk.h:165:31: note: expanded from macro 'dev_dbg'
165 | dynamic_dev_dbg(dev, dev_fmt(fmt), ##__VA_ARGS__)
| ^~~ ~~~~~~~~~~~
include/linux/dev_printk.h:19:22: note: expanded from macro 'dev_fmt'
19 | #define dev_fmt(fmt) fmt
| ^~~
include/linux/dynamic_debug.h:285:12: note: expanded from macro 'dynamic_dev_dbg'
285 | dev, fmt, ##__VA_ARGS__)
| ^~~ ~~~~~~~~~~~
include/linux/dynamic_debug.h:261:59: note: expanded from macro '_dynamic_func_call'
261 | _dynamic_func_call_cls(_DPRINTK_CLASS_DFLT, fmt, func, ##__VA_ARGS__)
| ^~~~~~~~~~~
include/linux/dynamic_debug.h:259:65: note: expanded from macro '_dynamic_func_call_cls'
259 | __dynamic_func_call_cls(__UNIQUE_ID(ddebug), cls, fmt, func, ##__VA_ARGS__)
| ^~~~~~~~~~~
include/linux/dynamic_debug.h:231:15: note: expanded from macro '__dynamic_func_call_cls'
231 | func(&id, ##__VA_ARGS__); \
| ^~~~~~~~~~~
1 warning generated.
vim +107 drivers/mfd/asus-ec.c
100
101 static int asus_ec_read(struct asus_ec_data *priv, bool in_irq)
102 {
103 int ret = i2c_smbus_read_i2c_block_data(priv->self, 0x6A,
104 sizeof(priv->ec_data),
105 priv->ec_data);
106
> 107 dev_dbg(&priv->self->dev, "EC read: %*ph, ret = %d%s\n",
108 sizeof(priv->ec_data), priv->ec_data,
109 ret, in_irq ? "; in irq" : "");
110
111 return ret;
112 }
113
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-02-01 17:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-01 10:43 [PATCH v1 0/9] mfd: Add support for Asus Transformer embedded controller Svyatoslav Ryhel
2026-02-01 10:43 ` [PATCH v1 1/9] dt-bindings: misc: document ASUS Transformers EC Dockram Svyatoslav Ryhel
2026-02-01 10:43 ` [PATCH v1 2/9] misc: Support Asus Transformer's EC access device Svyatoslav Ryhel
2026-02-03 11:41 ` Greg Kroah-Hartman
2026-02-03 11:54 ` Svyatoslav Ryhel
2026-02-03 12:00 ` Greg Kroah-Hartman
2026-02-03 12:01 ` Svyatoslav Ryhel
2026-02-03 16:28 ` Svyatoslav Ryhel
2026-02-03 16:45 ` Greg Kroah-Hartman
2026-02-03 16:50 ` Svyatoslav Ryhel
2026-02-03 16:58 ` Greg Kroah-Hartman
2026-02-04 12:40 ` Svyatoslav Ryhel
2026-02-01 10:43 ` [PATCH v1 3/9] dt-bindings: mfd: document ASUS Transformer EC Svyatoslav Ryhel
2026-02-01 10:43 ` [PATCH v1 4/9] mfd: Add driver for Asus Transformer embedded controller Svyatoslav Ryhel
2026-02-01 17:51 ` kernel test robot [this message]
2026-02-01 19:06 ` kernel test robot
2026-02-01 10:43 ` [PATCH v1 5/9] input: serio: Add driver for Asus Transformer dock keyboard and touchpad Svyatoslav Ryhel
2026-02-01 10:43 ` [PATCH v1 6/9] input: keyboard: Add driver for Asus Transformer dock multimedia keys Svyatoslav Ryhel
2026-02-03 11:00 ` Dmitry Torokhov
2026-02-03 11:18 ` Svyatoslav Ryhel
2026-02-01 10:43 ` [PATCH v1 7/9] leds: Add driver for Asus Transformer LEDs Svyatoslav Ryhel
2026-02-01 10:43 ` [PATCH v1 8/9] power: supply: Add driver for Asus Transformer battery Svyatoslav Ryhel
2026-02-01 10:43 ` [PATCH v1 9/9] power: supply: Add charger driver for Asus Transformers Svyatoslav Ryhel
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=202602020110.y4aJbWNb-lkp@intel.com \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--cc=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=ion@agorria.com \
--cc=krzk@kernel.org \
--cc=lee@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mirq-linux@rere.qmqm.pl \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pavel@kernel.org \
--cc=robh@kernel.org \
--cc=sre@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.