From: kernel test robot <lkp@intel.com>
To: Cosmo Chou <chou.cosmo@gmail.com>,
jdelvare@suse.com, linux@roeck-us.net, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
corbet@lwn.net, heiko@sntech.de, jernej.skrabec@gmail.com,
macromorgan@hotmail.com, linus.walleij@linaro.org
Cc: oe-kbuild-all@lists.linux.dev, linux-hwmon@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, chou.cosmo@gmail.com,
cosmo.chou@quantatw.com
Subject: Re: [PATCH 3/3] hwmon: Add driver for Astera Labs PT516XX retimer
Date: Wed, 6 Dec 2023 07:24:26 +0800 [thread overview]
Message-ID: <202312060716.Zh0AHxKs-lkp@intel.com> (raw)
In-Reply-To: <20231205074723.3546295-4-chou.cosmo@gmail.com>
Hi Cosmo,
kernel test robot noticed the following build warnings:
[auto build test WARNING on groeck-staging/hwmon-next]
[also build test WARNING on robh/for-next linus/master v6.7-rc4 next-20231205]
[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/Cosmo-Chou/dt-bindings-vendor-prefixes-add-asteralabs/20231205-155020
base: https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-next
patch link: https://lore.kernel.org/r/20231205074723.3546295-4-chou.cosmo%40gmail.com
patch subject: [PATCH 3/3] hwmon: Add driver for Astera Labs PT516XX retimer
reproduce: (https://download.01.org/0day-ci/archive/20231206/202312060716.Zh0AHxKs-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/202312060716.Zh0AHxKs-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Documentation/hwmon/pt516xx.rst:4: WARNING: Title underline too short.
vim +4 Documentation/hwmon/pt516xx.rst
2
3 Kernel driver pt516xx
> 4 ====================
5
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-12-05 23:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 7:47 [PATCH 0/3] hwmon: Add driver for Astera Labs PT516XX retimer Cosmo Chou
2023-12-05 7:47 ` [PATCH 1/3] dt-bindings: vendor-prefixes: add asteralabs Cosmo Chou
2023-12-05 16:45 ` Conor Dooley
2023-12-05 7:47 ` [PATCH 2/3] dt-bindings: hwmon: pt516xx: add bindings Cosmo Chou
2023-12-05 16:46 ` Conor Dooley
2023-12-06 8:02 ` Cosmo Chou
2023-12-05 7:47 ` [PATCH 3/3] hwmon: Add driver for Astera Labs PT516XX retimer Cosmo Chou
2023-12-05 15:55 ` Guenter Roeck
2023-12-09 8:02 ` Cosmo Chou
2023-12-05 23:24 ` kernel test robot [this message]
2023-12-11 17:43 ` Rob Herring
2023-12-05 14:45 ` [PATCH 0/3] " Guenter Roeck
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=202312060716.Zh0AHxKs-lkp@intel.com \
--to=lkp@intel.com \
--cc=chou.cosmo@gmail.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=cosmo.chou@quantatw.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jdelvare@suse.com \
--cc=jernej.skrabec@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=macromorgan@hotmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh+dt@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.