From: Tony Lindgren <tony@atomide.com>
To: kernel test robot <lkp@intel.com>, Arnd Bergmann <arnd@arndb.de>
Cc: Andreas Kemnade <andreas@kemnade.info>,
oe-kbuild-all@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, arm@kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [soc:omap/maintainers 1/1] htmldocs: Warning: MAINTAINERS references a file that doesn't exist: Documentation/devicetree/bindings/arm/ti/omap.yaml
Date: Tue, 15 Aug 2023 09:23:05 +0300 [thread overview]
Message-ID: <20230815062305.GS11676@atomide.com> (raw)
In-Reply-To: <202308142025.Bua4jLjW-lkp@intel.com>
Hi,
Adding Arnd as these branches are now in the arm-soc tree.
* kernel test robot <lkp@intel.com> [230814 13:06]:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git omap/maintainers
> head: fda31904ffbc7231898198333804fa551b681387
> commit: fda31904ffbc7231898198333804fa551b681387 [1/1] MAINTAINERS: add board bindings list to OMAP2+ files
> reproduce: (https://download.01.org/0day-ci/archive/20230814/202308142025.Bua4jLjW-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/202308142025.Bua4jLjW-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> >> Warning: MAINTAINERS references a file that doesn't exist: Documentation/devicetree/bindings/arm/ti/omap.yaml
Looks like this is caused by pull request branch for "Devicetree binding
changes for omaps for v6.6" not being merged into pull request
branch "Maintainer file list update for omaps for v6.6".
Regards,
Tony
prev parent reply other threads:[~2023-08-15 6:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 13:06 [soc:omap/maintainers 1/1] htmldocs: Warning: MAINTAINERS references a file that doesn't exist: Documentation/devicetree/bindings/arm/ti/omap.yaml kernel test robot
2023-08-15 6:23 ` Tony Lindgren [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=20230815062305.GS11676@atomide.com \
--to=tony@atomide.com \
--cc=andreas@kemnade.info \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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).