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 3E07246729 for ; Mon, 12 May 2025 16:50:36 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 37834402CA; Mon, 12 May 2025 16:50:36 +0200 (CEST) Received: from mail.loongson.cn (mail.loongson.cn [114.242.206.163]) by mails.dpdk.org (Postfix) with ESMTP id E56CC402C9 for ; Mon, 12 May 2025 16:50:34 +0200 (CEST) Received: from loongson.cn (unknown [10.40.64.71]) by gateway (Coremail) with SMTP id _____8Axz3O4CiJo72rhAA--.39696S3; Mon, 12 May 2025 22:50:32 +0800 (CST) Received: from localhost.localdomain (unknown [10.40.64.71]) by front1 (Coremail) with SMTP id qMiowMAxj8W1CiJoqnPKAA--.58497S3; Mon, 12 May 2025 22:50:29 +0800 (CST) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.15.2/8.15.2) with ESMTPS id 54CEEGui1062694 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Mon, 12 May 2025 22:14:16 +0800 Received: (from root@localhost) by localhost.localdomain (8.15.2/8.15.2/Submit) id 54CEEG3d1062693; Mon, 12 May 2025 22:14:16 +0800 Date: Mon, 12 May 2025 22:14:16 +0800 From: qemudev@loongson.cn Message-Id: <202505121414.54CEEG3d1062693@localhost.localdomain> Content-Type: text/plain; charset="utf-8" Subject: |WARNING| pw153422 [PATCH] doc: reword contributor's guidelines In-Reply-To: <20250512144842.29976-1-nandinipersad361@gmail.com> References: <20250512144842.29976-1-nandinipersad361@gmail.com> To: test-report@dpdk.org Cc: Nandini Persad , zhoumin@loongson.cn X-CM-TRANSID: qMiowMAxj8W1CiJoqnPKAA--.58497S3 X-CM-SenderInfo: pthp3vthy6z05rqj20fqof0/1tbiAgEAD2ghL2gRqAAAs7 X-Coremail-Antispam: 1Uk129KBj93XoWxJF43ur13Ar4fWw4DAr4DKFX_yoW5KFWfpF n8Jr9rCr4ktr43G392yr4fZFyrZa95Ga45X3WrG348ZFnxGr1vvw4xtayF9as8XryS93sr Xa129r97Z3WkZFgCm3ZEXasCq-sJn29KB7ZKAUJUUUUU529EdanIXcx71UUUUU7KY7ZEXa sCq-sGcSsGvfJ3Ic02F40EFcxC0VAKzVAqx4xG6I80ebIjqfuFe4nvWSU5nxnvy29KBjDU 0xBIdaVrnRJUUUyCb4IE77IF4wAFF20E14v26r1j6r4UM7CY07I20VC2zVCF04k26cxKx2 IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rwA2F7IY1VAKz4vEj48v e4kI8wA2z4x0Y4vE2Ix0cI8IcVAFwI0_Xr0_Ar1l84ACjcxK6xIIjxv20xvEc7CjxVAFwI 0_Gr0_Cr1l84ACjcxK6I8E87Iv67AKxVW0oVCq3wA2z4x0Y4vEx4A2jsIEc7CjxVAFwI0_ GcCE3s1le2I262IYc4CY6c8Ij28IcVAaY2xG8wAqjxCEc2xF0cIa020Ex4CE44I27wAqx4 xG64xvF2IEw4CE5I8CrVC2j2WlYx0E2Ix0cI8IcVAFwI0_Jr0_Jr4lYx0Ex4A2jsIE14v2 6r1j6r4UMcvjeVCFs4IE7xkEbVWUJVW8JwAKzVCY07xG64k0F24l42xK82IYc2Ij64vIr4 1l4I8I3I0E4IkC6x0Yz7v_Jr0_Gr1lx2IqxVAqx4xG67AKxVWUJVWUGwC20s026x8GjcxK 67AKxVWUGVWUWwC2zVAF1VAY17CE14v26r1Y6r17MIIYrxkI7VAKI48JMIIF0xvE2Ix0cI 8IcVAFwI0_Jr0_JF4lIxAIcVC0I7IYx2IY6xkF7I0E14v26r1j6r4UMIIF0xvE42xK8VAv wI8IcIk0rVWUJVWUCwCI42IY6I8E87Iv67AKxVWUJVW8JwCI42IY6I8E87Iv6xkF7I0E14 v26r1j6r4UYxBIdaVFxhVjvjDU0xZFpf9x07jUa9-UUUUU= X-BeenThere: test-report@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: automatic DPDK test reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: test-report-bounces@dpdk.org Test-Label: loongarch-compilation Test-Status: WARNING http://dpdk.org/patch/153422 _apply patch failure_ Submitter: Nandini Persad Date: Mon, 12 May 2025 07:48:41 -0700 DPDK git baseline: Repo:dpdk Branch: main CommitID: 75f179ebe347b6098cf3af26d3d3b7168fe3fe24 Apply patch set 153422 failed: Checking patch doc/guides/contributing/linux_uapi.rst... Checking patch doc/guides/contributing/patches.rst... error: while searching for: git clone git://dpdk.org/next/dpdk-next-* git clone https://dpdk.org/git/next/dpdk-next-* Make your Changes ----------------- Make your planned changes in the cloned ``dpdk`` repo. Here are some guidelines and requirements: * Follow the :ref:`coding_style` guidelines. * If you are a new contributor, or if your mail address changed, you may update the ``.mailmap`` file. Otherwise the new name or address will be added by a maintainer. Keeping this file up-to-date will help when someone wants to contact you about the changes you contributed to. * If you add new files or directories you should add your name to the ``MAINTAINERS`` file. * Initial submission of new PMDs should be prepared against a corresponding repo. * Thus, for example, initial submission of a new network PMD should be prepared against dpdk-next-net repo. * Likewise, initial submission of a new crypto or compression PMD should be prepared against dpdk-next-crypto repo. * For other PMDs and more info, refer to the ``MAINTAINERS`` file. * New external functions should be added to the local ``version.map`` file. See the :doc:`ABI policy ` and :ref:`ABI versioning ` guides. New external functions should also be added in alphabetical order. * Any new API function should be used in ``/app`` test directory. * When introducing a new device API, at least one driver should implement it. * Important changes will require an addition to the release notes in ``doc/guides/rel_notes/``. See the :ref:`Release Notes section of the Documentation Guidelines ` for details. * Test the compilation works with different targets, compilers and options, see :ref:`contrib_check_compilation`. * Don't break compilation between commits with forward dependencies in a patchset. Each commit should compile on its own to allow for ``git bisect`` and continuous integration testing. * Add tests to the ``app/test`` unit test framework where possible. * Add documentation, if relevant, in the form of Doxygen comments or a User Guide in RST format. See the :ref:`Documentation Guidelines `. * Code and related documentation must be updated atomically in the same patch. Once the changes have been made you should commit them to your local repo. For small changes, that do not require specific explanations, it is better to keep things together in the same patch. Larger changes that require different explanations should be separated into logical patches in a patchset. A good way of thinking about whether a patch should be split is to consider whether the change could be applied without dependencies as a backport. As a guide to how patches should be structured run ``git log`` on similar files. Commit Messages: Subject Line error: patch failed: doc/guides/contributing/patches.rst:135 error: doc/guides/contributing/patches.rst: patch does not apply Checking patch doc/guides/contributing/stable.rst... Checking patch doc/guides/contributing/vulnerability.rst...