Re: [libgpiod][PATCH] doc: add configuration to generate doxygen documentation on readthedocs.

Re: [libgpiod][PATCH] doc: add configuration to generate doxygen documentation on readthedocs.

[kernel test robot]

Hi Kent,

kernel test robot noticed the following build warnings:

[auto build test WARNING on linus/master]
[also build test WARNING on v6.4-rc5 next-20230609]
[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/Kent-Gibson/doc-add-configuration-to-generate-doxygen-documentation-on-readthedocs/20230610-100330
base:   linus/master
patch link:    https://lore.kernel.org/r/20230610020148.8973-1-warthog618%40gmail.com
patch subject: [libgpiod][PATCH] doc: add configuration to generate doxygen documentation on readthedocs.
config: powerpc-randconfig-r035-20230610 (https://download.01.org/0day-ci/archive/20230610/202306101327.8CQ451FM-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build):
        mkdir -p ~/bin
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # install powerpc cross compiling tool for clang build
        # apt-get install binutils-powerpc-linux-gnu
        git checkout linus/master
        b4 shazam https://lore.kernel.org/r/20230610020148.8973-1-warthog618@gmail.com
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang ~/bin/make.cross W=1 O=build_dir ARCH=powerpc olddefconfig
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang ~/bin/make.cross W=1 O=build_dir ARCH=powerpc SHELL=/bin/bash

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/202306101327.8CQ451FM-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> .readthedocs.yaml: warning: ignored by one of the .gitignore files
   tools/testing/selftests/arm64/tags/.gitignore: warning: ignored by one of the .gitignore files
   tools/testing/selftests/arm64/tags/Makefile: warning: ignored by one of the .gitignore files
   tools/testing/selftests/arm64/tags/run_tags_test.sh: warning: ignored by one of the .gitignore files
   tools/testing/selftests/arm64/tags/tags_test.c: warning: ignored by one of the .gitignore files
   tools/testing/selftests/kvm/.gitignore: warning: ignored by one of the .gitignore files
   tools/testing/selftests/kvm/Makefile: warning: ignored by one of the .gitignore files
   tools/testing/selftests/kvm/config: warning: ignored by one of the .gitignore files
   tools/testing/selftests/kvm/settings: warning: ignored by one of the .gitignore files

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

Re: [libgpiod][PATCH] doc: add configuration to generate doxygen documentation on readthedocs.

[Kent Gibson]

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.

Re: [libgpiod][PATCH] doc: add configuration to generate doxygen documentation on readthedocs.

[Bartosz Golaszewski]

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?

Anyway, I'm not sure where to report this. Looks like the robot lives
on github, so I'll try opening an issue there.

Bart

Re: [libgpiod][PATCH] doc: add configuration to generate doxygen documentation on readthedocs.

[Philip Li]

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
>