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 EF1F3A0548; Fri, 2 Apr 2021 10:08:07 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D7881140E11; Fri, 2 Apr 2021 10:08:07 +0200 (CEST) Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by mails.dpdk.org (Postfix) with ESMTP id 0249C4013F for ; Fri, 2 Apr 2021 10:08:05 +0200 (CEST) IronPort-SDR: hIHx+WvTddcKR7H56OR1knyX50e245g/49HGpYULI+WNnPbCyfzs97HSNDZembu5rphH1k/+o/ 1TnhQL48zfhA== X-IronPort-AV: E=McAfee;i="6000,8403,9941"; a="192449614" X-IronPort-AV: E=Sophos;i="5.81,299,1610438400"; d="scan'208";a="192449614" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Apr 2021 01:08:01 -0700 IronPort-SDR: KfFsYCbbPO4ypmHB7zg2M0dl7O3aEMtUB1amaCEYDsEzUJORcA7tiqM6tUF2iyfM7z+/FPTylq AeuQhKS5OWkg== X-IronPort-AV: E=Sophos;i="5.81,299,1610438400"; d="scan'208";a="413076832" Received: from obinchy-mobl.ger.corp.intel.com (HELO [10.213.215.97]) ([10.213.215.97]) by fmsmga008-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Apr 2021 01:07:59 -0700 To: "Min Hu (Connor)" , dev@dpdk.org References: <1617267209-25930-1-git-send-email-humin29@huawei.com> <61f1c3a3-ee4d-5606-4df0-579b5607010c@intel.com> <8ac461ed-021d-a017-fa79-167782df0247@huawei.com> From: Ferruh Yigit Cc: Luca Boccassi , Kevin Traynor , Christian Ehrhardt , Thomas Monjalon , David Marchand X-User: ferruhy Message-ID: <6c726d96-422d-61e0-0128-3622eb70aca7@intel.com> Date: Fri, 2 Apr 2021 09:07:55 +0100 MIME-Version: 1.0 In-Reply-To: <8ac461ed-021d-a017-fa79-167782df0247@huawei.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] [PATCH] net/hns3: use the correct HiSilicon copyright 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 Sender: "dev" On 4/2/2021 2:45 AM, Min Hu (Connor) wrote: > > > 在 2021/4/1 22:45, Ferruh Yigit 写道: >> On 4/1/2021 9:53 AM, Min Hu (Connor) wrote: >>> According to the suggestion of our legal department, >>> to standardize the copyright license of our code to >>> avoid potential copyright risks, we make a unified >>> modification to the "Hisilicon", which was nonstandard, >>> in the main modules we maintain. >>> >>> We change it to "HiSilicon", which is consistent with >>> the terms used on the following official website: >>> https://www.hisilicon.com/en/terms-of-use. >>> >>> Fixes: 565829db8b8f ("net/hns3: add build and doc infrastructure") >>> Fixes: 952ebacce4f2 ("net/hns3: support SVE Rx") >>> Fixes: e31f123db06b ("net/hns3: support NEON Tx") >>> Fixes: c09c7847d892 ("net/hns3: support traffic management") >>> >> >> Is backport not requested intentionally? >> > Yes, we think this is just spelling bug, which does not affect > functionality, so there is no need to backport. > > By the way, Is there any standard for which patch should be backported? We are backporting fixes, unless the fix doesn't apply to an old version somehow, like some patches fixes problems coming from external components, like problem comes with new version of FW that is not used by LTS code etc..., these doesn't need to be backported to old versions. Personally I am for backporting as much as possible, even syntax changes, because in long term they may cause conflicts and cause trouble merging actual fixes. Also for someone who gets a diff between latest and LTS version code, it helps to reduce the noise. cc'ed LTS maintainers for more authoritative response, at the end of the day they get the patches to the stable trees. >>> Signed-off-by: Min Hu (Connor) >> >> <...> >> >> >> .