From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: intel.com, ip: 134.134.136.31, mailfrom: hao.a.wu@intel.com) Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by groups.io with SMTP; Wed, 03 Jul 2019 00:52:50 -0700 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Jul 2019 00:52:49 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.63,446,1557212400"; d="scan'208";a="184680452" Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205]) by fmsmga001.fm.intel.com with ESMTP; 03 Jul 2019 00:52:49 -0700 Received: from fmsmsx116.amr.corp.intel.com (10.18.116.20) by fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS) id 14.3.439.0; Wed, 3 Jul 2019 00:52:49 -0700 Received: from shsmsx105.ccr.corp.intel.com (10.239.4.158) by fmsmsx116.amr.corp.intel.com (10.18.116.20) with Microsoft SMTP Server (TLS) id 14.3.439.0; Wed, 3 Jul 2019 00:52:49 -0700 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.110]) by SHSMSX105.ccr.corp.intel.com ([169.254.11.232]) with mapi id 14.03.0439.000; Wed, 3 Jul 2019 15:52:47 +0800 From: "Wu, Hao A" To: Leif Lindholm CC: "devel@edk2.groups.io" Subject: Re: [RFC PATCH 2/3] Maintainers.txt: add wildcard path association for Arm/AArch64 Thread-Topic: [RFC PATCH 2/3] Maintainers.txt: add wildcard path association for Arm/AArch64 Thread-Index: AQHVIu7GtJEv32vFO0iI/51qw0Dxzaa4nYow Date: Wed, 3 Jul 2019 07:52:46 +0000 Message-ID: References: <20190614202121.18952-3-leif.lindholm@linaro.org> In-Reply-To: <20190614202121.18952-3-leif.lindholm@linaro.org> Accept-Language: zh-CN, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Return-Path: hao.a.wu@intel.com Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable > -----Original Message----- > From: Leif Lindholm [mailto:leif.lindholm@linaro.org] > Sent: Saturday, June 15, 2019 4:21 AM > To: devel@edk2.groups.io > Cc: Feng, Bob C; Gao, Liming; Andrew Fish; Laszlo Ersek; Kinney, Michael = D; > Wu, Hao A > Subject: [RFC PATCH 2/3] Maintainers.txt: add wildcard path association f= or > Arm/AArch64 >=20 > Add Ard and Leif as responsible for any path matching > F: */Arm/ > F: */AArch64/ >=20 > Signed-off-by: Leif Lindholm > --- > Maintainers.txt | 8 ++++++++ > 1 file changed, 8 insertions(+) >=20 > diff --git a/Maintainers.txt b/Maintainers.txt > index cd32f9b00170..e415f51468d5 100644 > --- a/Maintainers.txt > +++ b/Maintainers.txt > @@ -82,6 +82,14 @@ EDK II Releases: > W: https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release- > Planning > M: Liming Gao >=20 > +EDK II Architectures: > +--------------------- > +ARM, AARCH64 > +F: */AArch64/ > +F: */Arm/ Hello Leif, I want to confirm a couple of usage model for the wildcard character. Maybe they have been explained with your response to Laszlo's comments, but I just want to double-confirm with my using cases. 1. Matching multiple levels of directories For the below 2 folders: MdeModulePkg/Bus/Ufs/ MdeModulePkg/Bus/Pci/UfsPciHcDxe/ I can use: MdeModulePkg/*Ufs*/ to match them all, right? 2. Matching header files (usually within the Include/ directory) In some cases, a feature may include some drivers + some include header files. So for the below case: MdeModulePkg/Include/Library/HiiLib.h MdeModulePkg/Include/Guid/HiiResourceSampleHii.h MdeModulePkg/Universal/HiiDatabaseDxe/ MdeModulePkg/Universal/HiiResourcesSampleDxe/ MdeModulePkg/Library/UefiHiiLib/ Should I use: MdeModulePkg/*Hii*/ to match the drivers(libraries) and the headers all or should I use: MdeModulePkg/*Hii*/ MdeModulePkg/Include/*Hii*.h instead? Best Regards, Hao Wu > +M: Leif Lindholm > +M: Ard Biesheuvel > + > EDK II Packages: > ---------------- > ArmPkg > -- > 2.11.0