From: Sean Christopherson <seanjc@google.com>
To: kernel test robot <yujie.liu@intel.com>
Cc: Edward Liaw <edliaw@google.com>,
oe-kbuild-all@lists.linux.dev,
Muhammad Usama Anjum <usama.anjum@collabora.com>
Subject: Re: [sean-jc:x86/gnu_source 41/42] tools/testing/selftests/kvm/rseq_test.c:223:undefined reference to `rseq_register_current_thread'
Date: Wed, 15 May 2024 08:23:52 -0700 [thread overview]
Message-ID: <ZkTG2WGnADfprMbH@google.com> (raw)
In-Reply-To: <202405141601.VXdtmd3C-lkp@intel.com>
On Wed, May 15, 2024, kernel test robot wrote:
> Hi Edward,
>
> First bad commit (maybe != root cause):
>
> tree: https://github.com/sean-jc/linux x86/gnu_source
Ignore this Edward, this is due to a bad merge conflict resolution in a branch in
my personal repo that I was using for review+testing. I'll simply delete the branch.
prev parent reply other threads:[~2024-05-15 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 1:42 [sean-jc:x86/gnu_source 41/42] tools/testing/selftests/kvm/rseq_test.c:223:undefined reference to `rseq_register_current_thread' kernel test robot
2024-05-15 15:23 ` Sean Christopherson [this message]
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=ZkTG2WGnADfprMbH@google.com \
--to=seanjc@google.com \
--cc=edliaw@google.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=usama.anjum@collabora.com \
--cc=yujie.liu@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).