[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] maintainers: add regex matching for xsm


  • To: Julien Grall <julien@xxxxxxx>, Jan Beulich <jbeulich@xxxxxxxx>
  • From: "Daniel P. Smith" <dpsmith@xxxxxxxxxxxxxxxxxxxx>
  • Date: Mon, 22 May 2023 15:35:00 -0400
  • Arc-authentication-results: i=1; mx.zohomail.com; dkim=pass header.i=apertussolutions.com; spf=pass smtp.mailfrom=dpsmith@xxxxxxxxxxxxxxxxxxxx; dmarc=pass header.from=<dpsmith@xxxxxxxxxxxxxxxxxxxx>
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1684784103; h=Content-Type:Content-Transfer-Encoding:Cc:Date:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:To; bh=LHtXxuQLJ2qd3EJg+oiO4vWWwXemlyBNcmjyBgrOsEI=; b=V4HQghP2xS1Oh4wqTTWJT3hEk5bSvOeRVtvn/SjmKON3XVexFDS6rOpI79iFC0++cCQNcKosnya7dFDMoBGSEcAb4WyD0DuDdPT2fkK2QVjS8sb33pkMq8/t9ZCvk+8gupXtEUWJf5eE/CtPqCg2T/eUF2O/d1IuCALg2xNa1Ck=
  • Arc-seal: i=1; a=rsa-sha256; t=1684784103; cv=none; d=zohomail.com; s=zohoarc; b=NZD3h/6MSHBDgza8k9G0UMwscqDDu8wBb/sEltpJfAmGWHwBYjPbXcZTW/D/EgV1QD90XEZa25nNA4iEjlhdrBiZqSf2gO8uIayZyEAwlnrY9hAUJMT7g/3u8Th6c44QftbzTwPVGt5eUGQhLpNwmPOm6vLW8yALTxnnlLOqFyQ=
  • Cc: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, George Dunlap <george.dunlap@xxxxxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Wei Liu <wl@xxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 22 May 2023 19:35:22 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 5/22/23 06:27, Julien Grall wrote:
Hi,

On 22/05/2023 10:23, Jan Beulich wrote:
On 19.05.2023 13:48, Daniel P. Smith wrote:
XSM is a subsystem where it is equally important of how and where its hooks are
called as is the implementation of the hooks. The people best suited for
evaluating the how and where are the XSM maintainers and reviewers. This
creates a challenge as the hooks are used throughout the hypervisor for which the XSM maintainers and reviewers are not, and should not be, a reviewer for each of these subsystems in the MAINTAINERS file. Though the MAINTAINERS file does support the use of regex matches, 'K' identifier, that are applied to both the commit message and the commit delta. Adding the 'K' identifier will declare that any patch relating to XSM require the input from the XSM maintainers and reviewers. For those that use the get_maintianers script, the 'K' identifier
will automatically add the XSM maintainers and reviewers.

With, aiui, a fair chance of false positives when e.g. XSM hook invocations
are only in patch context. Much like ...

Any one not using
get_maintainers, it will be their responsibility to ensure that if their work touches and XSM hook, to ensure the XSM maintainers and reviewers are copied.

... manual intervention is needed in the case of not using the script, I
think people should also be at least asked to see about avoiding stray Cc-s in that case.

I don't particularly like this suggestion because the sender may mistakenly believe this is a "stray CC".

Personally, I would prefer to be in CC more often than less often. I think we should give the choice to Daniel to decide whether he is happy to be in CC potentially more often.

If it is becoming too much then we can decide to adjust the script.

Unless of course I'm misreading get_maintainers.pl (my Perl
isn't really great) or the script would be adjusted to only look at added/
removed lines (albeit even that would leave a certain risk of false
positives).

--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -674,6 +674,8 @@ F:    tools/flask/
  F:    xen/include/xsm/
  F:    xen/xsm/
  F:    docs/misc/xsm-flask.txt
+K:  xsm_.*
+K:  \b(xsm|XSM)\b

Aside the NIT from Jan, this change is only affecting the number of e-mails the XSM maintainers will receive. So:

Acked-by: Julien Grall <jgrall@xxxxxxxxxx>

Apologies, I missed your ack before I sent v2 out.

v/r,
dps



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.