From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.5 required=3.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_PASS,USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 79D69C10F0E for ; Tue, 9 Apr 2019 17:36:50 +0000 (UTC) Received: from dpdk.org (dpdk.org [92.243.14.124]) by mail.kernel.org (Postfix) with ESMTP id 096D020833 for ; Tue, 9 Apr 2019 17:36:49 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="HX9lsr2t" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 096D020833 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dev-bounces@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 426C44F91; Tue, 9 Apr 2019 19:36:47 +0200 (CEST) Received: from mail-wm1-f65.google.com (mail-wm1-f65.google.com [209.85.128.65]) by dpdk.org (Postfix) with ESMTP id 96E854CC3; Tue, 9 Apr 2019 19:36:45 +0200 (CEST) Received: by mail-wm1-f65.google.com with SMTP id z24so4322091wmi.5; Tue, 09 Apr 2019 10:36:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=YquLE+8LblEvmpIfHixACADhQVRiW0o29cC2lcmk5NI=; b=HX9lsr2ta3DJChmyYhAxlJ8yGi0l7ew/D9Yll5Y/RQeJCaUPUZGQCTqLR5BHyiaSz1 cEJuEVzkPNDwOCMGgYeAMm4MSgyCNZ63HzQZ7R1AqA3tAe+exj4LiWDJjMC1CeQA96Ph 3W7GHFYL6dPRLLXeDjHC96ISf6Kl0oBeSO8i1/4Q50FBwXm5schuMyDGAcQtjFB1h/hT JwaeiukIPkT+5db1BS0J6IX+nWdnotYKvVIWwzIvMRv3CyS6YFI8KxadX1/L00TCu6wJ S0HrjAD/mY+GJvSQH2S3DfIlAB9yW+FZ+8hoy1PzSRBruKgGYSraNrTUtcToPR32HMS7 2tPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=YquLE+8LblEvmpIfHixACADhQVRiW0o29cC2lcmk5NI=; b=gsJahqlNDnFezfxkZcfezE1uhOBf44E7+F1YPr3Vn/kgzaFnPyXtCkoGMlEQ3P9yBr YvyAwycoxdHVqSIGxFhd0NpSU9TxLGlb2AaydGDT3UcgsI4BLHosZgodpdUdQTHNceVa kodsb/Ux+pl5uoVnCMtN5gkLrn4hbTKMVyAU07G6Fap/OhHDy5PWfxCwxdUEosqPyFdW XlUO7qOuOg2DEt34BnVJJVYlY3t02x0BQcUYVqSd3390XoB81F8C08klU9EF25WMPsLi K45DEhvoaqGsQSyoprdaZ2NPrQsPXYzsDRspvLojyVHOCNoWK5eCGbBfbSFb2QLOnuan bSoA== X-Gm-Message-State: APjAAAVpV93qGjHSNwmH8pSRxiBhmNrJ7cyBH5xjEVKgpEQrr/9Q6f5F ayIuoUqW23GYc2nrutZka5RZxN5/JRbqfyNV X-Google-Smtp-Source: APXvYqw6DJNjRK3vmSjgL43aKzAQjSjsjzUJPVeRifpMXyLG/wAZ6jfNq4WjFHAQAjLX1/DeY2A2zw== X-Received: by 2002:a05:600c:c4:: with SMTP id u4mr23173150wmm.80.1554831405062; Tue, 09 Apr 2019 10:36:45 -0700 (PDT) Received: from localhost.localdomain (bzq-109-64-23-174.red.bezeqint.net. [109.64.23.174]) by smtp.gmail.com with ESMTPSA id a9sm30833295wrt.29.2019.04.09.10.36.43 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 09 Apr 2019 10:36:44 -0700 (PDT) From: Rami Rosen To: dev@dpdk.org Cc: ferruh.yigit@intel.com, pablo.de.lara.guarch@intel.com, akhil.goyal@nxp.com, john.mcnamara@intel.com, marko.kovacevic@intel.com, Rami Rosen , stable@dpdk.org Date: Tue, 9 Apr 2019 20:36:35 +0300 Message-Id: <20190409173635.5127-1-ramirose@gmail.com> X-Mailer: git-send-email 2.19.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [dpdk-dev] [PATCH] doc: add guideines for initial PMD submission X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 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" This patch for DPDK Contributor's Guidelines indicates the repos against which a new PMD should be prepared; for new network ethernet PMDs it should be dpdk-next-net, and for new crypto PMDs it should be dpdk-next-crypto. Though this may seem obvious, it is not mentioned in DPDK documentation. Cc: stable@dpdk.org Signed-off-by: Rami Rosen --- doc/guides/contributing/patches.rst | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/guides/contributing/patches.rst b/doc/guides/contributing/patches.rst index d8404e623..4dde8e724 100644 --- a/doc/guides/contributing/patches.rst +++ b/doc/guides/contributing/patches.rst @@ -148,6 +148,10 @@ Make your planned changes in the cloned ``dpdk`` repo. Here are some guidelines * If you add new files or directories you should add your name to the ``MAINTAINERS`` file. +* If you add a new network PMD you should prepare the initial submission against dpdk-next-net repo. + +* If you add a new crypto PMD you should prepare the initial submission against dpdk-next-crypto repo. + * New external functions should be added to the local ``version.map`` file. See the :doc:`Guidelines for ABI policy and versioning `. New external functions should also be added in alphabetical order. -- 2.19.2