From: Dominique Martinet <asmadeus@codewreck.org>
To: Andrew Lunn <andrew@lunn.ch>, Jakub Kicinski <kuba@kernel.org>
Cc: netdev <netdev@vger.kernel.org>,
Eric Van Hensbergen <ericvh@gmail.com>,
Latchesar Ionkov <lucho@ionkov.net>,
v9fs-developer@lists.sourceforge.net
Subject: Re: [PATCH net-next] net: 9p: Fix kerneldoc warnings of missing parameters etc
Date: Sun, 1 Nov 2020 17:08:25 +0100 [thread overview]
Message-ID: <20201101160825.GB5153@nautica> (raw)
In-Reply-To: <20201101155405.GA1109407@lunn.ch>
Andrew Lunn wrote on Sun, Nov 01, 2020:
> > > Signed-off-by: Andrew Lunn <andrew@lunn.ch>
Acked-by: Dominique Martinet <asmadeus@codewreck.org>
> >
> > 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
next prev parent reply other threads:[~2020-11-01 16:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-31 18:26 [PATCH net-next] net: 9p: Fix kerneldoc warnings of missing parameters etc Andrew Lunn
2020-10-31 20:58 ` Dominique Martinet
2020-11-01 15:54 ` Andrew Lunn
2020-11-01 16:08 ` Dominique Martinet [this message]
2020-11-02 20:27 ` Jakub Kicinski
2020-11-02 20:30 ` patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201101160825.GB5153@nautica \
--to=asmadeus@codewreck.org \
--cc=andrew@lunn.ch \
--cc=ericvh@gmail.com \
--cc=kuba@kernel.org \
--cc=lucho@ionkov.net \
--cc=netdev@vger.kernel.org \
--cc=v9fs-developer@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).