All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <borislav.petkov@amd.com>
Cc: Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
	Frank Arnold <frank.arnold@amd.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [GIT PULL] L3 CID fix for 3.5
Date: Wed, 25 Apr 2012 10:23:58 +0000	[thread overview]
Message-ID: <20120425102357.GC20853@gmail.com> (raw)
In-Reply-To: <20120425093001.GA18882@aftab.osrc.amd.com>


* Borislav Petkov <borislav.petkov@amd.com> wrote:

> Ping?
> 
> Guys, any issues with this that I should know of?

Looks good to me. You marked it v3.5, should I pull it into 
v3.4? Looks small enough to me and we better keep such user 
facing interfaces correct, even if there's no direct regression.

Thanks,

	Ingo

WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <borislav.petkov@amd.com>
Cc: Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
	Frank Arnold <frank.arnold@amd.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [GIT PULL] L3 CID fix for 3.5
Date: Wed, 25 Apr 2012 12:23:58 +0200	[thread overview]
Message-ID: <20120425102357.GC20853@gmail.com> (raw)
In-Reply-To: <20120425093001.GA18882@aftab.osrc.amd.com>


* Borislav Petkov <borislav.petkov@amd.com> wrote:

> Ping?
> 
> Guys, any issues with this that I should know of?

Looks good to me. You marked it v3.5, should I pull it into 
v3.4? Looks small enough to me and we better keep such user 
facing interfaces correct, even if there's no direct regression.

Thanks,

	Ingo

  reply	other threads:[~2012-04-25 10:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-19  7:00 [patch] cpu: remove some dead code in store_cache_disable() Dan Carpenter
2012-04-19  7:00 ` Dan Carpenter
2012-04-19  8:18 ` Srivatsa S. Bhat
2012-04-19  8:30   ` Srivatsa S. Bhat
2012-04-19 11:02   ` Borislav Petkov
2012-04-19 11:02     ` Borislav Petkov
2012-04-19 11:14     ` Srivatsa S. Bhat
2012-04-19 11:26       ` Srivatsa S. Bhat
2012-04-19 11:44     ` Dan Carpenter
2012-04-19 11:44       ` Dan Carpenter
2012-04-19 16:53       ` [GIT PULL] L3 CID fix for 3.5 Borislav Petkov
2012-04-19 16:53         ` Borislav Petkov
2012-04-25  9:30         ` Borislav Petkov
2012-04-25  9:30           ` Borislav Petkov
2012-04-25 10:23           ` Ingo Molnar [this message]
2012-04-25 10:23             ` Ingo Molnar
2012-04-25 10:35             ` Borislav Petkov
2012-04-25 10:35               ` Borislav Petkov
2012-04-25 13:50 ` [tip:x86/urgent] x86, intel_cacheinfo: Fix error return code in amd_set_l3_disable_slot() tip-bot for Srivatsa S. Bhat

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=20120425102357.GC20853@gmail.com \
    --to=mingo@kernel.org \
    --cc=borislav.petkov@amd.com \
    --cc=dan.carpenter@oracle.com \
    --cc=frank.arnold@amd.com \
    --cc=hpa@zytor.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=srivatsa.bhat@linux.vnet.ibm.com \
    --cc=tglx@linutronix.de \
    --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.