Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:4 as permitted sender) client-ip=2620:137:e000::3:4;
Date:   Mon, 11 Dec 2023 09:49:38 -0800
In-Reply-To: <20231211085956.25bedfe4@canb.auug.org.au>
Mime-Version: 1.0
References: <20231211085956.25bedfe4@canb.auug.org.au>
Message-ID: <ZXdLsg1tN4DfBBSy@google.com>
Subject: Re: linux-next: duplicate patches in the kvm tree
From:   Sean Christopherson <seanjc@google.com>
To:     Stephen Rothwell <sfr@canb.auug.org.au>
Cc:     Paolo Bonzini <pbonzini@redhat.com>, KVM <kvm@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
Precedence: bulk

On Mon, Dec 11, 2023, Stephen Rothwell wrote:
> Hi all,
> 
> The following commits are also in Linus Torvalds' tree as different
> commits (but the same patches):
> 
>   3b99d46a1170 ("KVM: selftests: Actually print out magic token in NX hugepages skip message")
>   fc6543bb55d4 ("KVM: selftests: add -MP to CFLAGS")
> 
> These are commits
> 
>   4a073e813477 ("KVM: selftests: Actually print out magic token in NX hugepages skip message")
>   96f124015f82 ("KVM: selftests: add -MP to CFLAGS")
> 
> in Linus' tree.

This is my bad, I used the wrong base for a selftests branch.  My understanding
is that we're just going to eat the duplicate commits.