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.3 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 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 8DF15C2D0A3 for ; Sun, 1 Nov 2020 16:08:45 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 0D33D2222F for ; Sun, 1 Nov 2020 16:08:45 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=codewreck.org header.i=@codewreck.org header.b="OZFK98iM" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726989AbgKAQIo (ORCPT ); Sun, 1 Nov 2020 11:08:44 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40438 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726730AbgKAQIm (ORCPT ); Sun, 1 Nov 2020 11:08:42 -0500 Received: from nautica.notk.org (ipv6.notk.org [IPv6:2001:41d0:1:7a93::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 84231C0617A6 for ; Sun, 1 Nov 2020 08:08:42 -0800 (PST) Received: by nautica.notk.org (Postfix, from userid 1001) id 841CAC01B; Sun, 1 Nov 2020 17:08:40 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=codewreck.org; s=2; t=1604246920; bh=NAh4yRVnmCinK7IGx2ZG2mZVUNTtb4YsMwVS+qEAn0Q=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=OZFK98iMaWOnxh0jHh4eyyrYoGVPHBjyX9iJIFfhFINgalofOHgLQxxdt1Lafxz06 c4d7aiZdkQhLs+iJvgHkisdlvDVfJE9goszkvjh0C27SxjHTMywcpYZa9yAvA7rpyy v38dn78+6iaVY5270O5Tye35uHa6fXTXs85FFtX26Hty7X3Wzz7/6B+Qhai1iXz4uU DM1yT0lc8NwEwFyy9mX4Bw1DT+EOSGKwdIyBpZa9lO97H2qifHNazxl3BynrHpKCj5 pdELEyIZ/3IqYEvgXg3mFUiLjIC4jC4UBZafz5aJujmnqHXwNP8Vl+IvU5Ci+RqPp8 OmThf7DISjpBA== Date: Sun, 1 Nov 2020 17:08:25 +0100 From: Dominique Martinet To: Andrew Lunn , Jakub Kicinski Cc: netdev , Eric Van Hensbergen , Latchesar Ionkov , v9fs-developer@lists.sourceforge.net Subject: Re: [PATCH net-next] net: 9p: Fix kerneldoc warnings of missing parameters etc Message-ID: <20201101160825.GB5153@nautica> References: <20201031182655.1082065-1-andrew@lunn.ch> <20201031205813.GA624@nautica> <20201101155405.GA1109407@lunn.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20201101155405.GA1109407@lunn.ch> User-Agent: Mutt/1.5.21 (2010-09-15) Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Andrew Lunn wrote on Sun, Nov 01, 2020: > > > Signed-off-by: Andrew Lunn Acked-by: Dominique Martinet > > > > Thanks, LGTM I'll take this for next cycle unless someone is grabbing > > these > > I hope to turn on W=1 by default soon in most of /net. That patch is > likely to go to net-next. That would be nice! > What route do your patches normally take to Linus? Do you send a pull > request to net-next? Or straight to Linus? I normally send pull requests straight to Linus (because I also have fs/9p which isn't part of net/) ; but since it's really low volume I don't like bugging him everytime for such churn and am not really sure what to do -- that's why I asked :) > If this patch is not in net-next, i cannot enable it for 9p. So > either: > [...] > 4) Jakub takes this patch into net-next, and i can then enable W=1 in > 9p along with all the other sub-directories. We will get to know > about new warnings in net-next, and next, but not in your tree. Developers should use next for development anyway; I think that's the easiest way forward if you want to enable W=1 ASAP. I mean, if I take the patch the fixes will get in next in the next few days sure but it'll make enabling W=1 difficult for the net-next tree without it. I've added Jakub to direct recipients, could you take this one? Thanks, -- Dominique