From: Jakub Kicinski <kuba@kernel.org>
To: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
Andrew Lunn <andrew@lunn.ch>,
Ross Maynard <bids.7405@bigpond.com>,
Dave Jones <davej@codemonkey.org.uk>,
Bagas Sanjaya <bagasdotme@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Networking <netdev@vger.kernel.org>,
Linux USB <linux-usb@vger.kernel.org>,
Oliver Neukum <oneukum@suse.com>
Subject: Re: 3 more broken Zaurii - SL-5600, A300, C700
Date: Mon, 10 Jul 2023 09:55:19 -0700 [thread overview]
Message-ID: <20230710095519.5056c98b@kernel.org> (raw)
In-Reply-To: <ac957af4-f265-3ba0-0373-3a71d134a57e@leemhuis.info>
On Sun, 9 Jul 2023 06:36:32 +0200 Linux regression tracking (Thorsten
Leemhuis) wrote:
> To chime in here: I most agree, but FWIW, it broke more than a decade
> ago in v3.0, so maybe this is better suited for net-next. But of course
> that up to the -net maintainers.
I'm surprised to see you suggest -next for a fix to a user reported bug.
IMO it's very firmly net material.
next prev parent reply other threads:[~2023-07-10 16:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 2:09 Fwd: 3 more broken Zaurii - SL-5600, A300, C700 Bagas Sanjaya
2023-07-06 3:08 ` Bagas Sanjaya
2023-07-06 11:45 ` Thorsten Leemhuis
2023-07-06 16:41 ` Dave Jones
2023-07-07 12:28 ` Ross Maynard
2023-07-08 12:17 ` Ross Maynard
2023-07-08 20:49 ` Andrew Lunn
2023-07-09 4:36 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-10 16:55 ` Jakub Kicinski [this message]
2023-07-10 17:09 ` Linux regression tracking (Thorsten Leemhuis)
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=20230710095519.5056c98b@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=bagasdotme@gmail.com \
--cc=bids.7405@bigpond.com \
--cc=davej@codemonkey.org.uk \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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).