From: Jakub Kicinski <kuba@kernel.org>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: cgel.zte@gmail.com, mathew.j.martineau@linux.intel.com,
davem@davemloft.net, shuah@kernel.org, netdev@vger.kernel.org,
mptcp@lists.linux.dev, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, Ye Guojin <ye.guojin@zte.com.cn>,
ZealRobot <zealci@zte.com.cn>
Subject: Re: [PATCH] selftests: mptcp: remove duplicate include in mptcp_inq.c
Date: Fri, 10 Dec 2021 07:57:01 -0800 [thread overview]
Message-ID: <20211210075701.06bfced2@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <b6c19c9c-de6c-225c-5899-789dfd8e7ae8@tessares.net>
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.
next prev parent reply other threads:[~2021-12-10 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 7:14 [PATCH] selftests: mptcp: remove duplicate include in mptcp_inq.c cgel.zte
2021-12-10 9:58 ` Matthieu Baerts
2021-12-10 14:54 ` Jakub Kicinski
2021-12-10 14:56 ` Jakub Kicinski
2021-12-10 15:36 ` Matthieu Baerts
2021-12-10 15:57 ` Jakub Kicinski [this message]
2021-12-10 18:00 ` Mat Martineau
2021-12-10 19:10 ` 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=20211210075701.06bfced2@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
--to=kuba@kernel.org \
--cc=cgel.zte@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mathew.j.martineau@linux.intel.com \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=ye.guojin@zte.com.cn \
--cc=zealci@zte.com.cn \
/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).