From: Peter Zijlstra <peterz@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Juergen Gross <jgross@suse.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Xen Devel <xen-devel@lists.xenproject.org>,
Per Bilse <per.bilse@citrix.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the xen-tip tree
Date: Tue, 14 Feb 2023 12:22:17 +0100 [thread overview]
Message-ID: <Y+tu6Xqqb6cdiDAA@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20230214124700.22f0a62e@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
On Tue, Feb 14, 2023 at 12:47:00PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> The following commits are also in the tip tree as different commits
> (but the same patches):
>
> 415dab3c1796 ("drivers/xen/hypervisor: Expose Xen SIF flags to userspace")
> 336f560a8917 ("x86/xen: don't let xen_pv_play_dead() return")
> f697cb00afa9 ("x86/xen: mark xen_pv_play_dead() as __noreturn")
>
> These are commits
>
> 859761e770f8 ("drivers/xen/hypervisor: Expose Xen SIF flags to userspace")
> 076cbf5d2163 ("x86/xen: don't let xen_pv_play_dead() return")
> 1aff0d2658e5 ("x86/xen: mark xen_pv_play_dead() as __noreturn")
>
> in the tip tree.
This was intentional (dependencies) and the plan is to only offer the
tip branch for merge after the Xen tree goes in.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-02-14 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 1:47 linux-next: duplicate patches in the xen-tip tree Stephen Rothwell
2023-02-14 11:22 ` Peter Zijlstra [this message]
2023-02-21 8:39 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2025-03-25 22:03 Stephen Rothwell
2025-03-28 4:19 ` Stephen Rothwell
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=Y+tu6Xqqb6cdiDAA@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=per.bilse@citrix.com \
--cc=sfr@canb.auug.org.au \
--cc=sstabellini@kernel.org \
--cc=tglx@linutronix.de \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.