Bug 607696 - x86, uv: uv_global_gru_mmr_address() macro fix
x86, uv: uv_global_gru_mmr_address() macro fix
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel (Show other bugs)
All Linux
low Severity urgent
: rc
: 6.0
Assigned To: George Beshers
Red Hat Kernel QE team
: OtherQA
Depends On:
Blocks: 555548
  Show dependency treegraph
Reported: 2010-06-24 11:26 EDT by George Beshers
Modified: 2010-11-15 09:24 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-15 09:24:37 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
trivial backport (1.12 KB, patch)
2010-06-24 18:17 EDT, George Beshers
no flags Details | Diff

  None (edit)
Description George Beshers 2010-06-24 11:26:23 EDT
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 11:53:06 EDT
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 18:17:47 EDT
Created attachment 426712 [details]
trivial backport
Comment 4 George Beshers 2010-06-24 18:24:49 EDT
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 12:13:47 EDT
Patch(es) available on kernel-2.6.32-42.el6
Comment 9 George Beshers 2010-07-22 10:27:44 EDT
Verified to be in 2.6.32-50.

Comment 10 releng-rhel@redhat.com 2010-11-15 09:24:37 EST
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.

Note You need to log in before you can comment on or make changes to this bug.