From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id AC4BEA0093; Tue, 10 May 2022 14:32:04 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9F15C4282C; Tue, 10 May 2022 14:32:04 +0200 (CEST) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by mails.dpdk.org (Postfix) with ESMTP id 242034069D for ; Tue, 10 May 2022 14:32:03 +0200 (CEST) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 77B795C0139; Tue, 10 May 2022 08:32:01 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Tue, 10 May 2022 08:32:01 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm1; t=1652185921; x= 1652272321; bh=+nEBYfK3iVoDkLKW3Bj8PAHH/KoGFv+RrnhRWX9WsGU=; b=c hwZ4gXnKt2FMYVxWvRUChi9QOXOh6yqhNd0qpSAes0dWc++49Gb4Gsf2PsdR/HCh Vdh0nFTdqRUeEo5GzDUKj0TF5nmh27Vi5xuOWe/V3jCZcKOYh34tR7Z2QZH4feNt 2j6b3rHHGcvNt0XCHKVhN4oP0qW4kLm2MycSRq5ed5/KEpYZDinMuwIW0MrZjm1q wpGnbQzdImjyqgJ22gWuj+pBMUAJ9Bg2r5C9j7C+slQs5yfd6nStLVHjLEok2d51 LkwH7jtNXCyUhVjZFVDzetM1IhRZpCKTWkve8rIcVoBSNO7Fe/Cy49buJ5WFFXZP 91Ru/ZJ5zN4SLklMGIezg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; t=1652185921; x=1652272321; bh=+nEBYfK3iVoDk LKW3Bj8PAHH/KoGFv+RrnhRWX9WsGU=; b=dhP21qoNKSamgXbcowRFNhztsZqb6 QeAdKZHjPgl0PEMH8g92urmKwo7r1ZyKFSCnvZQ/drYmmKnVwazhHzOpWOiPCRjb Kr11YV+aqN64u4N3qu0ZuNW02soiXDrHgMr6Oyu7X9jJERpzclR6hdmvyA21wZCE KXfM27NhHdGs+WE2zZ1PkNmakXyyKEhyTEff1EhPKAdnR9kabeZkfkIOF7+F8C1r iSTD8MbO6nTZH2/Dw4eSFDnKIXA1RG/HbFZlD1Q5R4JdDvedFGxNK4Pb/fhotQfd TX49kqBKrBY87WoWM6OCHlDfxBGVNDigrnQ4y3w7mtCeSAewS3juHMMag== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrgedugdegkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvfevufffkfgjfhgggfgtsehtqhertddttdejnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepffdtuefhhedvkeelleevffdvlefhleehvdegtddvvdduueeivedt gfejvddugeefnecuffhomhgrihhnpeguphgukhdrohhrghenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhn rdhnvght X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 10 May 2022 08:31:59 -0400 (EDT) From: Thomas Monjalon To: =?utf-8?B?U3RhbmlzxYJhdw==?= Kardach Cc: David Marchand , dev , Frank Zhao , Sam Grove , Marcin Wojtas , upstream@semihalf.com, Stephen Hemminger Subject: Re: [PATCH 00/11] Introduce support for RISC-V architecture Date: Tue, 10 May 2022 14:31:57 +0200 Message-ID: <23271621.ouqheUzb2q@thomas> In-Reply-To: References: <20220505173003.3242618-1-kda@semihalf.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 10/05/2022 13:21, Stanis=C5=82aw Kardach: > On Mon, May 9, 2022 at 4:31 PM David Marchand > wrote: > > >> About the new "Sponsored-by" tag, it should not raise warnings in the > > >> CI if we agree on its addition. > > > > > > I'll modify it in V2 to be in form of: > > > Sponsored by: StarFive Technology > > > ... > > > Signed-off-by: ... > > > This was suggested by Stephen Hemminger as having a precedent in Linux > > kernel. Interestingly enough first use of this tag in kernel source was > > this year in January. > > > > I don't have an opinion on the spelling. > > > > At the moment, the checks raise a warning: > > http://mails.dpdk.org/archives/test-report/2022-May/278580.html > > > > My point is that for this new tag, either checkpatch.pl in kernel > > handles it (which I don't think it is the case) or we need to disable > > the signature check in checkpatch.pl and something is added in dpdk > > checkpatches.sh to accept all known tags. > > > BAD_SIGN_OFF handles more than just tag names (in total there's 10 cases > checked). I'm not sure replicating this to checkpatches.sh is worth the > maintenance. > Alternatively I could ignore BAD_SIGN_OFF on initial checkpatch.pl run and > then run it again with just the BAD_SIGN_OFF type and filter out the resu= lt. > In that case, what would be the acceptable content of Sponsored-by tag? F= or > line: > Sponsored-by: StarFive Technology > Current checkpatch.pl generates (used --terse for brevity): > 0001-eal-add-initial-support-for-RISC-V-architecture.patch:55: > WARNING:BAD_SIGN_OFF: Non-standard signature: Sponsored-by: > 0001-eal-add-initial-support-for-RISC-V-architecture.patch:55: > ERROR:BAD_SIGN_OFF: Unrecognized email address: 'StarFive Technology' >=20 > Using "Sponsored by:" does not trigger checks above (still feels like a > hack). Agree it is a hack, and not having the hyphen breaks my Vim colouring :) We can ignore this checkpatch warning, that's fine.