From: Kalle Valo <kvalo@codeaurora.org>
To: Andreas Born <futur.andy@googlemail.com>
Cc: Arend van Spriel <arend.vanspriel@broadcom.com>,
Mahesh Bandewar <maheshb@google.com>,
Andy Gospodarek <andy@greyhouse.net>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
James Feeney <james@nurealm.net>
Subject: Re: Regression: Bug 196547 - Since 4.12 - bonding module not working with wireless drivers
Date: Fri, 11 Aug 2017 16:14:48 +0300 [thread overview]
Message-ID: <87tw1edz5j.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CADps9UA7S2betC-+5sOXjYWmDC8gnk6JJ9aEueEOoYAC3DU8hg@mail.gmail.com> (Andreas Born's message of "Thu, 10 Aug 2017 19:52:03 +0200")
Andreas Born <futur.andy@googlemail.com> writes:
> Earlier today I submitted the patch (bonding: require speed/duplex
> only for 802.3ad, alb and tlb) [2] that only partially reverts what is
> a regression following my aforementioned logic. This seems to me like
> the best solution in the short term since it should satisfy both
> usergroups represented by Mahesh and James and restores consistence
> with the bonding documentation. James already commented approvingly on
> that patch in the bug report. [3]
>
> Regards
> Andreas
>
> [1]
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/networking/bonding.txt
Great, thanks.
I'll take it the patch is meant for net tree (and not net-next) so that
it will be fixed for v4.13? Also it should backported to v4.12 stable
tree. I don't see any mention of that in the patch submission and that's
why I'm asking.
--
Kalle Valo
next prev parent reply other threads:[~2017-08-11 13:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 5:39 Regression: Bug 196547 - Since 4.12 - bonding module not working with wireless drivers Kalle Valo
2017-08-10 12:43 ` Arend van Spriel
2017-08-10 17:52 ` Andreas Born
2017-08-11 13:14 ` Kalle Valo [this message]
2017-08-12 7:35 ` Kalle Valo
2017-08-12 19:30 ` James Feeney
2017-08-13 17:42 ` Andreas Born
2017-08-16 20:44 ` James Feeney
2017-08-16 21:01 ` David Miller
2017-08-16 21:22 ` Dan Williams
2017-08-16 21:31 ` David Miller
2017-08-17 2:11 ` Dan Williams
2017-08-17 2:36 ` Ben Greear
2017-08-17 3:18 ` Dan Williams
2017-08-17 3:32 ` Ben Greear
2017-08-17 2:42 ` David Miller
2017-08-17 5:33 ` Jay Vosburgh
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=87tw1edz5j.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=andy@greyhouse.net \
--cc=arend.vanspriel@broadcom.com \
--cc=davem@davemloft.net \
--cc=futur.andy@googlemail.com \
--cc=james@nurealm.net \
--cc=linux-wireless@vger.kernel.org \
--cc=maheshb@google.com \
--cc=netdev@vger.kernel.org \
/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).