From: kernel test robot <lkp@intel.com>
To: Costa Shulyupin <costa.shul@redhat.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
Muchun Song <muchun.song@linux.dev>,
Jonathan Corbet <corbet@lwn.net>,
linux-mm@kvack.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Costa Shulyupin <costa.shul@redhat.com>
Subject: Re: [PATCH] docs: update link to powerpc/vmemmap_dedup.rst
Date: Fri, 29 Sep 2023 18:30:02 +0800 [thread overview]
Message-ID: <202309291832.6j4oF2eE-lkp@intel.com> (raw)
In-Reply-To: <20230927164319.2686237-1-costa.shul@redhat.com>
Hi Costa,
kernel test robot noticed the following build warnings:
[auto build test WARNING on lwn/docs-next]
[also build test WARNING on linus/master v6.6-rc3 next-20230929]
[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/Costa-Shulyupin/docs-update-link-to-powerpc-vmemmap_dedup-rst/20230928-004508
base: git://git.lwn.net/linux.git docs-next
patch link: https://lore.kernel.org/r/20230927164319.2686237-1-costa.shul%40redhat.com
patch subject: [PATCH] docs: update link to powerpc/vmemmap_dedup.rst
reproduce: (https://download.01.org/0day-ci/archive/20230929/202309291832.6j4oF2eE-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/202309291832.6j4oF2eE-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: Documentation/mm/vmemmap_dedup.rst references a file that doesn't exist: Documentation/arch/powerpc/vmemmap_dedup.rst
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-09-29 10:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 16:43 [PATCH] docs: update link to powerpc/vmemmap_dedup.rst Costa Shulyupin
2023-09-29 10:30 ` kernel test robot [this message]
2023-10-10 19:30 ` Jonathan Corbet
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=202309291832.6j4oF2eE-lkp@intel.com \
--to=lkp@intel.com \
--cc=corbet@lwn.net \
--cc=costa.shul@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=muchun.song@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;
as well as URLs for NNTP newsgroup(s).