From: Stephen Rothwell <sfr@canb•auug.org.au>
To: 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>,
Peter Zijlstra <peterz@infradead•org>
Cc: 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: linux-next: duplicate patches in the xen-tip tree
Date: Tue, 14 Feb 2023 12:47:00 +1100 [thread overview]
Message-ID: <20230214124700.22f0a62e@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 604 bytes --]
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.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-02-14 1:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 1:47 Stephen Rothwell [this message]
2023-02-14 11:22 ` linux-next: duplicate patches in the xen-tip tree Peter Zijlstra
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=20230214124700.22f0a62e@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=boris.ostrovsky@oracle$(echo .)com \
--cc=hpa@zytor$(echo .)com \
--cc=jgross@suse$(echo .)com \
--cc=konrad.wilk@oracle$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@redhat$(echo .)com \
--cc=per.bilse@citrix$(echo .)com \
--cc=peterz@infradead$(echo .)org \
--cc=sstabellini@kernel$(echo .)org \
--cc=tglx@linutronix$(echo .)de \
--cc=xen-devel@lists$(echo .)xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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