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 29D2FA0032; Wed, 11 May 2022 13:06:21 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0F89C410F2; Wed, 11 May 2022 13:06:21 +0200 (CEST) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mails.dpdk.org (Postfix) with ESMTP id 9179140DDD; Wed, 11 May 2022 13:06:19 +0200 (CEST) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 201065C00C2; Wed, 11 May 2022 07:06:18 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Wed, 11 May 2022 07:06:18 -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=1652267178; x= 1652353578; bh=AtI0xAtAKX3AnExcAFZpqtpcbOFA0Hz1qj5vzHjgeaQ=; b=a s9gkqVWlDG9lMJzNaAlqkO/X/cOhUzO811z/qUrbxLmur8IzLBLgnMiLt0uH7ygd hFNF4NSqodpNZz/m7ro1ivWpzhihwOkbxySXaT691DN6YY/qLQ42/dqwdDqUDLIV IaARMyAZX4VmkplHljEx2GidPoG+fl9xqrNiG9QM9LlsvJxrrNyyQJrabG9aR6+D Wgzi2n5NAQnfUDivkpKahsLazu/wme5Kpdf4csuGxyrEo/lRe9zsQMrL+Ug2A1pB h4mGFExGYSKKr31bWLqjN4TbiXm3khkRq3Jf5MsuzG22KgXQPfJpMa8yIybIHFM5 PzDcLsHEjTJM3sDY5y3pw== 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=1652267178; x=1652353578; bh=AtI0xAtAKX3An ExcAFZpqtpcbOFA0Hz1qj5vzHjgeaQ=; b=K2hJxIkA0tkgii4PvvnKKcjSBMisw MbA2kUWRusDlriEa0Wlza6wSGSpe+WMtyFSfvSlSQYMKjM/myDGyl9vXYhXRbeGk Hwd6C8hCA0J6B5feyUyQUz8MWZDgAqDq4mHElezBuhXhH9SzIgHRlYieFgJLI2MO D4Qotm1H2Pa+8gribaCzhbTpHd869v8hB1sge+BLJDgcGtmqRtIjf9xUx9mOPtcN 2zOAM5OolBg0tRq1OtolbT187i3xZoBmPIgPfGq6ZXWmBrY7qogmH7o2gfs2czZK 02z+Snr/SmM8d69uMh4nw8rb0pmwotJNUQS3VMy7D8+169UZLaJ0Ybzpg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrgeehgdeffecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvfevufffkfgjfhgggfgtsehtqhertddttdejnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepgedttdeljeejgeffkeekkedtjeevtdehvedtkeeivdeuuedviedu vdelveejueejnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 11 May 2022 07:06:16 -0400 (EDT) From: Thomas Monjalon To: Morten =?ISO-8859-1?Q?Br=F8rup?= , =?utf-8?B?U3RhbmlzxYJhdw==?= Kardach Cc: David Marchand , dev , Frank Zhao , Sam Grove , Marcin Wojtas , upstream@semihalf.com, Stephen Hemminger , techboard@dpdk.org Subject: Re: [PATCH 00/11] Introduce support for RISC-V architecture Date: Wed, 11 May 2022 13:06:14 +0200 Message-ID: <7511702.lvqk35OSZv@thomas> In-Reply-To: References: <20220505173003.3242618-1-kda@semihalf.com> <98CBD80474FA8B44BF855DF32C47DC35D8705C@smartserver.smartshare.dk> 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 11/05/2022 12:28, Stanis=C5=82aw Kardach: > On Wed, May 11, 2022 at 10:09 AM Morten Br=C3=B8rup wrote: > > > From: Thomas Monjalon [mailto:thomas@monjalon.net] > > > 09/05/2022 14:24, Stanis=C5=82aw Kardach: > > > > On Fri, May 6, 2022 at 11:13 AM David Marchand wrote: > > > > > About the new "Sponsored-by" tag, it should not raise warnings in > > > > > the CI if we agree on its addition. > > > >=20 > > > > I'll modify it in V2 to be in form of: > > > > Sponsored by: StarFive Technology > > > > > > You mean removing the hyphen? > > > I think it is better to keep it so all tags have the same format. > > > > I agree with Thomas. Please keep the hyphen. > > > > > > ... > > > > 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 get it! Should employees start adding > > Sponsored-by: to their commits, > > when doing it as part of their job? > > And how about contract developers, should they also add a > > Sponsored-by: tag, > > since they are working under contract and getting paid by that company? Nothing is mandatory. It is just a way to give visibility of the sponsorship if requested. > If I understand correctly, the concern about the commit log staying > technical and not introducing extra elements not beneficial to the > project, correct? > In the scope of this particular patchset, the companies sponsoring the > work are in copyrights for appropriate files, so I can remove the > tags. > For my own curiosity, what would be a proper way for a contract > developer to mark the company sponsoring the work? Some companies may > not care, others will. Maybe it would be beneficial to add a comment > on this into the contributing guide (or it's already there and I've > missed it)? I don't know how to do it better. Any other suggestions?