[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20211210075701.06bfced2@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Fri, 10 Dec 2021 07:57:01 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Matthieu Baerts <matthieu.baerts@...sares.net>
Cc: cgel.zte@...il.com, mathew.j.martineau@...ux.intel.com,
davem@...emloft.net, shuah@...nel.org, netdev@...r.kernel.org,
mptcp@...ts.linux.dev, linux-kselftest@...r.kernel.org,
linux-kernel@...r.kernel.org, Ye Guojin <ye.guojin@....com.cn>,
ZealRobot <zealci@....com.cn>
Subject: Re: [PATCH] selftests: mptcp: remove duplicate include in
mptcp_inq.c
On Fri, 10 Dec 2021 16:36:06 +0100 Matthieu Baerts wrote:
> > Actually, I take that back, let's hear from Mat, he may want to take
> > the patch via his tree.
>
> We "rebase" our tree on top of net-next every night. I think for such
> small patches with no behaviour change and sent directly to netdev ML,
> it is probably best to apply them directly. I can check with Mat if it
> is an issue if you prefer.
Please do, I'm happy to apply the patch but Mat usually prefers to take
things thru MPTCP tree.
> I would have applied it in our MPTCP tree if we were sending PR, not to
> bother you for such patches but I guess it is best not to have us
> sending this patch a second time later :)
>
> BTW, if you prefer us sending PR over batches of patches, please tell us!
Small preference for patches. It's good to have the code on the ML for
everyone to look at and mixed PR + patches are a tiny bit more clicking
for me.
Powered by blists - more mailing lists