From: Michael Ellerman <mpe@ellerman.id.au>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
Yang Li <yang.lee@linux.alibaba.com>,
npiggin@gmail.com, naveen@kernel.org, maddy@linux.ibm.com
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH -next] powerpc/machdep: Remove duplicated include in svm.c
Date: Fri, 08 Nov 2024 10:49:44 +1100 [thread overview]
Message-ID: <878qtud2p3.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <ed3a5d53-af06-498f-a8fe-0fe1e3a293bc@csgroup.eu>
Christophe Leroy <christophe.leroy@csgroup.eu> writes:
> Le 07/11/2024 à 12:29, Michael Ellerman a écrit :
>> Yang Li <yang.lee@linux.alibaba.com> writes:
>>> The header files linux/mem_encrypt.h is included twice in svm.c,
>>> so one inclusion of each can be removed.
>>>
>>> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
>>> Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=11750
>>> Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
>>> ---
>>> arch/powerpc/platforms/pseries/svm.c | 1 -
>>> 1 file changed, 1 deletion(-)
>>
>> The two includes only appear in linux-next, and they both come from
>> different trees. They are required in each tree to avoid breaking the
>> build.
>>
>> So no one can merge this patch until the two trees are merged into mainline.
>
> But can't those two trees coordinate the patches so that the include
> goes at the same place avoiding duplication at merge ?
Yes that would work.
Except that in this case it's too late because the commits have already
been applied to both trees for over a week - neither maintainer is going
to want to rebase for something trivial like a duplicated header.
I could apply a patch to my tree to move the include to the same line as
the commit in the DMA tree, but even that seems like overkill for a
duplicated header.
I'll try and remember to apply this once the trees are merged in
mainline. But if not the bot that detected it in the first place can
just detect it again and repost.
cheers
next prev parent reply other threads:[~2024-11-07 23:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 1:02 [PATCH -next] powerpc/machdep: Remove duplicated include in svm.c Yang Li
2024-11-07 11:29 ` Michael Ellerman
2024-11-07 11:33 ` Christophe Leroy
2024-11-07 23:49 ` Michael Ellerman [this message]
2024-11-25 7:26 ` Christophe Leroy
2024-11-26 2:57 ` Michael Ellerman
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=878qtud2p3.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=abaci@linux.alibaba.com \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=naveen@kernel.org \
--cc=npiggin@gmail.com \
--cc=yang.lee@linux.alibaba.com \
/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).