From: Hu Haowen <src.res.211@gmail.com>
To: Stephen Rothwell <sfr@rothwell.id.au>, kernel test robot <lkp@intel.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [srcres258-doc:next 1/1] mm/memory-failure.c:1891:6: error: redefinition of 'is_raw_hwpoison_page_in_hugepage'
Date: Tue, 18 Jul 2023 23:04:26 +0800 [thread overview]
Message-ID: <433ced5a-7a04-e54c-8774-e2a1ae514ffc@gmail.com> (raw)
In-Reply-To: <20230718202633.7578c89e@pine.rothwell.emu.id.au>
On 2023/7/18 18:26, Stephen Rothwell wrote:
> Hi,
>
> On Tue, 18 Jul 2023 17:42:05 +0800 kernel test robot <lkp@intel.com> wrote:
>>
>> tree: https://github.com/srcres258/linux-doc next
>
> This is not the linux-next tree. It is a tree that merges linux-next
> every now and then which is *not* how to work with linux-next and will
> create lots of merge conflicts which may, or may not, be resolved
> correctly. Please do *not* report any problems with this tree to me.
Sorry for troubling you, Stephen. It might be a misunderstanding for the
kernel test robot as the address of my tree is mentioned within
MAINTAINERS and it is detected and put into CI automatically. In truth
the tree has nothing to do with Stephen's linux-next tree and it is used
by myself for kernel documentation translation stuffs.
Consequently my intention is identical with Stephen - to disable the CI
jobs and error reports as it might act as junk information for both
Stephen and myself.
Thanks,
Hu Haowen
>
next prev parent reply other threads:[~2023-07-18 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 9:42 [srcres258-doc:next 1/1] mm/memory-failure.c:1891:6: error: redefinition of 'is_raw_hwpoison_page_in_hugepage' kernel test robot
2023-07-18 10:26 ` Stephen Rothwell
2023-07-18 15:04 ` Hu Haowen [this message]
2023-07-18 15:38 ` Philip Li
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=433ced5a-7a04-e54c-8774-e2a1ae514ffc@gmail.com \
--to=src.res.211@gmail.com \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sfr@canb.auug.org.au \
--cc=sfr@rothwell.id.au \
/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