lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ff136876-449-2d6a-b4dd-13ece5f3e12@linux.intel.com>
Date:   Wed, 16 Aug 2023 09:32:22 +0300 (EEST)
From:   Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
To:     Reinette Chatre <reinette.chatre@...el.com>
cc:     Shuah Khan <skhan@...uxfoundation.org>,
        linux-kselftest@...r.kernel.org, Shuah Khan <shuah@...nel.org>,
        Maciej Wieczor-Retman <maciej.wieczor-retman@...el.com>,
        Fenghua Yu <fenghua.yu@...el.com>,
        Babu Moger <babu.moger@....com>,
        LKML <linux-kernel@...r.kernel.org>,
        Shaopeng Tan <tan.shaopeng@...fujitsu.com>
Subject: Re: [PATCH 1/7] selftests/resctrl: Ensure the benchmark commands
 fits to its array

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@...el.com> (supporter:RDT - RESOURCE ALLOCATION,blamed_fixes:1/1=100%)
Reinette Chatre <reinette.chatre@...el.com> (supporter:RDT - RESOURCE ALLOCATION)
Shuah Khan <shuah@...nel.org> (maintainer:KERNEL SELFTEST FRAMEWORK,blamed_fixes:1/1=100%)
Babu Moger <babu.moger@....com> (blamed_fixes:1/1=100%)
Sai Praneeth Prakhya <sai.praneeth.prakhya@...el.com> (blamed_fixes:1/1=100%)
linux-kernel@...r.kernel.org (open list:RDT - RESOURCE ALLOCATION)
linux-kselftest@...r.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.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ