From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
linux-kselftest@vger.kernel.org, Shuah Khan <shuah@kernel.org>,
Maciej Wieczor-Retman <maciej.wieczor-retman@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>,
Babu Moger <babu.moger@amd.com>,
LKML <linux-kernel@vger.kernel.org>,
Shaopeng Tan <tan.shaopeng@jp.fujitsu.com>
Subject: Re: [PATCH 1/7] selftests/resctrl: Ensure the benchmark commands fits to its array
Date: Wed, 16 Aug 2023 09:32:22 +0300 (EEST) [thread overview]
Message-ID: <ff136876-449-2d6a-b4dd-13ece5f3e12@linux.intel.com> (raw)
In-Reply-To: <a64114de-0a95-4ed8-aa06-b30a948fee6c@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1899 bytes --]
On Tue, 15 Aug 2023, Reinette Chatre wrote:
> On 8/15/2023 2:10 AM, Ilpo Järvinen wrote:
> >> ps. Unless you have an updated email address that works, could you please
> >> remove Sai's email from future submissions?
> >
> > It's auto-added by git send-email machinery. I guess I can try to make
> > an exception to my usual workflow by sending only to manually specified To
> > addresses (if I remember). Perhaps one day I'll write a tool to filter out
> > the addresses from git send-email generated ones but as is I don't have
> > one.
> >
>
> Which git send-email machinery are you referring to? If I understand correctly
> it does not automatically pick addresses but you can provide custom commands to
> it that can do it.
Ah sorry, it is actually scripts/get_maintainer.pl automation I use with
git send-email to figure out where to send the patches besides the --to &
--cc entries I provided. For this patch, get_maintainer.pl returns this
list:
Fenghua Yu <fenghua.yu@intel.com> (supporter:RDT - RESOURCE ALLOCATION,blamed_fixes:1/1=100%)
Reinette Chatre <reinette.chatre@intel.com> (supporter:RDT - RESOURCE ALLOCATION)
Shuah Khan <shuah@kernel.org> (maintainer:KERNEL SELFTEST FRAMEWORK,blamed_fixes:1/1=100%)
Babu Moger <babu.moger@amd.com> (blamed_fixes:1/1=100%)
Sai Praneeth Prakhya <sai.praneeth.prakhya@intel.com> (blamed_fixes:1/1=100%)
linux-kernel@vger.kernel.org (open list:RDT - RESOURCE ALLOCATION)
linux-kselftest@vger.kernel.org (open list:KERNEL SELFTEST FRAMEWORK)
...which includes Sai's address (not much I can do about that, it's
immutably crafted into git history that those lines were once touched by
Sai). I've thought of writing yet another wrapper to filter out known
failing addresses but until that's done, either I need to (remember to)
manually send the series w/o get_maintainer.pl automation or accept a few
failures here and there.
--
i.
next prev parent reply other threads:[~2023-08-16 6:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 9:16 [PATCH 0/7] selftests/resctrl: Rework benchmark command handling Ilpo Järvinen
2023-08-08 9:16 ` [PATCH 1/7] selftests/resctrl: Ensure the benchmark commands fits to its array Ilpo Järvinen
2023-08-14 17:48 ` Reinette Chatre
2023-08-15 9:10 ` Ilpo Järvinen
2023-08-15 15:47 ` Reinette Chatre
2023-08-16 6:32 ` Ilpo Järvinen [this message]
2023-08-16 21:46 ` Reinette Chatre
2023-08-08 9:16 ` [PATCH 2/7] selftests/resctrl: Correct benchmark command help Ilpo Järvinen
2023-08-14 17:49 ` Reinette Chatre
2023-08-15 9:11 ` Ilpo Järvinen
2023-08-08 9:16 ` [PATCH 3/7] selftests/resctrl: Remove bw_report and bm_type from main() Ilpo Järvinen
2023-08-14 17:49 ` Reinette Chatre
2023-08-08 9:16 ` [PATCH 4/7] selftests/resctrl: Simplify span lifetime Ilpo Järvinen
2023-08-14 17:49 ` Reinette Chatre
2023-08-08 9:16 ` [PATCH 5/7] selftests/resctrl: Use pointers to build benchmark cmd and make it const Ilpo Järvinen
2023-08-14 17:50 ` Reinette Chatre
2023-08-15 9:42 ` Ilpo Järvinen
2023-08-15 15:48 ` Reinette Chatre
2023-08-16 7:13 ` Ilpo Järvinen
2023-08-16 21:52 ` Reinette Chatre
2023-08-17 8:32 ` Ilpo Järvinen
2023-08-17 15:45 ` Reinette Chatre
2023-08-18 7:25 ` Ilpo Järvinen
2023-08-08 9:16 ` [PATCH 6/7] selftests/resctrl: remove ben_count variable Ilpo Järvinen
2023-08-14 17:51 ` Reinette Chatre
2023-08-08 9:16 ` [PATCH 7/7] selftests/resctrl: Cleanup benchmark argument parsing Ilpo Järvinen
2023-08-14 17:56 ` 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=ff136876-449-2d6a-b4dd-13ece5f3e12@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=babu.moger@amd.com \
--cc=fenghua.yu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maciej.wieczor-retman@intel.com \
--cc=reinette.chatre@intel.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tan.shaopeng@jp.fujitsu.com \
/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