From: Linus Torvalds <torvalds@linux-foundation.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: Jakub Kicinski <kuba@kernel.org>,
Johannes Berg <johannes@sipsolutions.net>,
davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, pabeni@redhat.com,
bpf@vger.kernel.org, ast@kernel.org
Subject: Re: [PULL] Networking for v6.3
Date: Thu, 23 Feb 2023 13:37:31 -0800 [thread overview]
Message-ID: <CAHk-=wgOmTXMxm=ouCEKu0Agd5q-u3mrQ8=ne8412ciG2b-eJA@mail.gmail.com> (raw)
In-Reply-To: <87pma02odj.fsf@kernel.org>
On Thu, Feb 23, 2023 at 11:06 AM Kalle Valo <kvalo@kernel.org> wrote:
>
> So that we can file a bug report about use of Wireless Extensions, what
> process is ThreadPoolForeg?
It is, as you already seem to have googled, just a sub-thread of google-chrome.
> The warning was applied over a month ago, I'm surprised nobody
> else has reported anything.
Honestly, I'm not sure how many people actually _run_ a real desktop
on linux-next. Getting merged into mainline really ends up resulting
in a lot more testing (outside of the test robots that don't tend to
really run desktop loads).
I see it on my desktop too, but I actually noticed it on my laptop
first, because it - once again - has started falling off the wireless
network regularly and I was looking if there were any messages about
it.
(That ath driver really is flaky, and I've never figured out what the
trigger is, it just sometimes goes dead and you have to disable and
re-enable wireless. But that's not a new problem, it's just a "that's
why I noticed")
Linus
prev parent reply other threads:[~2023-02-23 21:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 23:38 [PULL] Networking for v6.3 Jakub Kicinski
2023-02-22 2:46 ` Linus Torvalds
2023-02-22 3:33 ` Jakub Kicinski
2023-02-22 19:07 ` Alexander Lobakin
2023-02-22 2:50 ` pr-tracker-bot
2023-02-23 17:21 ` Linus Torvalds
2023-02-23 19:06 ` Kalle Valo
2023-02-23 21:37 ` Linus Torvalds [this message]
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='CAHk-=wgOmTXMxm=ouCEKu0Agd5q-u3mrQ8=ne8412ciG2b-eJA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).