From patchwork Wed Mar 30 04:24:52 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jakub Kicinski X-Patchwork-Id: 12795422 X-Patchwork-Delegate: kuba@kernel.org Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id C933EC433FE for ; Wed, 30 Mar 2022 04:25:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242503AbiC3E07 (ORCPT ); Wed, 30 Mar 2022 00:26:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39230 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235419AbiC3E06 (ORCPT ); Wed, 30 Mar 2022 00:26:58 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6C44CDF12; Tue, 29 Mar 2022 21:25:13 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id A0F4161550; Wed, 30 Mar 2022 04:25:12 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 968FEC340F0; Wed, 30 Mar 2022 04:25:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1648614312; bh=U+RoGeVHl41hvHJbe4CNBvquzt03zw4gxBoZIfdKUws=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=b9YRWp6Id4s99rqTmtqXl/okNYYgNqOWMFLMEtMML3+mmnQ05N+pvwPh+8QVS0WEE Qukzw5mrEt3GznuZFM3vVNGidCGKMb/1cxP9teDQ1ngR62vgnFnxL84gMZL+blf2O5 QWzzPeVwGEWuyWDOlso9+YRw94fZoxezNEg6OZKk/L57i07X/9v1PKGDVcZg1pN6sq gieJPtxd6SBxfcLD6BgRanv95Yr8dlM6PWBQfhEQVrpbAWMFRe7II0m+bsSMLgoP4n vp0NW7u9qHaho9yB4D4unsIElNNKb9Ept7cOU6JBb/USciFwHvA3TKJ/aaReL828YF xaIkJZJNn1nWw== From: Jakub Kicinski To: davem@davemloft.net Cc: netdev@vger.kernel.org, pabeni@redhat.com, corbet@lwn.net, bpf@vger.kernel.org, linux-doc@vger.kernel.org, andrew@lunn.ch, f.fainelli@gmail.com, Jakub Kicinski Subject: [PATCH net v3 01/14] docs: netdev: replace references to old archives Date: Tue, 29 Mar 2022 21:24:52 -0700 Message-Id: <20220330042505.2902770-2-kuba@kernel.org> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20220330042505.2902770-1-kuba@kernel.org> References: <20220330042505.2902770-1-kuba@kernel.org> MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org X-Patchwork-Delegate: kuba@kernel.org Most people use (or should use) lore at this point. Replace the pointers to older archiving systems. Signed-off-by: Jakub Kicinski Reviewed-by: Florian Fainelli --- Documentation/networking/netdev-FAQ.rst | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/Documentation/networking/netdev-FAQ.rst b/Documentation/networking/netdev-FAQ.rst index e26532f49760..25b8a7de737c 100644 --- a/Documentation/networking/netdev-FAQ.rst +++ b/Documentation/networking/netdev-FAQ.rst @@ -16,10 +16,8 @@ Note that some subsystems (e.g. wireless drivers) which have a high volume of traffic have their own specific mailing lists. The netdev list is managed (like many other Linux mailing lists) through -VGER (http://vger.kernel.org/) and archives can be found below: - -- http://marc.info/?l=linux-netdev -- http://www.spinics.net/lists/netdev/ +VGER (http://vger.kernel.org/) with archives available at +https://lore.kernel.org/netdev/ Aside from subsystems like that mentioned above, all network-related Linux development (i.e. RFC, review, comments, etc.) takes place on From patchwork Wed Mar 30 04:24:53 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jakub Kicinski X-Patchwork-Id: 12795424 X-Patchwork-Delegate: kuba@kernel.org Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id DC129C43217 for ; Wed, 30 Mar 2022 04:25:21 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242514AbiC3E1A (ORCPT ); Wed, 30 Mar 2022 00:27:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39228 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229891AbiC3E06 (ORCPT ); Wed, 30 Mar 2022 00:26:58 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CC3DBDF58; Tue, 29 Mar 2022 21:25:13 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 2A4BB61552; Wed, 30 Mar 2022 04:25:13 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 2B58EC34112; Wed, 30 Mar 2022 04:25:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1648614312; bh=ibPzGpYP5ul+5VCwSW0FJEX+gMTvTy87AoOUvx1t1b4=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=gENQQOITiXvTvlLW1paZURN/arNkdkzqbUnpqtvSP4miMNGZeI9Ji9uNEEc8ETnLU SSu19DbQ7zKvqMFHsYlChkFnO+mPeTnO2C1dVpxB94VVDigH8aimFdNq7iJo2JYLXI sbUqAfsEwy36xI43jHr9lpvGSIV68pFxGCNZn6nlHOoPZvUKriRPtkJMh8YC7iEZBA Q9+A0gdHMrXn5Ool+hgrbmy/AKck5MwoTmMsTuWoPCYVryVHa3qortECi+SLuYa1TR utbABR+wbBuAgySfH2eWLxM2+4ou046/C+hz8ROi/8vygW15wLyJOMrwovvKE/0mGi kZfEd4iUl4W9Q== From: Jakub Kicinski To: davem@davemloft.net Cc: netdev@vger.kernel.org, pabeni@redhat.com, corbet@lwn.net, bpf@vger.kernel.org, linux-doc@vger.kernel.org, andrew@lunn.ch, f.fainelli@gmail.com, Jakub Kicinski Subject: [PATCH net v3 02/14] docs: netdev: minor reword Date: Tue, 29 Mar 2022 21:24:53 -0700 Message-Id: <20220330042505.2902770-3-kuba@kernel.org> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20220330042505.2902770-1-kuba@kernel.org> References: <20220330042505.2902770-1-kuba@kernel.org> MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org X-Patchwork-Delegate: kuba@kernel.org that -> those Signed-off-by: Jakub Kicinski Reviewed-by: Florian Fainelli --- Documentation/networking/netdev-FAQ.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/networking/netdev-FAQ.rst b/Documentation/networking/netdev-FAQ.rst index 25b8a7de737c..f7e5755e013e 100644 --- a/Documentation/networking/netdev-FAQ.rst +++ b/Documentation/networking/netdev-FAQ.rst @@ -19,7 +19,7 @@ The netdev list is managed (like many other Linux mailing lists) through VGER (http://vger.kernel.org/) with archives available at https://lore.kernel.org/netdev/ -Aside from subsystems like that mentioned above, all network-related +Aside from subsystems like those mentioned above, all network-related Linux development (i.e. RFC, review, comments, etc.) takes place on netdev. From patchwork Wed Mar 30 04:24:54 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jakub Kicinski X-Patchwork-Id: 12795425 X-Patchwork-Delegate: kuba@kernel.org Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id F1F52C4167B for ; Wed, 30 Mar 2022 04:25:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241100AbiC3E1E (ORCPT ); Wed, 30 Mar 2022 00:27:04 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39268 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239331AbiC3E06 (ORCPT ); Wed, 30 Mar 2022 00:26:58 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3EB0ADF77; Tue, 29 Mar 2022 21:25:14 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id AE3E961557; Wed, 30 Mar 2022 04:25:13 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id B1FD4C34113; Wed, 30 Mar 2022 04:25:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1648614313; bh=UsrRGzreh0yhSlb7JDzUQnpiSfmiX+Wi47jWa5ruVEA=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=pg1VmtAQv9x8fnu25+qLYB8QZXzEsbwcjhu00JGeGXTGVacEiQ04SbTTrxtcauaos wEIOL4yh+IB1ejODBRF0TwpG0T+bab/6TMrhTs2c9pCfZw1wSfWZdDl4jdj/EAIGxe xiXky+fRMaou7sgAenGYf4pvNf9fzvCrfnLWn41SqM9eOWy7DhiMBsizqc4jELV/4Q arDwCqTaSTJH0I60TOmgWSnwwD6xWxHWL/DuUu+2EwyldS/v9oWZU8toB5adik0naY xmsKTUmCxUV9J92IJ4/ojFHB0Ov8ZBT+Y3q5MY9u6aSBvcj1AnMYpXcWrvZnUnwVoq BlwoQw2LAY04g== From: Jakub Kicinski To: davem@davemloft.net Cc: netdev@vger.kernel.org, pabeni@redhat.com, corbet@lwn.net, bpf@vger.kernel.org, linux-doc@vger.kernel.org, andrew@lunn.ch, f.fainelli@gmail.com, Jakub Kicinski Subject: [PATCH net v3 03/14] docs: netdev: move the patch marking section up Date: Tue, 29 Mar 2022 21:24:54 -0700 Message-Id: <20220330042505.2902770-4-kuba@kernel.org> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20220330042505.2902770-1-kuba@kernel.org> References: <20220330042505.2902770-1-kuba@kernel.org> MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org X-Patchwork-Delegate: kuba@kernel.org We want people to mark their patches with net and net-next in the subject. Many miss doing that. Move the FAQ section which points that out up, and place it after the section which enumerates the trees, that seems like a pretty logical place for it. Since the two sections are together we can remove a little bit (not too much) of the repetition. v2: also remove the text for non-git setups, we want people to use git. Signed-off-by: Jakub Kicinski Reviewed-by: Andrew Lunn Reviewed-by: Florian Fainelli --- Documentation/networking/netdev-FAQ.rst | 25 +++++++++++-------------- 1 file changed, 11 insertions(+), 14 deletions(-) diff --git a/Documentation/networking/netdev-FAQ.rst b/Documentation/networking/netdev-FAQ.rst index f7e5755e013e..fd5f5a1a0846 100644 --- a/Documentation/networking/netdev-FAQ.rst +++ b/Documentation/networking/netdev-FAQ.rst @@ -35,6 +35,17 @@ mainline tree from Linus, and ``net-next`` is where the new code goes - https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git - https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git +How do I indicate which tree (net vs. net-next) my patch should be in? +---------------------------------------------------------------------- +To help maintainers and CI bots you should explicitly mark which tree +your patch is targeting. Assuming that you use git, use the prefix +flag:: + + git format-patch --subject-prefix='PATCH net-next' start..finish + +Use ``net`` instead of ``net-next`` (always lower case) in the above for +bug-fix ``net`` content. + How often do changes from these trees make it to the mainline Linus tree? ------------------------------------------------------------------------- To understand this, you need to know a bit of background information on @@ -90,20 +101,6 @@ and note the top of the "tags" section. If it is rc1, it is early in the dev cycle. If it was tagged rc7 a week ago, then a release is probably imminent. -How do I indicate which tree (net vs. net-next) my patch should be in? ----------------------------------------------------------------------- -Firstly, think whether you have a bug fix or new "next-like" content. -Then once decided, assuming that you use git, use the prefix flag, i.e. -:: - - git format-patch --subject-prefix='PATCH net-next' start..finish - -Use ``net`` instead of ``net-next`` (always lower case) in the above for -bug-fix ``net`` content. If you don't use git, then note the only magic -in the above is just the subject text of the outgoing e-mail, and you -can manually change it yourself with whatever MUA you are comfortable -with. - I sent a patch and I'm wondering what happened to it - how can I tell whether it got merged? -------------------------------------------------------------------------------------------- Start by looking at the main patchworks queue for netdev: From patchwork Wed Mar 30 04:24:55 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jakub Kicinski X-Patchwork-Id: 12795430 X-Patchwork-Delegate: kuba@kernel.org Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0DBBDC433FE for ; Wed, 30 Mar 2022 04:25:36 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242575AbiC3E1Q (ORCPT ); Wed, 30 Mar 2022 00:27:16 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39386 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242523AbiC3E1C (ORCPT ); Wed, 30 Mar 2022 00:27:02 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 454F5DF58; Tue, 29 Mar 2022 21:25:16 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id F1410B81B38; Wed, 30 Mar 2022 04:25:14 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 451F7C340F2; Wed, 30 Mar 2022 04:25:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1648614313; bh=xUrwySdk8pPWDD17ccX90NEP3D7DzJVSGSGlzNVJ3lY=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=VlC1kSJ2BPl5WFsAK9ywdoWnCJn+RRBLY1/V9H40+EtFDIIvOaCN7LRH0ZL/q/t1n HXjddKaAcu/lqtc2A5L3lG34RhstkQeHW6nEalmAM+nIYj+KL3OZN89+/jaYay8rD3 BSwQ4cVAvJ7XqSvcDE6AMZYMhx7jasxcKGPMiicxL0fz9tvCgv3CBdFy4sJYl3rRuY b89OcyyUR1W6LwNyroJsfoD5uheOGAfCmQMaH/0QyHIkArN1hVycZU5RnQ0BVtw9HR PgZ8PCO/Va4PVrJ2XjiRpEx1/Q7ZqsvEv2JQ/RED1mnzNyuNKbMi2zmG+es07Rgt1/ 2R2P0R0RRJEqA== From: Jakub Kicinski To: davem@davemloft.net Cc: netdev@vger.kernel.org, pabeni@redhat.com, corbet@lwn.net, bpf@vger.kernel.org, linux-doc@vger.kernel.org, andrew@lunn.ch, f.fainelli@gmail.com, Jakub Kicinski Subject: [PATCH net v3 04/14] docs: netdev: turn the net-next closed into a Warning Date: Tue, 29 Mar 2022 21:24:55 -0700 Message-Id: <20220330042505.2902770-5-kuba@kernel.org> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20220330042505.2902770-1-kuba@kernel.org> References: <20220330042505.2902770-1-kuba@kernel.org> MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org X-Patchwork-Delegate: kuba@kernel.org Use the sphinx Warning box to make the net-next being closed stand out more. Signed-off-by: Jakub Kicinski Reviewed-by: Florian Fainelli --- Documentation/networking/netdev-FAQ.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/Documentation/networking/netdev-FAQ.rst b/Documentation/networking/netdev-FAQ.rst index fd5f5a1a0846..041993258dda 100644 --- a/Documentation/networking/netdev-FAQ.rst +++ b/Documentation/networking/netdev-FAQ.rst @@ -70,8 +70,9 @@ relating to vX.Y An announcement indicating when ``net-next`` has been closed is usually sent to netdev, but knowing the above, you can predict that in advance. -IMPORTANT: Do not send new ``net-next`` content to netdev during the -period during which ``net-next`` tree is closed. +.. warning:: + Do not send new ``net-next`` content to netdev during the + period during which ``net-next`` tree is closed. Shortly after the two weeks have passed (and vX.Y-rc1 is released), the tree for ``net-next`` reopens to collect content for the next (vX.Y+1) From patchwork Wed Mar 30 04:24:56 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jakub Kicinski X-Patchwork-Id: 12795426 X-Patchwork-Delegate: kuba@kernel.org Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 27316C433FE for ; Wed, 30 Mar 2022 04:25:30 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242531AbiC3E1F (ORCPT ); Wed, 30 Mar 2022 00:27:05 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39270 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242499AbiC3E06 (ORCPT ); Wed, 30 Mar 2022 00:26:58 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D572FDFE2; Tue, 29 Mar 2022 21:25:14 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 6630E61561; Wed, 30 Mar 2022 04:25:14 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id CD663C340F0; Wed, 30 Mar 2022 04:25:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1648614314; bh=GiQdRnvOD79OWqlDvg6Sf9vtrfZD84+3sCIuYPexe1U=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=gSGhcRD5JWoHlxMqNPIsPDmbTMb30xYVQxshK/PgfHfWBQXBwMAoUskIe7KaDS6wu 56DVEfK1Nm0CkEfo5JaEdzVbzcj3DFPGmxyHjsF1qt0vg+4CJSrjzUHz4PoHpnkPoT QZDLtyRK5yn12tfKgzWQpkUrS4D6oN9mRZNqhU1oaQIZDYNsAjZgsZ0wXteAofXp7v 3v+6aplyh1PiCluiPQCNuI1/ZjYgHc50hXS3p++tt7A5NsW7+lXnvLfVoV+hOpCHts R1/mYaJXLria8Ppt6b2TzfzyjZb6nKArKT6ozLv+vNZC38PTgxbAx185P/anecl+L6 MLP7TzMJuHFQg== From: Jakub Kicinski To: davem@davemloft.net Cc: netdev@vger.kernel.org, pabeni@redhat.com, corbet@lwn.net, bpf@vger.kernel.org, linux-doc@vger.kernel.org, andrew@lunn.ch, f.fainelli@gmail.com, Jakub Kicinski Subject: [PATCH net v3 05/14] docs: netdev: note that RFC postings are allowed any time Date: Tue, 29 Mar 2022 21:24:56 -0700 Message-Id: <20220330042505.2902770-6-kuba@kernel.org> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20220330042505.2902770-1-kuba@kernel.org> References: <20220330042505.2902770-1-kuba@kernel.org> MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org X-Patchwork-Delegate: kuba@kernel.org Document that RFCs are allowed during the merge window. Signed-off-by: Jakub Kicinski Reviewed-by: Andrew Lunn Reviewed-by: Florian Fainelli --- v2: new patch --- Documentation/networking/netdev-FAQ.rst | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Documentation/networking/netdev-FAQ.rst b/Documentation/networking/netdev-FAQ.rst index 041993258dda..f4c77efa75d4 100644 --- a/Documentation/networking/netdev-FAQ.rst +++ b/Documentation/networking/netdev-FAQ.rst @@ -74,6 +74,9 @@ sent to netdev, but knowing the above, you can predict that in advance. Do not send new ``net-next`` content to netdev during the period during which ``net-next`` tree is closed. +RFC patches sent for review only are obviously welcome at any time +(use ``--subject-prefix='RFC net-next'`` with ``git format-patch``). + Shortly after the two weeks have passed (and vX.Y-rc1 is released), the tree for ``net-next`` reopens to collect content for the next (vX.Y+1) release. From patchwork Wed Mar 30 04:24:57 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jakub Kicinski X-Patchwork-Id: 12795427 X-Patchwork-Delegate: kuba@kernel.org Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 46CEAC433F5 for ; Wed, 30 Mar 2022 04:25:30 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242534AbiC3E1J (ORCPT ); Wed, 30 Mar 2022 00:27:09 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39318 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242510AbiC3E07 (ORCPT ); Wed, 30 Mar 2022 00:26:59 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5E524DF12; Tue, 29 Mar 2022 21:25:15 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id EF3D16154F; Wed, 30 Mar 2022 04:25:14 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 61C56C34112; Wed, 30 Mar 2022 04:25:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1648614314; bh=Er8YOZixM4jKeeHVZrftGgBEi/e3ZfteGSGNqYpWtjM=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=BA5VY8mSCChbxjABGX8WigW4bg+X2p9siIcFqRng7P01Ogzjw07jDmzVoZA9ihQ/b wthG40uHPZZx72x32dfeQcvIlPNwrLkTY++TDLP7b64gFiT413wfmoeB7zI+ji9vaK PTRLrxvI9rwMae822272+reMWnfvry7Da1pJ/9haSmrj2PjazT3icBwG3R8wb1GY4a wwJyYhp7RTl/yNeVvHjDnShYf1JCdsSRpBclWfbJ0vAhsqf+SfvMQLfqMwEGeeEM6H vFqWqI8OlLldZP0KH+9tq4rpDMD8xX4FVKWodzODQDBtcbGpJJmj7GccXJzMPR1d7/ 1gFQ+5WtKJ2Sw== From: Jakub Kicinski To: davem@davemloft.net Cc: netdev@vger.kernel.org, pabeni@redhat.com, corbet@lwn.net, bpf@vger.kernel.org, linux-doc@vger.kernel.org, andrew@lunn.ch, f.fainelli@gmail.com, Jakub Kicinski Subject: [PATCH net v3 06/14] docs: netdev: shorten the name and mention msgid for patch status Date: Tue, 29 Mar 2022 21:24:57 -0700 Message-Id: <20220330042505.2902770-7-kuba@kernel.org> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20220330042505.2902770-1-kuba@kernel.org> References: <20220330042505.2902770-1-kuba@kernel.org> MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org X-Patchwork-Delegate: kuba@kernel.org Cut down the length of the question so it renders better in docs. Mention that Message-ID can be used to search patchwork. Signed-off-by: Jakub Kicinski Reviewed-by: Florian Fainelli --- Documentation/networking/netdev-FAQ.rst | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/Documentation/networking/netdev-FAQ.rst b/Documentation/networking/netdev-FAQ.rst index f4c77efa75d4..e10a8140d642 100644 --- a/Documentation/networking/netdev-FAQ.rst +++ b/Documentation/networking/netdev-FAQ.rst @@ -105,14 +105,16 @@ and note the top of the "tags" section. If it is rc1, it is early in the dev cycle. If it was tagged rc7 a week ago, then a release is probably imminent. -I sent a patch and I'm wondering what happened to it - how can I tell whether it got merged? --------------------------------------------------------------------------------------------- +How can I tell the status of a patch I've sent? +----------------------------------------------- Start by looking at the main patchworks queue for netdev: https://patchwork.kernel.org/project/netdevbpf/list/ The "State" field will tell you exactly where things are at with your -patch. +patch. Patches are indexed by the ``Message-ID`` header of the emails +which carried them so if you have trouble finding your patch append +the value of ``Message-ID`` to the URL above. The above only says "Under Review". How can I find out more? ------------------------------------------------------------- From patchwork Wed Mar 30 04:24:58 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jakub Kicinski X-Patchwork-Id: 12795428 X-Patchwork-Delegate: kuba@kernel.org Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B9EC6C43219 for ; Wed, 30 Mar 2022 04:25:31 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242542AbiC3E1L (ORCPT ); Wed, 30 Mar 2022 00:27:11 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39388 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242522AbiC3E1C (ORCPT ); Wed, 30 Mar 2022 00:27:02 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D7EE3DF12; Tue, 29 Mar 2022 21:25:17 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 96A68B81B3B; Wed, 30 Mar 2022 04:25:16 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id EB23BC34111; Wed, 30 Mar 2022 04:25:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1648614315; bh=l58mJnP81DtmPGRPX5qWvZ3Q2ots0mc89rQXBZoafjQ=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=jgbQubZUZ5HGW59kwd414J/Wj6kT1sHSErfPKwplGBQVy8s1D+7CQ929ewaPoeR9I WZSUEqNNPOjmet5Bqb5UUnw7scdoYvJnOznlG6Ry3H5tJJX5M2x7HEb9LpFS0tZs+V 6+E8H9PdaZQNGqU+WMNF2iCo+tIwk/n+o3xcwG6Knfu+PFpQNaxhgRst3EOfofJsqQ 8K+TkLaMdoUcQ24iBj0BmKjTp/vH6ef4Nl1Zj5GWKTzZQ86rtoIS8ZJ1UwIRpISpNA +NJJAyHyy1vOJLVJ+fQayew9f9ideNR00W1E7caRHJkRBworVSGTcsYd9a2FtNeLSe j+jSHg/OmA4oQ== From: Jakub Kicinski To: davem@davemloft.net Cc: netdev@vger.kernel.org, pabeni@redhat.com, corbet@lwn.net, bpf@vger.kernel.org, linux-doc@vger.kernel.org, andrew@lunn.ch, f.fainelli@gmail.com, Jakub Kicinski Subject: [PATCH net v3 07/14] docs: netdev: rephrase the 'Under review' question Date: Tue, 29 Mar 2022 21:24:58 -0700 Message-Id: <20220330042505.2902770-8-kuba@kernel.org> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20220330042505.2902770-1-kuba@kernel.org> References: <20220330042505.2902770-1-kuba@kernel.org> MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org X-Patchwork-Delegate: kuba@kernel.org The semantics of "Under review" have shifted. Reword the question about it a bit and focus it on the response time. Signed-off-by: Jakub Kicinski Reviewed-by: Florian Fainelli --- v3: remove the going back to the end of the queue threat --- Documentation/networking/netdev-FAQ.rst | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/Documentation/networking/netdev-FAQ.rst b/Documentation/networking/netdev-FAQ.rst index e10a8140d642..00ac300ebe6a 100644 --- a/Documentation/networking/netdev-FAQ.rst +++ b/Documentation/networking/netdev-FAQ.rst @@ -116,10 +116,12 @@ patch. Patches are indexed by the ``Message-ID`` header of the emails which carried them so if you have trouble finding your patch append the value of ``Message-ID`` to the URL above. -The above only says "Under Review". How can I find out more? -------------------------------------------------------------- +How long before my patch is accepted? +------------------------------------- Generally speaking, the patches get triaged quickly (in less than -48h). So be patient. Asking the maintainer for status updates on your +48h). But be patient, if your patch is active in patchwork (i.e. it's +listed on the project's patch list) the chances it was missed are close to zero. +Asking the maintainer for status updates on your patch is a good way to ensure your patch is ignored or pushed to the bottom of the priority list. From patchwork Wed Mar 30 04:24:59 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jakub Kicinski X-Patchwork-Id: 12795431 X-Patchwork-Delegate: kuba@kernel.org Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id D29F7C43219 for ; Wed, 30 Mar 2022 04:25:37 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242590AbiC3E1S (ORCPT ); Wed, 30 Mar 2022 00:27:18 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39474 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242526AbiC3E1D (ORCPT ); Wed, 30 Mar 2022 00:27:03 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 948D4DF77; Tue, 29 Mar 2022 21:25:18 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 4A49CB81B37; Wed, 30 Mar 2022 04:25:17 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7E3A8C34113; Wed, 30 Mar 2022 04:25:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1648614315; bh=vdjnHae9b0yzMsExMtKNC+WLL55dm1Lg2N7VoIhWL24=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=mTZKm4E8m33oHKpcKq7YJWQyiuUk3Jg8Wh1nkdORLbAzaSYkoe3W9+ofBksvmsr1v Efo823GVm4kHVuXHNv8YPJuwges2bN/XsGmR9gLj0uQY8/eS7IEZFw1PHpkWxZL7Jy deqZnwwOtOTxIhntyVYE+RNzLpJvr2jMIu2oXJZgjyD/ZWz3Ed7DUa2LVorBMD7uuL 5nZ3yNQLujZr6FV0et69NPdeiD4J3ZS3goiXAOUK66tEMFtSuzJ+bAKP58QrRZw/VV 0YiY014VRDr3+PJwyZT4iM1L1WYyAmQEcLlJ4CAcMdjACa0iBCEbwufLrLN3NRCTx1 4WQhPhw2g7j7Q== From: Jakub Kicinski To: davem@davemloft.net Cc: netdev@vger.kernel.org, pabeni@redhat.com, corbet@lwn.net, bpf@vger.kernel.org, linux-doc@vger.kernel.org, andrew@lunn.ch, f.fainelli@gmail.com, Jakub Kicinski Subject: [PATCH net v3 08/14] docs: netdev: rephrase the 'should I update patchwork' question Date: Tue, 29 Mar 2022 21:24:59 -0700 Message-Id: <20220330042505.2902770-9-kuba@kernel.org> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20220330042505.2902770-1-kuba@kernel.org> References: <20220330042505.2902770-1-kuba@kernel.org> MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org X-Patchwork-Delegate: kuba@kernel.org Make the question shorter and adjust the start of the answer accordingly. Signed-off-by: Jakub Kicinski Reviewed-by: Florian Fainelli --- Documentation/networking/netdev-FAQ.rst | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/Documentation/networking/netdev-FAQ.rst b/Documentation/networking/netdev-FAQ.rst index 00ac300ebe6a..9c455d08510d 100644 --- a/Documentation/networking/netdev-FAQ.rst +++ b/Documentation/networking/netdev-FAQ.rst @@ -125,9 +125,11 @@ Asking the maintainer for status updates on your patch is a good way to ensure your patch is ignored or pushed to the bottom of the priority list. -I submitted multiple versions of the patch series. Should I directly update patchwork for the previous versions of these patch series? --------------------------------------------------------------------------------------------------------------------------------------- -No, please don't interfere with the patch status on patchwork, leave +Should I directly update patchwork state of my own patches? +----------------------------------------------------------- +It may be tempting to help the maintainers and update the state of your +own patches when you post a new version or spot a bug. Please do not do that. +Interfering with the patch status on patchwork will only cause confusion. Leave it to the maintainer to figure out what is the most recent and current version that should be applied. If there is any doubt, the maintainer will reply and ask what should be done. From patchwork Wed Mar 30 04:25:00 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jakub Kicinski X-Patchwork-Id: 12795432 X-Patchwork-Delegate: kuba@kernel.org Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8D535C4321E for ; Wed, 30 Mar 2022 04:25:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242592AbiC3E1V (ORCPT ); Wed, 30 Mar 2022 00:27:21 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39684 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242535AbiC3E1K (ORCPT ); Wed, 30 Mar 2022 00:27:10 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1F2DADFEE; Tue, 29 Mar 2022 21:25:19 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id C7A89B81B3E; Wed, 30 Mar 2022 04:25:17 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 155BDC340F2; Wed, 30 Mar 2022 04:25:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1648614316; bh=Sllik6iaE1cFnQrEoRqBsr3czJlnZUnNA2SzJ7V4NuY=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=as41uzSoty88duMR3fFhyTHJE9rK2pjXJj2+tJ8sNPltO82uEfjew3y/3Ms6V8z8p 06iz4waRAfpwx9/z6MCzmI3t+/2r+GiDgtHQsnprRXCOvN/78jVCismJl3vZgf+VHJ /5H2/OK6zHePq7M26ITm8tgBqhP8SHJhxigvOKp03BERXs6Cmk5g6iwZ8Lyqgii/3n qCjUM8YHPspmbJOx4DBw93Az/KgXhOKgkTHq0oCKQKHqpEZWBcm4hYfHpFbyuFSkHN FRf3/OX7GxpA+JYFMk1abjUWzkEuAackYi8MXFXil/TxhVOZTPhilk8E5sHJqv/mm9 mVqqocCUzTTLg== From: Jakub Kicinski To: davem@davemloft.net Cc: netdev@vger.kernel.org, pabeni@redhat.com, corbet@lwn.net, bpf@vger.kernel.org, linux-doc@vger.kernel.org, andrew@lunn.ch, f.fainelli@gmail.com, Jakub Kicinski Subject: [PATCH net v3 09/14] docs: netdev: add a question about re-posting frequency Date: Tue, 29 Mar 2022 21:25:00 -0700 Message-Id: <20220330042505.2902770-10-kuba@kernel.org> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20220330042505.2902770-1-kuba@kernel.org> References: <20220330042505.2902770-1-kuba@kernel.org> MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org X-Patchwork-Delegate: kuba@kernel.org We have to tell people to stop reposting to often lately, or not to repost while the discussion is ongoing. Document this. Reviewed-by: Andrew Lunn Signed-off-by: Jakub Kicinski Reviewed-by: Florian Fainelli --- Documentation/networking/netdev-FAQ.rst | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/Documentation/networking/netdev-FAQ.rst b/Documentation/networking/netdev-FAQ.rst index 9c455d08510d..f8b89dc81cab 100644 --- a/Documentation/networking/netdev-FAQ.rst +++ b/Documentation/networking/netdev-FAQ.rst @@ -140,6 +140,17 @@ No, please resend the entire patch series and make sure you do number your patches such that it is clear this is the latest and greatest set of patches that can be applied. +I have received review feedback, when should I post a revised version of the patches? +------------------------------------------------------------------------------------- +Allow at least 24 hours to pass between postings. This will ensure reviewers +from all geographical locations have a chance to chime in. Do not wait +too long (weeks) between postings either as it will make it harder for reviewers +to recall all the context. + +Make sure you address all the feedback in your new posting. Do not post a new +version of the code if the discussion about the previous version is still +ongoing, unless directly instructed by a reviewer. + I submitted multiple versions of a patch series and it looks like a version other than the last one has been accepted, what should I do? ---------------------------------------------------------------------------------------------------------------------------------------- There is no revert possible, once it is pushed out, it stays like that. From patchwork Wed Mar 30 04:25:01 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jakub Kicinski X-Patchwork-Id: 12795429 X-Patchwork-Delegate: kuba@kernel.org Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7A43DC4332F for ; Wed, 30 Mar 2022 04:25:33 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242558AbiC3E1O (ORCPT ); Wed, 30 Mar 2022 00:27:14 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39390 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242524AbiC3E1C (ORCPT ); Wed, 30 Mar 2022 00:27:02 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 12053DF6A; Tue, 29 Mar 2022 21:25:18 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 9D32761515; Wed, 30 Mar 2022 04:25:17 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 9BECFC340EE; Wed, 30 Mar 2022 04:25:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1648614317; bh=K61ZB8eL6+rIPGneJi8e6vZ8cd5Fs9s7rksmt7GGVNs=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=aAYswTubeEK+kZkY2wp9k+iqcR2Q/2P/C6oP4A6gw2ptcWg3Hknv2zNiS2dh/Imkq f9thuehkd9RFPKeb6U6XSryVwInkluDLy67SZ5+vTKOP+dEcAKjIuPcdLlFVrAcuh8 KtoRd2wFbNgbb30DJOzpVlTrCnuCenDq7U64CrRL2n/lT/MvzLaH1iPrENxPDFd5cE nfHC1D6RblzAf3EvUQDsB9kLQj4KFpfQluYP11Z36F5vXPJ10NQ/7+cbcq4IoYODHO WT3iOJ1rpOewbcU8JDzVKxM95zuxW8KkrLYYbsVAGNi9lwEEUaBvxAhCWDBR8NRcMX m387O7qrLs4uQ== From: Jakub Kicinski To: davem@davemloft.net Cc: netdev@vger.kernel.org, pabeni@redhat.com, corbet@lwn.net, bpf@vger.kernel.org, linux-doc@vger.kernel.org, andrew@lunn.ch, f.fainelli@gmail.com, Jakub Kicinski Subject: [PATCH net v3 10/14] docs: netdev: make the testing requirement more stringent Date: Tue, 29 Mar 2022 21:25:01 -0700 Message-Id: <20220330042505.2902770-11-kuba@kernel.org> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20220330042505.2902770-1-kuba@kernel.org> References: <20220330042505.2902770-1-kuba@kernel.org> MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org X-Patchwork-Delegate: kuba@kernel.org These days we often ask for selftests so let's update our testing requirements. Signed-off-by: Jakub Kicinski Reviewed-by: Florian Fainelli --- Documentation/networking/netdev-FAQ.rst | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/Documentation/networking/netdev-FAQ.rst b/Documentation/networking/netdev-FAQ.rst index f8b89dc81cab..1388f78cfbc5 100644 --- a/Documentation/networking/netdev-FAQ.rst +++ b/Documentation/networking/netdev-FAQ.rst @@ -196,11 +196,15 @@ as possible alternative mechanisms. What level of testing is expected before I submit my change? ------------------------------------------------------------ -If your changes are against ``net-next``, the expectation is that you -have tested by layering your changes on top of ``net-next``. Ideally -you will have done run-time testing specific to your change, but at a -minimum, your changes should survive an ``allyesconfig`` and an -``allmodconfig`` build without new warnings or failures. +At the very minimum your changes must survive an ``allyesconfig`` and an +``allmodconfig`` build with ``W=1`` set without new warnings or failures. + +Ideally you will have done run-time testing specific to your change, +and the patch series contains a set of kernel selftest for +``tools/testing/selftests/net`` or using the KUnit framework. + +You are expected to test your changes on top of the relevant networking +tree (``net`` or ``net-next``) and not e.g. a stable tree or ``linux-next``. How do I post corresponding changes to user space components? ------------------------------------------------------------- From patchwork Wed Mar 30 04:25:02 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jakub Kicinski X-Patchwork-Id: 12795435 X-Patchwork-Delegate: kuba@kernel.org Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 87536C433EF for ; Wed, 30 Mar 2022 04:25:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242536AbiC3E1Z (ORCPT ); Wed, 30 Mar 2022 00:27:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39778 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242545AbiC3E1L (ORCPT ); Wed, 30 Mar 2022 00:27:11 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7B5B3E0A6; Tue, 29 Mar 2022 21:25:20 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id D76FAB81B34; Wed, 30 Mar 2022 04:25:18 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 32B54C34112; Wed, 30 Mar 2022 04:25:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1648614317; bh=HuGkOYeCEuEsc3HuodeCEqEow7DthokmDdOaxcQStg4=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=upUEvqpOhTiPhi0lu00Lx2Bc17BPACsqQY00D9GNEUQQzkPNoC8NNGYFR93Q8xg7D p4eYwqbP6DkzVQYqHjRKU07ghoc2t39R5cbmtGnoWOo5JETB7FlGhNn+AqJ75q0sV/ CXtok/DQPf3fLv3pNHgga4yGdRgwaMyeRKII8UxcngKTAJvw/qRgvcZBUx9XkVEsLZ BNBxtwrQc+HdGr6NnnT8xjEYfz13xERuQLcPTYHK/VWKOf9bJeXq2FOub97NA1D5FD obGgv6VNnvLueaDg+2Zu2I+xSbGagufu/3WCPu2bsRT+pDE6jXWXDVjr+VbipdEU5W N+YvvZ3vxsBmw== From: Jakub Kicinski To: davem@davemloft.net Cc: netdev@vger.kernel.org, pabeni@redhat.com, corbet@lwn.net, bpf@vger.kernel.org, linux-doc@vger.kernel.org, andrew@lunn.ch, f.fainelli@gmail.com, Jakub Kicinski Subject: [PATCH net v3 11/14] docs: netdev: add missing back ticks Date: Tue, 29 Mar 2022 21:25:02 -0700 Message-Id: <20220330042505.2902770-12-kuba@kernel.org> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20220330042505.2902770-1-kuba@kernel.org> References: <20220330042505.2902770-1-kuba@kernel.org> MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org X-Patchwork-Delegate: kuba@kernel.org I think double back ticks are more correct. Add where they are missing. Signed-off-by: Jakub Kicinski Reviewed-by: Florian Fainelli --- Documentation/networking/netdev-FAQ.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/Documentation/networking/netdev-FAQ.rst b/Documentation/networking/netdev-FAQ.rst index 1388f78cfbc5..294ad9b0162d 100644 --- a/Documentation/networking/netdev-FAQ.rst +++ b/Documentation/networking/netdev-FAQ.rst @@ -218,7 +218,7 @@ or the user space project is not reviewed on netdev include a link to a public repo where user space patches can be seen. In case user space tooling lives in a separate repository but is -reviewed on netdev (e.g. patches to `iproute2` tools) kernel and +reviewed on netdev (e.g. patches to ``iproute2`` tools) kernel and user space patches should form separate series (threads) when posted to the mailing list, e.g.:: @@ -251,18 +251,18 @@ traffic if we can help it. netdevsim is great, can I extend it for my out-of-tree tests? ------------------------------------------------------------- -No, `netdevsim` is a test vehicle solely for upstream tests. -(Please add your tests under tools/testing/selftests/.) +No, ``netdevsim`` is a test vehicle solely for upstream tests. +(Please add your tests under ``tools/testing/selftests/``.) -We also give no guarantees that `netdevsim` won't change in the future +We also give no guarantees that ``netdevsim`` won't change in the future in a way which would break what would normally be considered uAPI. Is netdevsim considered a "user" of an API? ------------------------------------------- Linux kernel has a long standing rule that no API should be added unless -it has a real, in-tree user. Mock-ups and tests based on `netdevsim` are -strongly encouraged when adding new APIs, but `netdevsim` in itself +it has a real, in-tree user. Mock-ups and tests based on ``netdevsim`` are +strongly encouraged when adding new APIs, but ``netdevsim`` in itself is **not** considered a use case/user. Any other tips to help ensure my net/net-next patch gets OK'd? From patchwork Wed Mar 30 04:25:03 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jakub Kicinski X-Patchwork-Id: 12795433 X-Patchwork-Delegate: kuba@kernel.org Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id AF60DC433F5 for ; Wed, 30 Mar 2022 04:25:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242535AbiC3E1W (ORCPT ); Wed, 30 Mar 2022 00:27:22 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39476 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242528AbiC3E1D (ORCPT ); Wed, 30 Mar 2022 00:27:03 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BF474DFE2; Tue, 29 Mar 2022 21:25:18 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 4C1F76154F; Wed, 30 Mar 2022 04:25:18 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id B5E42C340EE; Wed, 30 Mar 2022 04:25:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1648614318; bh=v9JEe17Ci9gU/r2Rz9f+Qliuq1qdflaeXctdUD+BZRQ=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=Dh+aT2bA3VJmbtRkZ8dnSWnm6etD8gGnn2FTfr+tf+izAcRBg8GQWPvA79fx40Xw8 aTPJFEmxUTKV8CAznAsgYrFuIYfh1FEI64P4TQNEocMy8taoRcf+iML5DKO7AJsyr/ hOTIu2OONrkTjH5Aq4HsktYfdIqMNJkYm55X0cbUwhbBMg1D50XmWIlm3K15OKz32B 1kwSKcxjj/k9K4BWXAbWWLllbLRpt0Z+SJW4Rw5EUYFRbK/DUYekGFw/zNs15Hm2oC Ni97ojnQbPqk99Q/YzsWzHVfAmFaV4buyrnVlSzvhZeBikxKvsn+dHoh4jxWwTclx3 Iw4bwjoSlvw8g== From: Jakub Kicinski To: davem@davemloft.net Cc: netdev@vger.kernel.org, pabeni@redhat.com, corbet@lwn.net, bpf@vger.kernel.org, linux-doc@vger.kernel.org, andrew@lunn.ch, f.fainelli@gmail.com, Jakub Kicinski Subject: [PATCH net v3 12/14] docs: netdev: call out the merge window in tag checking Date: Tue, 29 Mar 2022 21:25:03 -0700 Message-Id: <20220330042505.2902770-13-kuba@kernel.org> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20220330042505.2902770-1-kuba@kernel.org> References: <20220330042505.2902770-1-kuba@kernel.org> MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org X-Patchwork-Delegate: kuba@kernel.org Add the most important case to the question about "where are we in the cycle" - the case of net-next being closed. Signed-off-by: Jakub Kicinski Reviewed-by: Florian Fainelli --- Documentation/networking/netdev-FAQ.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Documentation/networking/netdev-FAQ.rst b/Documentation/networking/netdev-FAQ.rst index 294ad9b0162d..a18e4e671e85 100644 --- a/Documentation/networking/netdev-FAQ.rst +++ b/Documentation/networking/netdev-FAQ.rst @@ -103,7 +103,9 @@ So where are we now in this cycle? and note the top of the "tags" section. If it is rc1, it is early in the dev cycle. If it was tagged rc7 a week ago, then a release is -probably imminent. +probably imminent. If the most recent tag is a final release tag +(without an ``-rcN`` suffix) - we are most likely in a merge window +and ``net-next`` is closed. How can I tell the status of a patch I've sent? ----------------------------------------------- From patchwork Wed Mar 30 04:25:04 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jakub Kicinski X-Patchwork-Id: 12795434 X-Patchwork-Delegate: kuba@kernel.org Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9E9E4C433EF for ; Wed, 30 Mar 2022 04:25:42 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242595AbiC3E1Y (ORCPT ); Wed, 30 Mar 2022 00:27:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39728 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242536AbiC3E1K (ORCPT ); Wed, 30 Mar 2022 00:27:10 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4276DDFFE; Tue, 29 Mar 2022 21:25:19 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id D188C61552; Wed, 30 Mar 2022 04:25:18 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 485D3C34110; Wed, 30 Mar 2022 04:25:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1648614318; bh=RbzcFqOr0G6u+c1ZbQeSdrw2wYhqK0hXqhtZD8w4ywQ=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=oURXZ/feWZF+COAe5l4bLfI7dio89kk/NwTkI1z5UmT59/odmgNTK+myPa+tMMAyC l2o+zVAGDuhd+25OJVHtD/7yLolE359LFIJq7wIsvdD8OiCit7lqSbN/GZzzMHyKns 3Ux23KQc4LM9DvWOfms6F4RInPnT1c7/jRkybWbgEtOw+zrCGcwsgNwSqiWGjOq/OH Z6qQ8bFliYZqI+zYfY95spj0YpGGX/wSA83G1zBouQmWONMp8Jm+bWIk+QP3lyrZGp +9KyKERJUp0NwPSXwj2frGXyPhRavBdATQnIZuddh25Tmim1jRkztp9oalmWtz7tRv R0AM9qFGnESKQ== From: Jakub Kicinski To: davem@davemloft.net Cc: netdev@vger.kernel.org, pabeni@redhat.com, corbet@lwn.net, bpf@vger.kernel.org, linux-doc@vger.kernel.org, andrew@lunn.ch, f.fainelli@gmail.com, Jakub Kicinski Subject: [PATCH net v3 13/14] docs: netdev: broaden the new vs old code formatting guidelines Date: Tue, 29 Mar 2022 21:25:04 -0700 Message-Id: <20220330042505.2902770-14-kuba@kernel.org> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20220330042505.2902770-1-kuba@kernel.org> References: <20220330042505.2902770-1-kuba@kernel.org> MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org X-Patchwork-Delegate: kuba@kernel.org Convert the "should I use new or old comment formatting" to cover all formatting. This makes the question itself shorter. Signed-off-by: Jakub Kicinski Reviewed-by: Florian Fainelli --- Documentation/networking/netdev-FAQ.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Documentation/networking/netdev-FAQ.rst b/Documentation/networking/netdev-FAQ.rst index a18e4e671e85..c456b5225d66 100644 --- a/Documentation/networking/netdev-FAQ.rst +++ b/Documentation/networking/netdev-FAQ.rst @@ -183,10 +183,10 @@ Is the comment style convention different for the networking content? * another line of text */ -I am working in existing code that has the former comment style and not the latter. Should I submit new code in the former style or the latter? ------------------------------------------------------------------------------------------------------------------------------------------------ -Make it the latter style, so that eventually all code in the domain -of netdev is of this format. +I am working in existing code which uses non-standard formatting. Which formatting should I use? +------------------------------------------------------------------------------------------------ +Make your code follow the most recent guidelines, so that eventually all code +in the domain of netdev is in the preferred format. I found a bug that might have possible security implications or similar. Should I mail the main netdev maintainer off-list? --------------------------------------------------------------------------------------------------------------------------- From patchwork Wed Mar 30 04:25:05 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jakub Kicinski X-Patchwork-Id: 12795436 X-Patchwork-Delegate: kuba@kernel.org Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E5EDBC433F5 for ; Wed, 30 Mar 2022 04:25:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241116AbiC3E11 (ORCPT ); Wed, 30 Mar 2022 00:27:27 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39728 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242546AbiC3E1M (ORCPT ); Wed, 30 Mar 2022 00:27:12 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7B7A1E0B2; Tue, 29 Mar 2022 21:25:20 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id C1F6F61557; Wed, 30 Mar 2022 04:25:19 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id CB920C340EE; Wed, 30 Mar 2022 04:25:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1648614319; bh=rr/JfM01NA9fTgIIQTyL0hc+z3aaAIbMCzadjNz0JKg=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=F5oCGCMRhcZ6iJy2SN2x04M4PxF03Ww4fA1Xyis8ISwYMpR/RJ+S9qT3kpHx8K2+7 WCO2xOH96xt0L0goZGDm3kiP0MnMkEN5HQ4FCf2MsFYBiJQvbgEWSw8PFH/jmfs6Xu rfRL/1jhA8rYH75/0fzJ/NUUJ/1RJmdfbsBq/MaiviDD1TK6QSoSzyq/xk/MzAby1l EW7WBGUCq9FRr5j2rdlnWwZn+7U5S9AaMbnAab5FjYAGzlPHoxyIn4rUbR1eWvezfs BUR2nZmyxxx45XYrVDVpuZDhzIzWhiXM/YKA/9/upfo6uF33W2YC3dhFkXY+YBAyGX yVYjMtSBNAoeg== From: Jakub Kicinski To: davem@davemloft.net Cc: netdev@vger.kernel.org, pabeni@redhat.com, corbet@lwn.net, bpf@vger.kernel.org, linux-doc@vger.kernel.org, andrew@lunn.ch, f.fainelli@gmail.com, Jakub Kicinski Subject: [PATCH net v3 14/14] docs: netdev: move the netdev-FAQ to the process pages Date: Tue, 29 Mar 2022 21:25:05 -0700 Message-Id: <20220330042505.2902770-15-kuba@kernel.org> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20220330042505.2902770-1-kuba@kernel.org> References: <20220330042505.2902770-1-kuba@kernel.org> MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org X-Patchwork-Delegate: kuba@kernel.org The documentation for the tip tree is really in quite a similar spirit to the netdev-FAQ. Move the netdev-FAQ to the process docs as well. Signed-off-by: Jakub Kicinski Reviewed-by: Florian Fainelli --- Documentation/bpf/bpf_devel_QA.rst | 2 +- Documentation/networking/index.rst | 3 ++- Documentation/process/maintainer-handbooks.rst | 1 + .../netdev-FAQ.rst => process/maintainer-netdev.rst} | 0 MAINTAINERS | 1 + 5 files changed, 5 insertions(+), 2 deletions(-) rename Documentation/{networking/netdev-FAQ.rst => process/maintainer-netdev.rst} (100%) diff --git a/Documentation/bpf/bpf_devel_QA.rst b/Documentation/bpf/bpf_devel_QA.rst index 253496af8fef..761474bd7fe6 100644 --- a/Documentation/bpf/bpf_devel_QA.rst +++ b/Documentation/bpf/bpf_devel_QA.rst @@ -658,7 +658,7 @@ Otherwise, you can use ``bpf`` target. Additionally, you *must* use bpf target .. Links .. _Documentation/process/: https://www.kernel.org/doc/html/latest/process/ -.. _netdev-FAQ: ../networking/netdev-FAQ.rst +.. _netdev-FAQ: Documentation/process/maintainer-netdev.rst .. _selftests: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/testing/selftests/bpf/ .. _Documentation/dev-tools/kselftest.rst: diff --git a/Documentation/networking/index.rst b/Documentation/networking/index.rst index ce017136ab05..72cf33579b78 100644 --- a/Documentation/networking/index.rst +++ b/Documentation/networking/index.rst @@ -1,12 +1,13 @@ Linux Networking Documentation ============================== +Refer to :ref:`netdev-FAQ` for a guide on netdev development process specifics. + Contents: .. toctree:: :maxdepth: 2 - netdev-FAQ af_xdp bareudp batman-adv diff --git a/Documentation/process/maintainer-handbooks.rst b/Documentation/process/maintainer-handbooks.rst index 6af1abb0da48..d783060b4cc6 100644 --- a/Documentation/process/maintainer-handbooks.rst +++ b/Documentation/process/maintainer-handbooks.rst @@ -16,3 +16,4 @@ which is supplementary to the general development process handbook :maxdepth: 2 maintainer-tip + maintainer-netdev diff --git a/Documentation/networking/netdev-FAQ.rst b/Documentation/process/maintainer-netdev.rst similarity index 100% rename from Documentation/networking/netdev-FAQ.rst rename to Documentation/process/maintainer-netdev.rst diff --git a/MAINTAINERS b/MAINTAINERS index d91f6c6e3d3b..00dd58fc8bf3 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -13661,6 +13661,7 @@ B: mailto:netdev@vger.kernel.org T: git git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git T: git git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git F: Documentation/networking/ +F: Documentation/process/maintainer-netdev.rst F: include/linux/in.h F: include/linux/net.h F: include/linux/netdevice.h