mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Disha Goel <disgoel@linux.ibm.com>
To: kernel test robot <lkp@intel.com>, shuah@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/filesystems: Move file_stressor to dedicated subdirectory
Date: Thu, 21 May 2026 18:20:25 +0530	[thread overview]
Message-ID: <b9bda4cb-8125-4612-b6ba-9694361e7509@linux.ibm.com> (raw)
In-Reply-To: <202605192100.DvRgEGZ3-lkp@intel.com>

On 19/05/26 6:48 pm, kernel test robot wrote:
> Hi Disha,
> 
> kernel test robot noticed the following build warnings:
> 
> [auto build test WARNING on shuah-kselftest/next]
> [also build test WARNING on shuah-kselftest/fixes linus/master v7.1-rc4 next-20260518]
> [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/Disha-Goel/selftests-filesystems-Move-file_stressor-to-dedicated-subdirectory/20260519-185602
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git next
> patch link:    https://lore.kernel.org/r/20260519104210.11836-1-disgoel%40linux.ibm.com
> patch subject: [PATCH] selftests/filesystems: Move file_stressor to dedicated subdirectory
> config: m68k-allnoconfig (https://download.01.org/0day-ci/archive/20260519/202605192100.DvRgEGZ3-lkp@intel.com/config)
> compiler: m68k-linux-gcc (GCC) 15.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260519/202605192100.DvRgEGZ3-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/202605192100.DvRgEGZ3-lkp@intel.com/
> 
> All warnings (new ones prefixed by >>):
> 
>     Documentation/.renames.txt: warning: ignored by one of the .gitignore files
>>> tools/testing/selftests/filesystems/file_stressor/Makefile: warning: ignored by one of the .gitignore files
>>> tools/testing/selftests/filesystems/file_stressor/file_stressor.c: warning: ignored by one of the .gitignore files
>>> tools/testing/selftests/filesystems/file_stressor/settings: warning: ignored by one of the .gitignore files

Thanks for the report. This has been fixed in v2.

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

-- 
Regards,
Disha


      reply	other threads:[~2026-05-21 12:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-19 10:42 Disha Goel
2026-05-19 10:42 ` [PATCH] selftests/filesystems: allow security.selinux xattr in listxattr kernfs test Disha Goel
2026-05-19 13:18 ` [PATCH] selftests/filesystems: Move file_stressor to dedicated subdirectory kernel test robot
2026-05-21 12:50   ` Disha Goel [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=b9bda4cb-8125-4612-b6ba-9694361e7509@linux.ibm.com \
    --to=disgoel@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=shuah@kernel.org \
    /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

all inboxes | Powered by JetHome®