public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Reinette Chatre <reinette.chatre@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: tglx@linutronix.de, fenghua.yu@intel.com, tony.luck@intel.com,
	kuo-lang.tseng@intel.com, ravi.v.shankar@intel.com,
	mingo@redhat.com, babu.moger@amd.com, hpa@zytor.com,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V6 0/4] x86/resctrl: Enable user to view and select thread throttling mode
Date: Wed, 20 May 2020 10:32:02 -0700	[thread overview]
Message-ID: <5c044d17-e42e-1493-28a5-3ecac043c8f1@intel.com> (raw)
In-Reply-To: <20200520071109.GA1457@zn.tnic>

Hi Borislav,

On 5/20/2020 12:11 AM, Borislav Petkov wrote:
> On Tue, May 19, 2020 at 03:13:59PM -0700, Reinette Chatre wrote:
>> I am very sorry. I was hoping that this series could be considered for
>> inclusion into v5.8 and submitted it seven weeks ago because of that.
>> The recent feedback addressed seemed to be the final few small comments
>> needed to be ready for inclusion and I was afraid that waiting long to
>> address this would cause me to miss opportunity to be considered for
>> inclusion since we are already at rc6.
> 
> That's understandable but does it really matter when it goes in? If not
> in 5.8, then 5.9. I.e., there's always a next kernel.
> 
> So why the hurry?
> 

I was told that these enhancements really needed to get into v5.8,
otherwise the OSV intercepts will be much further out. Certainly not of
concern to you and not your problem, I am just answering your question
as an explanation for my goal for inclusion into v5.8.

It seems inappropriate that I have the title of maintainer and not be
able to have patches considered for inclusion during an entire release
cycle. I completely understand that you are under tremendous load and
expect that you have an incredible amount of things demanding your
attention. I was wrong to expect a higher level of visibility of these
patches and I am sorry that I spammed you with this patchset.

Reinette

  reply	other threads:[~2020-05-20 17:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19 21:28 [PATCH V6 0/4] x86/resctrl: Enable user to view and select thread throttling mode Reinette Chatre
2020-05-19 21:28 ` [PATCH V6 1/4] " Reinette Chatre
2020-05-19 21:28 ` [PATCH V6 2/4] x86/resctrl: Enumerate per-thread MBA Reinette Chatre
2020-05-19 21:28 ` [PATCH V6 3/4] x86/resctrl: Enable " Reinette Chatre
2020-05-19 21:28 ` [PATCH V6 4/4] x86/resctrl: Use appropriate API for strings terminated by newline Reinette Chatre
2020-05-19 21:47   ` Andy Shevchenko
2020-05-19 21:35 ` [PATCH V6 0/4] x86/resctrl: Enable user to view and select thread throttling mode Borislav Petkov
2020-05-19 22:13   ` Reinette Chatre
2020-05-20  7:11     ` Borislav Petkov
2020-05-20 17:32       ` Reinette Chatre [this message]
2020-05-20 18:35         ` Borislav Petkov
2020-05-20 20:24           ` Reinette Chatre

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=5c044d17-e42e-1493-28a5-3ecac043c8f1@intel.com \
    --to=reinette.chatre@intel.com \
    --cc=babu.moger@amd.com \
    --cc=bp@alien8.de \
    --cc=fenghua.yu@intel.com \
    --cc=hpa@zytor.com \
    --cc=kuo-lang.tseng@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=ravi.v.shankar@intel.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox