From: Jakub Kicinski <kuba@kernel.org>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
David Miller <davem@davemloft.net>,
Networking <netdev@vger.kernel.org>,
Benjamin Poirier <bpoirier@nvidia.com>,
Hangbin Liu <liuhangbin@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
MPTCP Upstream <mptcp@lists.linux.dev>
Subject: Re: linux-next: manual merge of the net-next tree with the net tree
Date: Thu, 22 Sep 2022 12:59:08 -0700 [thread overview]
Message-ID: <20220922125908.28efd4b4@kernel.org> (raw)
In-Reply-To: <2b4722a2-04cd-5e8f-ee09-c01c55aee7a7@tessares.net>
On Wed, 21 Sep 2022 11:18:17 +0200 Matthieu Baerts wrote:
> Hi Stephen,
>
> On 21/09/2022 03:04, Stephen Rothwell wrote:
> > Hi all,
> >
> > Today's linux-next merge of the net-next tree got a conflict in:
> >
> > tools/testing/selftests/drivers/net/bonding/Makefile
> >
> > between commit:
> >
> > bbb774d921e2 ("net: Add tests for bonding and team address list management")
> >
> > from the net tree and commit:
> >
> > 152e8ec77640 ("selftests/bonding: add a test for bonding lladdr target")
> >
> > from the net-next tree.
> >
> > I fixed it up (see below) and can carry the fix as necessary.
> Thank you for sharing this fix (and all the others!).
>
> I also had this conflict on my side[1] and I resolved it differently,
> more like what is done in the -net tree I think, please see the patch
> attached to this email.
>
> I guess I should probably use your version. It is just I saw it after
> having resolved the conflict on my side :)
> I will check later how the network maintainers will resolve this
> conflict and update my tree if needed.
I took this opportunity to sort 'em:
- TEST_PROGS := bond-break-lacpdu-tx.sh
- TEST_PROGS += bond-lladdr-target.sh
-TEST_PROGS := bond-break-lacpdu-tx.sh \
- dev_addr_lists.sh \
- bond-arp-interval-causes-panic.sh
++TEST_PROGS := \
++ bond-arp-interval-causes-panic.sh \
++ bond-break-lacpdu-tx.sh \
++ dev_addr_lists.sh
+
+ TEST_FILES := lag_lib.sh
Here's to hoping there are no more bond selftests before final..
next prev parent reply other threads:[~2022-09-22 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220921110437.5b7dbd82@canb.auug.org.au>
2022-09-21 9:18 ` linux-next: manual merge of the net-next tree with the net tree Matthieu Baerts
2022-09-22 19:59 ` Jakub Kicinski [this message]
2022-09-23 8:28 ` Matthieu Baerts
2022-09-23 12:25 ` Jakub Kicinski
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=20220922125908.28efd4b4@kernel.org \
--to=kuba@kernel.org \
--cc=bpoirier@nvidia.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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