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

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


  • To: "Daniel P. Smith" <dpsmith@xxxxxxxxxxxxxxxxxxxx>
  • From: Jan Beulich <jbeulich@xxxxxxxx>
  • Date: Mon, 22 May 2023 11:23:22 +0200
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=suse.com; dmarc=pass action=none header.from=suse.com; dkim=pass header.d=suse.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=K0RQAM99YhPXWe6dTITvTbitjWSiSjqtTMVsef9V3/k=; b=Q/8gKIh6Qn59Rl1edNtbPKzfIg73xr6kMJ5J7vNWcr7pn+HC5zTxJ9i4lanbVObd4ar14KlT0QcqZMLScNFpDqzB+mCQowC2bjC+RPeB/D483OGRkwNZgkm2eeQOsWoNvU8JNsBkJp3stcUwQ+43bRUbjktm9a1xhncMAp+eXnFZRD5QMN199pqqp3PcyK/awPW0EVZaaZSXkhIRAroIXnXZcHYev6e5w+NunRrBxHHP5iqJFsI/1fwj3fcTsZ/gAsqv/amvHz5uSsVPFiSyKYtiQyDkHXY5QBZVAGQVUv9t+YrBHCFxtcuC1kHL1iY9OlbTF8h+x4pz9PNNAi82TA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=XxioQ/An6iRYnTi0j60hxS12Xgko55OWSknr2PlVJhk0/74VS2pGeKg2+HOn1Gc72C9TG3k9nXI4VR+U3tNyjy2oF/3WNbkvwO3IOzK+edgXQLbJlpEC96d7HxfaRkAaVJPxoTn0vSRp8QlvVLyMiKuvuDghjTEmFwair9ydwKuym2PWVNPnkBSg3/3Ctwfk8McJttN/1eqQ9l2mB0O3HQcmGd+yNyU28sSe8iH273OW0zE2G/0AfwYTnAZND9PC35M8rI4WisGS40c7MT7uz3PDNZp6VG7HT9lah73xQTAeupk184iYnpJ5FyNVuIigYapFkCCtg58xBhh+Pxnb4w==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=suse.com;
  • Cc: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, George Dunlap <george.dunlap@xxxxxxxxxx>, Julien Grall <julien@xxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Wei Liu <wl@xxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 22 May 2023 09:23:41 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

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

Nit: Please make padding match that of adjacent lines.

Jan



 


Rackspace

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