Bug 607696

Summary: x86, uv: uv_global_gru_mmr_address() macro fix
Product: Red Hat Enterprise Linux 6 Reporter: George Beshers <gbeshers>
Component: kernelAssignee: George Beshers <gbeshers>
Status: CLOSED CURRENTRELEASE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: urgent Docs Contact:
Priority: low    
Version: 6.0CC: arozansk, caiqian, dwa, martinez, tee
Target Milestone: rcKeywords: OtherQA
Target Release: 6.0   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-15 14:24:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 555548    
Description Flags
trivial backport none

Description George Beshers 2010-06-24 15:26:23 UTC
Description of problem:
  Patch I overlooked.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 2 RHEL Product and Program Management 2010-06-24 15:53:06 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for

Comment 3 George Beshers 2010-06-24 22:17:47 UTC
Created attachment 426712 [details]
trivial backport

Comment 4 George Beshers 2010-06-24 22:24:49 UTC
Asking for an exception into snap7 because it will make
testing of the snap7 kernel much more meaningful.


Comment 6 Aristeu Rozanski 2010-07-01 16:13:47 UTC
Patch(es) available on kernel-2.6.32-42.el6

Comment 9 George Beshers 2010-07-22 14:27:44 UTC
Verified to be in 2.6.32-50.


Comment 10 releng-rhel@redhat.com 2010-11-15 14:24:37 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.