From: Krzysztof Kozlowski <krzk@kernel.org>
To: kernel test robot <lkp@intel.com>,
Florian Fainelli <f.fainelli@gmail.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Rob Herring <robh@kernel.org>,
linux-doc@vger.kernel.org
Subject: Re: [krzk-mem-ctrl:for-v6.1/brcm-stb 1/3] htmldocs: Warning: Documentation/devicetree/bindings/arm/bcm/brcm,brcmstb.txt references a file that doesn't exist: Documentation/devicetree/bindings/memory-controllers/brcm,memc.yaml
Date: Thu, 18 Aug 2022 09:09:54 +0300 [thread overview]
Message-ID: <427c0198-850c-17a7-f0d7-954a8252b11a@kernel.org> (raw)
In-Reply-To: <202208180941.oGoLuq8U-lkp@intel.com>
On 18/08/2022 04:59, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux-mem-ctrl.git for-v6.1/brcm-stb
> head: 65991a63d02decf269e7d5334620df0dd5919762
> commit: 0da0b6bf854dcfb047fec70bbbadabb7ff0fcb3e [1/3] dt-bindings: memory-controller: Document Broadcom STB MEMC
> 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 >>):
>
>>> Warning: Documentation/devicetree/bindings/arm/bcm/brcm,brcmstb.txt references a file that doesn't exist: Documentation/devicetree/bindings/memory-controllers/brcm,memc.yaml
I'll fixup the commit.
Florian,
It's useful also to have own development trees covered by LKP.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-08-18 6:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 1:59 kernel test robot
2022-08-18 6:09 ` Krzysztof Kozlowski [this message]
2022-08-20 2:56 ` Florian Fainelli
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=427c0198-850c-17a7-f0d7-954a8252b11a@kernel.org \
--to=krzk@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®