mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Akiyoshi Kurita <weibu@redadmin.org>,
	Akira@www.redadmin.org, Yokosawa@www.redadmin.org,
	akiyks@gmail.com, Jonathan@www.redadmin.org,
	Corbet@www.redadmin.org, corbet@lwn.net
Cc: oe-kbuild-all@lists.linux.dev, Shuah@www.redadmin.org,
	Khan@www.redadmin.org, skhan@linuxfoundation.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Akiyoshi Kurita <weibu@redadmin.org>
Subject: Re: [PATCH] docs/ja_JP: translate submitting-patches.rst (review and report tags)
Date: Mon, 7 Sep 2026 14:55:37 +0200	[thread overview]
Message-ID: <202609071452.EmRYk0Iq-lkp@intel.com> (raw)
In-Reply-To: <20260903020356.1055420-1-weibu@redadmin.org>

Hi Akiyoshi,

kernel test robot noticed the following build warnings:

[auto build test WARNING on lwn/docs-next]
[also build test WARNING on linus/master v7.3-rc2 next-20260902]
[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/Akiyoshi-Kurita/docs-ja_JP-translate-submitting-patches-rst-review-and-report-tags/20260903-110356
base:   git://git.lwn.net/linux.git docs-next
patch link:    https://lore.kernel.org/r/20260903020356.1055420-1-weibu%40redadmin.org
patch subject: [PATCH] docs/ja_JP: translate submitting-patches.rst (review and report tags)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
docutils: docutils (Docutils 0.21.2, Python 3.13.5, on linux)
reproduce: (https://download.01.org/0day-ci/archive/20260907/202609071452.EmRYk0Iq-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/202609071452.EmRYk0Iq-lkp@intel.com/

All warnings (new ones prefixed by >>):

   Relational referents
   ~~~~~~~~~~~~~~~~~~~~~ [docutils]
>> Documentation/translations/ja_JP/process/submitting-patches.rst:666: WARNING: duplicate label tagging_people, other instance in Documentation/process/submitting-patches.rst
   Documentation/userspace-api/landlock:572: ./security/landlock/errata/abi-4.h:5: ERROR: Unexpected section title.


vim +666 Documentation/translations/ja_JP/process/submitting-patches.rst

   665	
 > 666	.. _tagging_people:

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

  parent reply	other threads:[~2026-09-07 12:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03  2:03 Akiyoshi Kurita
2026-09-07  9:23 ` Akira Yokosawa
2026-09-07 12:55 ` kernel test robot [this message]
2026-09-10  1:14 ` [PATCH v2] " Akiyoshi Kurita

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=202609071452.EmRYk0Iq-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Akira@www.redadmin.org \
    --cc=Corbet@www.redadmin.org \
    --cc=Jonathan@www.redadmin.org \
    --cc=Khan@www.redadmin.org \
    --cc=Shuah@www.redadmin.org \
    --cc=Yokosawa@www.redadmin.org \
    --cc=akiyks@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=skhan@linuxfoundation.org \
    --cc=weibu@redadmin.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®