From: Thomas Gleixner <tglx@linutronix.de>
To: "Luck, Tony" <tony.luck@intel.com>, LKML <linux-kernel@vger.kernel.org>
Cc: "x86@kernel.org" <x86@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Linus Torvalds <torvalds@linux-foundation.org>,
Song Liu <songliubraving@fb.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Peter Ziljstra <peterz@infradead.org>
Subject: RE: [patch V2 00/20] x86/fpu: Clean up exception fixups and error handling in sigframe related code
Date: Wed, 08 Sep 2021 07:14:56 +0200 [thread overview]
Message-ID: <87pmtj8x7z.ffs@tglx> (raw)
In-Reply-To: <cf9a841219904c048983fe2aee578761@intel.com>
On Wed, Sep 08 2021 at 04:06, Tony Luck wrote:
>>> Huch? That tree is based on 0bcfe68b876 and it just has those 20 patches
>>> on top which should not at all interfere with your root filesystem
>>> device. Let me verify.
>>
>> I lost connection to my test machines. Will continue tomorrow morning.
>
> To save you some time I ran a bisect. It says the wheels fall off the bus at
> patch 13/2
Yes, but that's not the real culprit. That's just the messenger.
next prev parent reply other threads:[~2021-09-08 5:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 19:56 [patch V2 00/20] x86/fpu: Clean up exception fixups and error handling in sigframe related code Thomas Gleixner
2021-09-07 20:04 ` Thomas Gleixner
2021-09-07 20:07 ` Luck, Tony
2021-09-07 20:18 ` Thomas Gleixner
2021-09-07 21:13 ` Luck, Tony
2021-09-07 21:55 ` Thomas Gleixner
2021-09-07 22:37 ` Thomas Gleixner
2021-09-07 23:20 ` Linus Torvalds
2021-09-07 23:22 ` Linus Torvalds
2021-09-08 13:22 ` Thomas Gleixner
2021-09-08 4:06 ` Luck, Tony
2021-09-08 5:14 ` Thomas Gleixner [this message]
2021-09-08 13:21 ` Thomas Gleixner
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=87pmtj8x7z.ffs@tglx \
--to=tglx@linutronix.de \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.com \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=x86@kernel.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.