From: Greg KH <gregkh@linuxfoundation.org>
To: Mike Travis <mike.travis@hpe.com>
Cc: stable@vger.kernel.org
Subject: Re: Fwd: [tip:x86/urgent] x86/platform/UV: Fix critical UV MMR address error
Date: Mon, 9 Apr 2018 22:03:33 +0200 [thread overview]
Message-ID: <20180409200333.GA1811@kroah.com> (raw)
In-Reply-To: <194fcfd1-5324-b392-3c3e-553624beb1ed@hpe.com>
On Mon, Apr 09, 2018 at 10:57:56AM -0700, Mike Travis wrote:
> This was sent to stable@vger.kernel.org almost 2 weeks ago and I haven't
> heard anything back yet. Is there any update on the status? (sorry for the
> bad formatting, this is the only way I can forward the email. I can only
> resend the original email before the commit email from Thomas.)
How did you send it?
Ugh, you bounced it? No wonder I didn't do anything with it at all, it
looked exactly like a "this is being committed to the TIP tree" type
message.
How was I supposed to know what to do with it?
Please be more specific next time, read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
A simple "please commit git id XXXXX to the X.X tree" is all that is
needed.
Wait, in looking closer at this:
> -------- Forwarded Message --------
> Subject: [tip:x86/urgent] x86/platform/UV: Fix critical UV MMR address error
> Date: Wed, 28 Mar 2018 11:25:04 -0700
> From: tip-bot for mike.travis@hpe.com <tipbot@zytor.com>
> Reply-To: andrew.banman@hpe.com, hpa@zytor.com, tglx@linutronix.de,
> mingo@kernel.org, russ.anderson@hpe.com, travis@sgi.com,
> linux-kernel@vger.kernel.org, mike.travis@hpe.com, dimitri.sivanich@hpe.com
> To: linux-tip-commits@vger.kernel.org
> CC: dimitri.sivanich@hpe.com, mike.travis@hpe.com,
> linux-kernel@vger.kernel.org, mingo@kernel.org, hpa@zytor.com,
> tglx@linutronix.de, andrew.banman@hpe.com, russ.anderson@hpe.com,
> travis@sgi.com
>
> Commit-ID: bd47a85acd727e27b7283daff557865ad04c59f6
Ok, that commit showed up in 4.16:
$ git describe --contains bd47a85acd727e27b7283daff557865ad04c59f6
v4.16~2^2
But the commit this fixes:
> Gitweb: https://git.kernel.org/tip/bd47a85acd727e27b7283daff557865ad04c59f6
> Author: mike.travis@hpe.com <mike.travis@hpe.com>
> AuthorDate: Wed, 28 Mar 2018 12:40:11 -0500
> Committer: Thomas Gleixner <tglx@linutronix.de>
> CommitDate: Wed, 28 Mar 2018 20:19:45 +0200
>
> x86/platform/UV: Fix critical UV MMR address error
>
> A critical error was found testing the fixed UV4 HUB in that an MMR address
> was found to be incorrect. This causes the virtual address space for
> accessing the MMIOH1 region to be allocated with the incorrect size.
>
> Fixes: 673aa20c55a1 ("x86/platform/UV: Update uv_mmrs.h to prepare for UV4A
> fixes")
Is in 4.16-rc1:
$ git describe --contains 673aa20c55a1
v4.16-rc1~174^2~9
And is not backported to any other stable tree that I see:
$ fr 673aa20c55a1
4.16
$ alias fr
alias fr='~/linux/scripts/fix_in_what_release'
So what exactly am I supposed to do with this commit? What do you want
to see done with it?
totally confused,
greg k-h
next prev parent reply other threads:[~2018-04-09 20:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 17:40 [PATCH 0/1] x86/platform/UV: UV Fix patches for Intel processors mike.travis
2018-03-28 17:40 ` [PATCH 1/1] x86/platform/UV: Fix critical UV MMR address error mike.travis
2018-03-28 18:17 ` Thomas Gleixner
2018-03-28 18:29 ` Mike Travis
2018-03-28 18:25 ` [tip:x86/urgent] " tip-bot for mike.travis@hpe.com
2018-04-09 17:57 ` Fwd: " Mike Travis
2018-04-09 20:03 ` Greg KH [this message]
2018-04-09 22:48 ` Mike Travis
2018-04-10 5:26 ` Greg KH
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=20180409200333.GA1811@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=mike.travis@hpe.com \
--cc=stable@vger.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.