Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1755771AbdDOATc (ORCPT <rfc822;w@1wt.eu>);
        Fri, 14 Apr 2017 20:19:32 -0400
Received: from mga07.intel.com ([134.134.136.100]:45130 "EHLO mga07.intel.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1755406AbdDOAT3 (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 14 Apr 2017 20:19:29 -0400
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.37,201,1488873600"; 
   d="scan'208";a="87660420"
Date: Fri, 14 Apr 2017 17:20:04 -0700 (PDT)
From: Shivappa Vikas <vikas.shivappa@linux.intel.com>
X-X-Sender: vikas@vshiva-Udesk
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
In-Reply-To: <alpine.DEB.2.10.1704141051161.3411@vshiva-Udesk>
Message-ID: <alpine.DEB.2.10.1704141717240.3411@vshiva-Udesk>
References: <1491611637-20417-1-git-send-email-vikas.shivappa@linux.intel.com> <alpine.DEB.2.10.1704121558160.31192@vshiva-Udesk> <alpine.DEB.2.20.1704130132230.2548@nanos> <alpine.DEB.2.20.1704141611290.2327@nanos>
 <alpine.DEB.2.10.1704141051161.3411@vshiva-Udesk>
User-Agent: Alpine 2.10 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1015
Lines: 40



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
>> 
>