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 05BCEA034F; Tue, 9 Nov 2021 15:45:01 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B80C140E03; Tue, 9 Nov 2021 15:45:00 +0100 (CET) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by mails.dpdk.org (Postfix) with ESMTP id BCD764068B for ; Tue, 9 Nov 2021 15:44:59 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 66E525C00F3; Tue, 9 Nov 2021 09:44:58 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Tue, 09 Nov 2021 09:44:58 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm2; bh= JzJEtpu+rRLRG46ZHo5cqHYJv9HOzTOVQusMt6EWwkE=; b=rb28Ma4GQ0E66KNv w8KreSjcFzt3vW8lIMDVbT/kKWy/YxtRU2xGrJX4C30lWGbQNKd38JMqXDU34ozk hG6hBuWmU7SJPsKQnfybDJguc8uS1BZ1/yLd2DkX05V/zbglqwAtw946f8BidaXV IuxE403m0EbOC5XluI+LdzZONdFd/nKRJvn3m+1LWalZAXe3tTFiKBjOf6OIHPPg V4T7MhgrNi+HxoSW4uZMVfg+Ybd4YIRypNgu16ORsL61s9w1n7vZ49/KEmEF3byK GYAEmH3qUpwvrdXs2rcgnzdVnAXlXkgjG6l3v5c35cuhlpBokiKaEOvq/PkWVqY0 oVWesg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=JzJEtpu+rRLRG46ZHo5cqHYJv9HOzTOVQusMt6EWw kE=; b=OCoSWjzbuGA3ptLbDZhqtNXmZ1iLXE2GpW0Zd486H1nXHZjNHUeT579vj 4IaqJKHIGKwldMvqsaDNPtb5Bw6yNDs59bgyLoM1M4xHn4nDKQHVZMGbpZSKWpTa nmd5ORgNvYbzA2fPfP1MTPXM3fgYKd6uUTnWFqqjDZGBzSFxPri6qKeevoymrmru PUFfyjwlq37xesWDsxoW3QDH0o0hdxXjYWqVLvCAeHGDWsxmPF47YuaMO2l6WhEN 9P+4QYFq/seIh4fksAoQFstDe9Xa/T1o4CUC8VPJdiw6MpA2CS0T4+3DPmp2MV1C BHkj42MbabdpPSWltQq6Zd1w80xJg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrudeggdeijecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucggtf frrghtthgvrhhnpedugefgvdefudfftdefgeelgffhueekgfffhfeujedtteeutdejueei iedvffegheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhroh hmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 9 Nov 2021 09:44:57 -0500 (EST) From: Thomas Monjalon To: Gagandeep Singh Cc: dev@dpdk.org, nipun.gupta@nxp.com, david.marchand@redhat.com, ferruh.yigit@intel.com, gakhil@marvell.com, hemant.agrawal@nxp.com Date: Tue, 09 Nov 2021 15:44:56 +0100 Message-ID: <2155251.kCPDGmGbOk@thomas> In-Reply-To: <20211109043910.4016824-2-g.singh@nxp.com> References: <20211108090704.3585175-2-g.singh@nxp.com> <20211109043910.4016824-1-g.singh@nxp.com> <20211109043910.4016824-2-g.singh@nxp.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v4 1/5] dma/dpaa: introduce DPAA DMA driver 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" 09/11/2021 05:39, Gagandeep Singh: > The DPAA DMA driver is an implementation of the dmadev APIs, > that provide means to initiate a DMA transaction from CPU. > The initiated DMA is performed without CPU being involved > in the actual DMA transaction. This is achieved via using > the QDMA controller of DPAA SoC. > > Signed-off-by: Gagandeep Singh > --- > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -1377,6 +1377,17 @@ F: drivers/raw/dpaa2_qdma/ > F: doc/guides/rawdevs/dpaa2_qdma.rst > > > + > +Dmadev Drivers > +-------------- > + > +NXP DPAA DMA > +M: Gagandeep Singh > +M: Nipun Gupta > +F: drivers/dma/dpaa/ > +F: doc/guides/dmadevs/dpaa.rst > + > + There is already a section for DMA drivers. > Packet processing > ----------------- > [...] > --- /dev/null > +++ b/doc/guides/dmadevs/dpaa.rst > @@ -0,0 +1,54 @@ > +.. SPDX-License-Identifier: BSD-3-Clause > + Copyright 2021 NXP > + > +NXP DPAA DMA Driver > +===================== There are other occurences in this patch of a lack of attention. Doing underlining of correct length is a minimum when starting a doc. > --- a/doc/guides/rel_notes/release_21_11.rst > +++ b/doc/guides/rel_notes/release_21_11.rst > @@ -20,6 +20,9 @@ DPDK Release 21.11 > ninja -C build doc > xdg-open build/doc/guides/html/rel_notes/release_21_11.html > > +* **Added NXP DPAA DMA driver.** > + > + * Added a new dmadev driver for NXP DPAA platform. > > New Features > ------------ The new features should be inside this section and well sorted. There are a lot of other details that I won't report. All of this look to be on purpose, or a big negligence. In any case, it looks to me as sending some junk work to my face. I am too kind, so I will fix all, and will merge after the deadline passed. But please remember that I don't forget such attitude, and I think other maintainers won't forget as well.