mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] x86/urgent for v5.10-rc1
Date: Tue, 13 Oct 2020 19:36:15 +0200	[thread overview]
Message-ID: <20201013173615.GI32151@zn.tnic> (raw)

Hi Linus,

here's the clang build warning fix from yesterday which is finally
ready. I've added a second one from the tip's urgent queue which could
go in now too.

Please pull,
thx.

---

The following changes since commit 8b6591fd0ac8b7e8b2873703bc24b71a6f3d2d3e:

  Merge tag 'x86_platform_for_v5.10' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (2020-10-12 10:31:18 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_urgent_for_v5.10-rc1

for you to fetch changes up to 081dd68c89061077930ec7776d98837cb64b0405:

  x86/platform/uv: Remove unused variable in UV5 NMI handler (2020-10-13 19:21:13 +0200)

----------------------------------------------------------------
- Fix the #DE oops message string format which confused tools parsing
crash information. (Thomas Gleixner)

- Remove an unused variable in the UV5 code which was triggering a build
warning with clang. (Mike Travis)

----------------------------------------------------------------
Mike Travis (1):
      x86/platform/uv: Remove unused variable in UV5 NMI handler

Thomas Gleixner (1):
      x86/traps: Fix #DE Oops message regression

 arch/x86/kernel/traps.c       | 2 +-
 arch/x86/platform/uv/uv_nmi.c | 3 ---
 2 files changed, 1 insertion(+), 4 deletions(-)

-- 
Regards/Gruss,
    Boris.

SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg

             reply	other threads:[~2020-10-13 17:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13 17:36 Borislav Petkov [this message]
2020-10-13 19:47 ` 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=20201013173615.GI32151@zn.tnic \
    --to=bp@suse.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®