Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: linus.luessing@c0d3.blue
Cc: netdev@vger.kernel.org, roopa@cumulusnetworks.com,
nikolay@cumulusnetworks.com, bridge@lists.linux-foundation.org,
gluon@luebeck.freifunk.net, openwrt-devel@lists.openwrt.org
Subject: Re: [RFC PATCH net-next] bridge: Implement MLD Querier wake-up calls / Android bug workaround
Date: Sun, 16 Aug 2020 21:10:02 -0700 (PDT) [thread overview]
Message-ID: <20200816.211002.1955628031429504263.davem@davemloft.net> (raw)
In-Reply-To: <20200816202424.3526-1-linus.luessing@c0d3.blue>
From: Linus Lüssing <linus.luessing@c0d3.blue>
Date: Sun, 16 Aug 2020 22:24:24 +0200
> I'm aware that this is quite a hack, so I'm unsure if this is suitable
> for upstream. On the other hand, the Android ticket isn't moving
> anywhere and even if it were fixed in Android, I'd expect it to take
> years until that fix would propagate or unpatched Android devices to
> vanish. So I'm wondering if it should be treated like a hardware bug
> workaround and by that should be suitable for applying it upstream in
> the Linux kernel?
Long after those Android devices are deprecated and no longer used, we
will still have this ugly hack in the tree.
Sorry, we're not doing this.
next prev parent reply other threads:[~2020-08-17 4:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-16 20:24 [RFC PATCH net-next] bridge: Implement MLD Querier wake-up calls / Android bug workaround Linus Lüssing
2020-08-16 22:08 ` [Bridge] " Stephen Hemminger
2020-08-16 22:10 ` David Miller
2020-08-23 15:42 ` Linus Lüssing
2020-08-23 17:19 ` Stephen Hemminger
2020-08-23 19:49 ` Felix Fietkau
2020-08-17 4:10 ` David Miller [this message]
2020-08-17 8:39 ` Bjørn Mork
2020-08-17 13:17 ` [gluon] " Sven Eckelmann
2020-08-17 13:35 ` Bjørn Mork
2020-08-17 14:24 ` Daniel Golle
2020-08-18 0:35 ` [bridge] fdde3c8b90: WARNING:at_net/core/rtnetlink.c:#rtnl_link_register kernel test robot
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=20200816.211002.1955628031429504263.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bridge@lists.linux-foundation.org \
--cc=gluon@luebeck.freifunk.net \
--cc=linus.luessing@c0d3.blue \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=openwrt-devel@lists.openwrt.org \
--cc=roopa@cumulusnetworks.com \
/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).