netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yujie Liu <yujie.liu@intel.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: kernel test robot <lkp@intel.com>, <davem@davemloft.net>,
	<oe-kbuild-all@lists.linux.dev>, <netdev@vger.kernel.org>,
	<edumazet@google.com>, <pabeni@redhat.com>, <corbet@lwn.net>,
	<leitao@debian.org>, <linux-doc@vger.kernel.org>
Subject: Re: [PATCH net-next] docs: netlink: link to family documentations from spec info
Date: Thu, 30 Nov 2023 16:52:10 +0800	[thread overview]
Message-ID: <ZWhNOvnxSMAudjXM@yujie-X299> (raw)
In-Reply-To: <20231127190611.37a94d4c@kernel.org>

On Mon, Nov 27, 2023 at 07:06:11PM -0800, Jakub Kicinski wrote:
> On Tue, 28 Nov 2023 11:01:55 +0800 kernel test robot wrote:
> > Hi Jakub,
> > 
> > kernel test robot noticed the following build warnings:
> > 
> > [auto build test WARNING on net-next/main]
> > 
> > url:    https://github.com/intel-lab-lkp/linux/commits/Jakub-Kicinski/docs-netlink-link-to-family-documentations-from-spec-info/20231128-050136
> > base:   net-next/main
> > patch link:    https://lore.kernel.org/r/20231127205642.2293153-1-kuba%40kernel.org
> > patch subject: [PATCH net-next] docs: netlink: link to family documentations from spec info
> > reproduce: (https://download.01.org/0day-ci/archive/20231128/202311280834.lYzXIFc4-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/202311280834.lYzXIFc4-lkp@intel.com/
> > 
> > All warnings (new ones prefixed by >>):
> > 
> > >> Warning: Documentation/userspace-api/netlink/specs.rst references a file that doesn't exist: Documentation/networking/netlink_spec/index.rst  
> 
> Is it possible that the build bot is missing python-yaml support and
> the generation of Documentation/networking/netlink_spec/index.rst
> fails?

Hi Jakub, this is indeed due to missing pyyaml module in the bot so the
doc file is not generated. We've installed it now and the warning is
gone. Sorry for the noise and please ignore this report.

> 
> Or is this an ordering issue?
> 

  reply	other threads:[~2023-11-30  8:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27 20:56 [PATCH net-next] docs: netlink: link to family documentations from spec info Jakub Kicinski
2023-11-28  3:01 ` kernel test robot
2023-11-28  3:06   ` Jakub Kicinski
2023-11-30  8:52     ` Yujie Liu [this message]
2023-11-30 15:05       ` Jakub Kicinski
2023-11-28  9:39 ` Breno Leitao
2023-11-28 10:21 ` Donald Hunter

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=ZWhNOvnxSMAudjXM@yujie-X299 \
    --to=yujie.liu@intel.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=leitao@debian.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --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).