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: Tue, 07 Sep 2021 23:55:40 +0200 [thread overview]
Message-ID: <87v93c82zn.ffs@tglx> (raw)
In-Reply-To: <a883fe85b6b941b9bff44bc4b268bba1@intel.com>
On Tue, Sep 07 2021 at 21:13, Tony Luck wrote:
>>> Was it just the email post that was bad? I.e. are the patches in:
>>>
>>> git://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git x86/fpu
>>>
>>> ok? I just compiled that, should I boot it, or wait?
>>
>> Just the mail script went south. The git tree is fine.
>
> What else is in that tree? My kernel doesn't boot (fails to find root filesystem device).
> Same .config boots Linus latest (HEAD= 0bcfe68b876 Revert "memcg: enable accounting for pollfd and select bits arrays")
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.
Thanks,
tglx
next prev parent reply other threads:[~2021-09-07 21:55 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 [this message]
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
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=87v93c82zn.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox