From: <Sergiu.Moga@microchip.com>
To: <lkp@intel.com>, <gregkh@linuxfoundation.org>, <krzk@kernel.org>
Cc: <kbuild-all@lists.01.org>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Solve warning regarding inexistent atmel-usart binding
Date: Mon, 26 Sep 2022 13:43:47 +0000 [thread overview]
Message-ID: <05455d1c-2c7b-a2ae-c9a8-c4381019efa4@microchip.com> (raw)
In-Reply-To: <202209241552.d7FasbxD-lkp@intel.com>
On 24.09.2022 10:32, kernel test robot wrote:
> Hi Sergiu,
>
> Thank you for the patch! Perhaps something to improve:
>
> [auto build test WARNING on lwn-2.6/docs-next]
> [also build test WARNING on linus/master v6.0-rc6 next-20220923]
> [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/Sergiu-Moga/MAINTAINERS-Solve-warning-regarding-inexistent-atmel-usart-binding/20220923-193737
> base: git://git.lwn.net/linux-2.6 docs-next
> reproduce:
> # https://github.com/intel-lab-lkp/linux/commit/c9b63912686e3725733b4de1978d4eb8a0d40ba4
> git remote add linux-review https://github.com/intel-lab-lkp/linux
> git fetch --no-tags linux-review Sergiu-Moga/MAINTAINERS-Solve-warning-regarding-inexistent-atmel-usart-binding/20220923-193737
> git checkout c9b63912686e3725733b4de1978d4eb8a0d40ba4
> make menuconfig
> # enable CONFIG_COMPILE_TEST, CONFIG_WARN_MISSING_DOCUMENTS, CONFIG_WARN_ABI_ERRORS
> 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: MAINTAINERS references a file that doesn't exist: Documentation/devicetree/bindings/serial/atmel,at91-usart.yaml
>
> --
> 0-DAY CI Kernel Test Service
> https://01.org/lkp
The tree that this warning is reported on does not have the patch[1]
that this very fix relies on to make it valid. Therefore, I believe this
can be ignored.
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-next&id=b9e947fbf008769ffda1028f627d604757e62265
Regards,
Sergiu
prev parent reply other threads:[~2022-09-26 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 11:34 [PATCH] MAINTAINERS: Solve warning regarding inexistent atmel-usart binding Sergiu Moga
2022-09-23 11:42 ` Greg KH
2022-09-23 11:46 ` Sergiu.Moga
2022-09-23 13:19 ` Nicolas Ferre
2022-09-24 7:32 ` kernel test robot
2022-09-26 13:43 ` Sergiu.Moga [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=05455d1c-2c7b-a2ae-c9a8-c4381019efa4@microchip.com \
--to=sergiu.moga@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@lists.01.org \
--cc=krzk@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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).