From: Nathan Chancellor <nathan@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Sean Christopherson <seanjc@google.com>,
Chao Gao <chao.gao@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Vishal Verma <vishal.l.verma@intel.com>
Subject: Re: linux-next: manual merge of the kvm-x86 tree with the tip tree
Date: Fri, 6 Mar 2026 15:48:54 -0700 [thread overview]
Message-ID: <20260306224854.GB2746259@ax162> (raw)
In-Reply-To: <20b59abc-096e-4578-9935-0aaf80dc90d8@sirena.org.uk>
On Fri, Mar 06, 2026 at 01:24:34PM +0000, Mark Brown wrote:
> On Thu, Mar 05, 2026 at 12:24:01PM -0700, Nathan Chancellor wrote:
>
> > This obviously clears it. Mark, can that be applied to whichever merge
> > happens second?
>
> I manually made a change which hopefully matches that, your patch failed
> patch format detection for some reason...
Thanks, the version in next-20260306 looks good to me.
Cheers,
Nathan
next prev parent reply other threads:[~2026-03-06 22:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 12:21 linux-next: manual merge of the kvm-x86 tree with the tip tree Mark Brown
2026-03-04 23:10 ` Sean Christopherson
2026-03-05 19:24 ` Nathan Chancellor
2026-03-06 13:24 ` Mark Brown
2026-03-06 22:48 ` Nathan Chancellor [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-25 4:59 Stephen Rothwell
2025-11-25 7:09 ` Borislav Petkov
2025-12-04 5:10 ` Stephen Rothwell
2025-11-20 4:52 Stephen Rothwell
2025-11-20 4:46 Stephen Rothwell
2025-10-20 0:07 Stephen Rothwell
2025-09-22 9:50 Mark Brown
2025-09-22 11:27 ` Aithal, Srikanth
2025-09-22 11:40 ` Mark Brown
2025-09-22 13:23 ` Mark Brown
2025-09-22 14:04 ` Sean Christopherson
2025-09-30 18:13 ` Paolo Bonzini
2025-09-19 13:50 Mark Brown
2025-01-06 4:05 Stephen Rothwell
2025-01-09 19:18 ` Sean Christopherson
2025-01-23 3:25 ` Stephen Rothwell
2024-02-07 4:35 Stephen Rothwell
2023-01-19 23:54 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=20260306224854.GB2746259@ax162 \
--to=nathan@kernel.org \
--cc=broonie@kernel.org \
--cc=chao.gao@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=seanjc@google.com \
--cc=vishal.l.verma@intel.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