From: kernel test robot <lkp@intel.com>
To: Atif Ofluoglu <Atif.Ofluoglu@analog.com>, linux@roeck-us.net
Cc: kbuild-all@lists.01.org, jdelvare@suse.com,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
Atif Ofluoglu <atif.ofluoglu@analog.com>
Subject: Re: [PATCH 2/2] Added documentation for Maxim Integrated max20754 hwmon userspace sysfs.
Date: Fri, 8 Jul 2022 14:41:38 +0800 [thread overview]
Message-ID: <202207081439.A6GFlbPu-lkp@intel.com> (raw)
In-Reply-To: <a8d037609be3e6f81bc15e2a6c24cb7809e3226b.1657204859.git.atif.ofluoglu@analog.com>
Hi Atif,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on groeck-staging/hwmon-next]
[also build test WARNING on linus/master v5.19-rc5 next-20220707]
[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/Atif-Ofluoglu/Adding-MAX20754-support/20220707-233249
base: https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-next
reproduce: make htmldocs
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> Documentation/hwmon/max20754.rst: WARNING: document isn't included in any toctree
>> Documentation/hwmon/max20754.rst:49: WARNING: Malformed table.
--
0-DAY CI Kernel Test Service
https://01.org/lkp
prev parent reply other threads:[~2022-07-08 6:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 15:29 [PATCH 0/2] Adding MAX20754 support Atif Ofluoglu
2022-07-07 15:29 ` [PATCH 1/2] hwmon: (pmbus/max20754) Add support for MAX20754 Atif Ofluoglu
2022-07-07 18:56 ` kernel test robot
2022-07-13 14:16 ` Guenter Roeck
2022-07-07 15:29 ` [PATCH 2/2] Added documentation for Maxim Integrated max20754 hwmon userspace sysfs Atif Ofluoglu
2022-07-08 6:41 ` kernel test robot [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=202207081439.A6GFlbPu-lkp@intel.com \
--to=lkp@intel.com \
--cc=Atif.Ofluoglu@analog.com \
--cc=jdelvare@suse.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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