From: kernel test robot <lkp@intel.com>
To: Lorenzo Bianconi <lorenzo@kernel.org>, netdev@vger.kernel.org
Cc: kbuild-all@lists.01.org, ilias.apalodimas@linaro.org,
hawk@kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, corbet@lwn.net,
linux-doc@vger.kernel.org, jbrouer@redhat.com,
lorenzo.bianconi@redhat.com
Subject: Re: [PATCH v2 net-next] Documentation: update networking/page_pool.rst with ethtool APIs
Date: Mon, 4 Jul 2022 06:47:33 +0800 [thread overview]
Message-ID: <202207040608.lU2e57H3-lkp@intel.com> (raw)
In-Reply-To: <8c1f582d286fd5a7406dfff895eea39bb8fedca6.1654546043.git.lorenzo@kernel.org>
Hi Lorenzo,
I love your patch! Perhaps something to improve:
[auto build test WARNING on net-next/master]
url: https://github.com/intel-lab-lkp/linux/commits/Lorenzo-Bianconi/Documentation-update-networking-page_pool-rst-with-ethtool-APIs/20220607-041741
base: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git 58f9d52ff689a262bec7f5713c07f5a79e115168
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/networking/page_pool.rst:154: WARNING: Unexpected indentation.
vim +154 Documentation/networking/page_pool.rst
151
152 * page_pool_ethtool_stats_get_strings(): reports page_pool ethtool stats
153 strings according to the struct page_pool_stats
> 154 * rx_pp_alloc_fast
155 * rx_pp_alloc_slow
156 * rx_pp_alloc_slow_ho
157 * rx_pp_alloc_empty
158 * rx_pp_alloc_refill
159 * rx_pp_alloc_waive
160 * rx_pp_recycle_cached
161 * rx_pp_recycle_cache_full
162 * rx_pp_recycle_ring
163 * rx_pp_recycle_ring_full
164 * rx_pp_recycle_released_ref
165
--
0-DAY CI Kernel Test Service
https://01.org/lkp
prev parent reply other threads:[~2022-07-03 22:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 20:15 [PATCH v2 net-next] Documentation: update networking/page_pool.rst with ethtool APIs Lorenzo Bianconi
2022-06-08 4:00 ` Jakub Kicinski
2022-06-08 14:20 ` Lorenzo Bianconi
2022-07-03 22:47 ` 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=202207040608.lU2e57H3-lkp@intel.com \
--to=lkp@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=jbrouer@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=lorenzo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).