From: Thomas Gleixner <tglx@linutronix.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [GIT pull] x86/urgent for 5.10-rc1
Date: Sun, 25 Oct 2020 19:56:27 +0100 [thread overview]
Message-ID: <87sga23zj8.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <CAHk-=whYsdbVzNdPPFKNY1R0d79jdDv442qx1DwLT=RRq6xxcw@mail.gmail.com>
On Sun, Oct 25 2020 at 11:34, Linus Torvalds wrote:
> On Sun, Oct 25, 2020 at 7:25 AM Thomas Gleixner <tglx@linutronix.de> wrote:
>>
>> Restore the original #DE Oops message so tools which parse crash or dmesg
>> find what they expect.
>
> Hmm. I already got this one from Borislav as a different commit
> (5f1ec1fd3225: "x86/traps: Fix #DE Oops message regression"), so I'm
Hrm. Why didn't I notice?
> skipping this pull request as unnecessary.
Sure.
> I'm assuming nobody has based any work on top of it, and if they have,
> it's not the end of the world to get the duplicate commit, but it
> seems pointless to do a pull that ends up with no code changes at all
> for me.
Fair enough.
next prev parent reply other threads:[~2020-10-25 18:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-25 14:25 [GIT pull] locking/urgent " Thomas Gleixner
2020-10-25 14:25 ` [GIT pull] perf/urgent " Thomas Gleixner
2020-10-25 18:35 ` pr-tracker-bot
2020-10-25 14:25 ` [GIT pull] sched/urgent " Thomas Gleixner
2020-10-25 18:35 ` pr-tracker-bot
2020-10-25 14:25 ` [GIT pull] timers/urgent " Thomas Gleixner
2020-10-25 18:35 ` pr-tracker-bot
2020-10-25 14:25 ` [GIT pull] x86/urgent " Thomas Gleixner
2020-10-25 18:34 ` Linus Torvalds
2020-10-25 18:56 ` Thomas Gleixner [this message]
2020-10-25 18:35 ` [GIT pull] locking/urgent " pr-tracker-bot
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=87sga23zj8.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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
all inboxes | Powered by JetHome®