public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: tip-bot for Borislav Petkov <borislav.petkov@amd.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hagen@jauu.net, hpa@zytor.com,
	mingo@redhat.com, farnold@amd64.org, tglx@linutronix.de,
	hpa@linux.intel.com, borislav.petkov@amd.com
Subject: [tip:x86/cpu] x86, AMD, cacheinfo: Fix fallout caused by max3 conversion
Date: Mon, 16 May 2011 21:22:03 GMT	[thread overview]
Message-ID: <tip-50e7534427283afd997d58481778c07bea79eb63@git.kernel.org> (raw)
In-Reply-To: <1305553188-21061-2-git-send-email-bp@amd64.org>

Commit-ID:  50e7534427283afd997d58481778c07bea79eb63
Gitweb:     http://git.kernel.org/tip/50e7534427283afd997d58481778c07bea79eb63
Author:     Borislav Petkov <borislav.petkov@amd.com>
AuthorDate: Mon, 16 May 2011 15:39:46 +0200
Committer:  H. Peter Anvin <hpa@linux.intel.com>
CommitDate: Mon, 16 May 2011 11:24:23 -0700

x86, AMD, cacheinfo: Fix fallout caused by max3 conversion

732eacc0542d0aa48797f675888b85d6065af837 converted code around the
kernel using nested max() macros to use the new max3 macro but forgot to
remove the old line in intel_cacheinfo.c. Fix it.

Cc: Hagen Paul Pfeifer <hagen@jauu.net>
Cc: Frank Arnold <farnold@amd64.org>
Signed-off-by: Borislav Petkov <borislav.petkov@amd.com>
Link: http://lkml.kernel.org/r/1305553188-21061-2-git-send-email-bp@amd64.org
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
---
 arch/x86/kernel/cpu/intel_cacheinfo.c |    1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/arch/x86/kernel/cpu/intel_cacheinfo.c b/arch/x86/kernel/cpu/intel_cacheinfo.c
index 1ce1af2..31590a0 100644
--- a/arch/x86/kernel/cpu/intel_cacheinfo.c
+++ b/arch/x86/kernel/cpu/intel_cacheinfo.c
@@ -327,7 +327,6 @@ static void __cpuinit amd_calc_l3_indices(struct amd_l3_cache *l3)
 	l3->subcaches[2] = sc2 = !(val & BIT(8))  + !(val & BIT(9));
 	l3->subcaches[3] = sc3 = !(val & BIT(12)) + !(val & BIT(13));
 
-	l3->indices = (max(max(max(sc0, sc1), sc2), sc3) << 10) - 1;
 	l3->indices = (max(max3(sc0, sc1, sc2), sc3) << 10) - 1;
 }
 

  parent reply	other threads:[~2011-05-16 21:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-16 13:39 [PATCH 0/3] x86, AMD, cacheinfo: L3 CID fixes Borislav Petkov
2011-05-16 13:39 ` [PATCH 1/3] x86, AMD, cacheinfo: Fix fallout caused by max3 conversion Borislav Petkov
2011-05-16 17:31   ` Greg KH
2011-05-16 17:38     ` Borislav Petkov
2011-05-16 17:42       ` H. Peter Anvin
2011-05-16 17:47         ` Borislav Petkov
2011-05-16 18:00           ` H. Peter Anvin
2011-05-16 18:19             ` Borislav Petkov
2011-05-16 18:45   ` Hagen Paul Pfeifer
2011-05-16 21:22   ` tip-bot for Borislav Petkov [this message]
2011-05-16 13:39 ` [PATCH 2/3] x86, AMD, cacheinfo: Fix L3 cache index disable checks Borislav Petkov
2011-05-16 21:22   ` [tip:x86/cpu] " tip-bot for Frank Arnold
2011-05-16 13:39 ` [PATCH 3/3] Documentation, ABI: Update L3 cache index disable text Borislav Petkov
2011-05-16 17:30   ` Greg KH
2011-05-16 21:22   ` [tip:x86/cpu] " tip-bot for Borislav Petkov

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=tip-50e7534427283afd997d58481778c07bea79eb63@git.kernel.org \
    --to=borislav.petkov@amd.com \
    --cc=farnold@amd64.org \
    --cc=hagen@jauu.net \
    --cc=hpa@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    /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