From: Philip Li <philip.li@intel.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Kent Gibson <warthog618@gmail.com>, <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: Mon, 12 Jun 2023 21:40:06 +0800 [thread overview]
Message-ID: <ZIcgNne/L0lTpdAd@rli9-mobl> (raw)
In-Reply-To: <CAMRc=MeLYqU8HuqVs7wGpAjZ6U+_J3TMsNonknup=hOSPqj2bQ@mail.gmail.com>
On Mon, Jun 12, 2023 at 02:58:28PM +0200, Bartosz Golaszewski wrote:
> On Sat, Jun 10, 2023 at 7:43 AM Kent Gibson <warthog618@gmail.com> wrote:
> >
> > 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.
>
> Normally the robot can figure out non-kernel patches. I think this
> time it got confused by the commit only adding a new file and tried to
> apply it to the kernel?
Sorry for the false positive. Yes, this is the case, the patch was successfully
applied and wrongly considered as kernel patch. We will fix the logic in next
few days to avoid such problem.
>
> Anyway, I'm not sure where to report this. Looks like the robot lives
> on github, so I'll try opening an issue there.
Thanks, yes, github https://github.com/intel/lkp-tests could be used to report
any issue related to the bot. Or you can drop mail to lkp@intel.com, that we
monitor the mail tightly.
>
> Bart
>
next prev parent reply other threads:[~2023-06-12 13:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-10 2:01 [libgpiod][PATCH] doc: add configuration to generate doxygen documentation on readthedocs Kent Gibson
2023-06-10 5:20 ` kernel test robot
2023-06-10 5:43 ` Kent Gibson
2023-06-12 12:58 ` Bartosz Golaszewski
2023-06-12 13:40 ` Philip Li [this message]
2023-06-10 5:42 ` kernel test robot
2023-06-12 16:27 ` Bartosz Golaszewski
2023-06-12 16:40 ` Kent Gibson
2023-06-12 17:30 ` Bartosz Golaszewski
-- strict thread matches above, loose matches on Subject: below --
2022-03-05 9:40 Kent Gibson
2022-03-07 9:16 ` Bartosz Golaszewski
2022-03-07 9:30 ` Kent Gibson
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=ZIcgNne/L0lTpdAd@rli9-mobl \
--to=philip.li@intel.com \
--cc=brgl@bgdev.pl \
--cc=linux-gpio@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=warthog618@gmail.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).