All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Mike Travis <travis@sgi.com>
Cc: Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Dimitri Sivanich <sivanich@sgi.com>, Russ Anderson <rja@sgi.com>,
	John Estabrook <estabrook@sgi.com>,
	Andrew Banman <abanman@sgi.com>, Nathan Zimmer <nzimmer@sgi.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH 0/4] x86/platform/UV: SGI UV4 Kernel Fixes
Date: Wed, 27 Jul 2016 11:02:39 -0700	[thread overview]
Message-ID: <20160727180239.GD8437@kroah.com> (raw)
In-Reply-To: <20160727173331.230927085@asylum.americas.sgi.com>

On Wed, Jul 27, 2016 at 12:33:31PM -0500, Mike Travis wrote:
> 
> A few problems have been found as the UV4 BIOS and hardware is being
> developed and tested.  These patches fix those problems.
> 
> Patch1: uv4_fix_gam_range_lookup_table
>   - Fixes a problem with building the UV4 GAM range table
> 
> Patch2: uv4_fix_bios_init_error
>   - Fixes a panic associated with the UV4 system table
> 
> Patch3: uv4_remove_uvsystab_pxm
>   - Fixes a problem with incorrect data from UV4 BIOS
> 
> Patch4: uv4_disable_is_uv_system
>   - Fixes a panic using the RHEL7 kdump kernel


<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read Documentation/stable_kernel_rules.txt
for how to do this properly.

</formletter>

  parent reply	other threads:[~2016-07-27 18:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-27 17:33 [PATCH 0/4] x86/platform/UV: SGI UV4 Kernel Fixes Mike Travis
2016-07-27 17:33 ` [PATCH 1/4] x86/platform/UV: Fix problem with UV4 Socket IDs not being contiguous Mike Travis
2016-07-27 17:33 ` [PATCH 2/4] x86/platform/UV: Fix problem with bad UV4 EFI System Table causing panic Mike Travis
2016-07-29 11:17   ` Thomas Gleixner
2016-07-29 16:31     ` Mike Travis
2016-07-27 17:33 ` [PATCH 3/4] x86/platform/UV: Fix problem with UV4 BIOS providing incorrect PXM values Mike Travis
2016-07-27 17:33 ` [PATCH 4/4] x86/platform/UV: Fix kernel panic running RHEL kdump kernel on UV Mike Travis
2016-07-27 18:02 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-08-01 18:40 [PATCH 0/4] x86/platform/UV: SGI UV4 Kernel Fixes Mike Travis

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=20160727180239.GD8437@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=abanman@sgi.com \
    --cc=akpm@linux-foundation.org \
    --cc=estabrook@sgi.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=nzimmer@sgi.com \
    --cc=rja@sgi.com \
    --cc=sivanich@sgi.com \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=travis@sgi.com \
    --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.