From: "Artem S. Tashkinov" <aros@gmx.com>
To: gregkh@linuxfoundation.org
Cc: intel-wired-lan@lists.osuosl.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [Intel-wired-lan] [BUG] e1000e, scheduling while atomic (stable)
Date: Sat, 27 Apr 2024 10:54:23 +0000 [thread overview]
Message-ID: <2330c23c-e99b-454a-b195-32c5b4332071@gmx.com> (raw)
In-Reply-To: <2024042328-footprint-enrage-2db3@gregkh>
Hello,
This fix is still not queued in 6.8 stable:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-6.8
Why?
Regards,
Artem
next prev parent reply other threads:[~2024-04-27 10:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 18:46 [BUG] e1000e, scheduling while atomic Jérôme Carretero
2024-04-18 3:44 ` [Intel-wired-lan] " Sasha Neftin
2024-04-19 16:20 ` [Intel-wired-lan] [BUG] e1000e, scheduling while atomic (stable) Jérôme Carretero
2024-04-20 16:17 ` Sasha Neftin
2024-04-23 16:23 ` Greg Kroah-Hartman
2024-04-25 6:06 ` Sasha Neftin
2024-04-27 10:54 ` Artem S. Tashkinov [this message]
2024-04-27 11:14 ` Greg KH
2024-04-28 8:01 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-29 17:13 ` Tony Nguyen
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=2330c23c-e99b-454a-b195-32c5b4332071@gmx.com \
--to=aros@gmx.com \
--cc=gregkh@linuxfoundation.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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 read-only IMAP folder(s) and NNTP newsgroup(s).