From: Kent Gibson <warthog618@gmail.com>
To: brgl@bgdev.pl
Cc: linux-gpio@vger.kernel.org, llvm@lists.linux.dev,
oe-kbuild-all@lists.linux.dev
Subject: Re: [libgpiod][PATCH] doc: add configuration to generate doxygen documentation on readthedocs.
Date: Sat, 10 Jun 2023 13:43:08 +0800 [thread overview]
Message-ID: <ZIQNbB30BUsirOr1@sol> (raw)
In-Reply-To: <202306101327.8CQ451FM-lkp@intel.com>
On Sat, Jun 10, 2023 at 01:20:47PM +0800, kernel test robot wrote:
> Hi Kent,
>
> kernel test robot noticed the following build warnings:
>
Ok, not sure what to make of that - why is the test robot concerned with
libgpiod patches?
The files in the patch aren't ignored by the .gitignores in the libgpiod
tree, so it must've applied the patch to the linux tree - which doesn't
like dot-files. That wont end well either way.
Can we tell the test robot not to try paddling around in the libgpiod
pool, e.g. ignore patches with the [libgpiod] prefix?
Cheers,
Kent.
next prev parent reply other threads:[~2023-06-10 5:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230610020148.8973-1-warthog618@gmail.com>
2023-06-10 5:20 ` [libgpiod][PATCH] doc: add configuration to generate doxygen documentation on readthedocs kernel test robot
2023-06-10 5:43 ` Kent Gibson [this message]
2023-06-12 12:58 ` Bartosz Golaszewski
2023-06-12 13:40 ` Philip Li
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=ZIQNbB30BUsirOr1@sol \
--to=warthog618@gmail.com \
--cc=brgl@bgdev.pl \
--cc=linux-gpio@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--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