All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shivappa Vikas <vikas.shivappa@linux.intel.com>
To: Shivappa Vikas <vikas.shivappa@linux.intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Shivappa Vikas <vikas.shivappa@intel.com>,
	x86@kernel.org, LKML <linux-kernel@vger.kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@kernel.org>,
	ravi.v.shankar@intel.com, Tony Luck <tony.luck@intel.com>,
	fenghua.yu@intel.com, Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 0/8 V4] x86/intel_rdt: Intel Memory bandwidth allocation
Date: Fri, 14 Apr 2017 17:20:04 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.10.1704141717240.3411@vshiva-Udesk> (raw)
In-Reply-To: <alpine.DEB.2.10.1704141051161.3411@vshiva-Udesk>



On Fri, 14 Apr 2017, Shivappa Vikas wrote:

>
>
> On Fri, 14 Apr 2017, Thomas Gleixner wrote:
>> 
>> Please do the following:
>> 
>> 1) Verify that it still works as I have no hardware to test it. Once you
>>    confirmed, it's going to show up in -next. So please do that ASAP,
>>    i.e. yesterday.
>> 
>> 2) Go through the patches one by one and compare it to your own to figure
>>    out yourself how it should be done. Next time, I'm simply going to drop
>>    such crap whether that makes it miss the merge window or not.
>
> Ok doing the testing now. Will update soon.
> Also will followup with the type of changes and implement the same convention 
> in the future patches.

All your changes are tested to be fine when used on the hardware and function 
as before. Although we did discover some minor parsing issues (which existed in 
the version i sent originally..) and will send a fix on top of 
current tip/x86/cpu soon.

Thanks,
Vikas

>
> Thanks,
> Vikas
>
>> 
>> Yours grumpy
>>
>>      tglx
>> 
>

      reply	other threads:[~2017-04-15  0:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-08  0:33 [PATCH 0/8 V4] x86/intel_rdt: Intel Memory bandwidth allocation Vikas Shivappa
2017-04-08  0:33 ` [PATCH 1/8] Documentation, x86: " Vikas Shivappa
2017-04-14 14:17   ` [tip:x86/cpu] " tip-bot for Vikas Shivappa
2017-04-08  0:33 ` [PATCH 2/8] x86/intel_rdt/mba: Generalize the naming to get ready for MBA Vikas Shivappa
2017-04-14 14:17   ` [tip:x86/cpu] x86/intel_rdt: Cleanup namespace to support multiple resource types tip-bot for Vikas Shivappa
2017-04-08  0:33 ` [PATCH 3/8] x86/intel_rdt/mba: Memory b/w allocation feature detect Vikas Shivappa
2017-04-14 14:19   ` [tip:x86/cpu] x86/intel_rdt/mba: Memory bandwith " tip-bot for Vikas Shivappa
2017-04-08  0:33 ` [PATCH 4/8] x86/intel_rct/mba: Add MBA structures and initialize MBA Vikas Shivappa
2017-04-14 14:19   ` [tip:x86/cpu] x86/intel_rdt/mba: Add primary support for Memory Bandwidth Allocation (MBA) tip-bot for Vikas Shivappa
2017-04-08  0:33 ` [PATCH 5/8] x86/intel_rdt: Prep to add info files for MBA Vikas Shivappa
2017-04-14 14:20   ` [tip:x86/cpu] x86/intel_rdt: Make information files resource specific tip-bot for Vikas Shivappa
2017-04-08  0:33 ` [PATCH 6/8] x86/intel_rdt/mba: Add info directory files for MBA Vikas Shivappa
2017-04-14 14:20   ` [tip:x86/cpu] x86/intel_rdt/mba: Add info directory files for Memory Bandwidth Allocation tip-bot for Vikas Shivappa
2017-04-08  0:33 ` [PATCH 7/8] x86/intel_rdt: Prep to add schemata file for MBA Vikas Shivappa
2017-04-14 14:21   ` [tip:x86/cpu] x86/intel_rdt: Make schemata file parsers resource specific tip-bot for Vikas Shivappa
2017-04-08  0:33 ` [PATCH 8/8] x86/intel_rdt/mba: Add schemata file support for MBA Vikas Shivappa
2017-04-14 14:21   ` [tip:x86/cpu] " tip-bot for Vikas Shivappa
2017-04-12 22:59 ` [PATCH 0/8 V4] x86/intel_rdt: Intel Memory bandwidth allocation Shivappa Vikas
2017-04-12 23:33   ` Thomas Gleixner
2017-04-14 14:29     ` Thomas Gleixner
2017-04-14 17:52       ` Shivappa Vikas
2017-04-15  0:20         ` Shivappa Vikas [this message]

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=alpine.DEB.2.10.1704141717240.3411@vshiva-Udesk \
    --to=vikas.shivappa@linux.intel.com \
    --cc=fenghua.yu@intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=ravi.v.shankar@intel.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=vikas.shivappa@intel.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.