From: Sasha Neftin <sasha.neftin@intel.com>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jérôme Carretero" <cJ-ko@zougloub.eu>
Cc: <netdev@vger.kernel.org>, <intel-wired-lan@lists.osuosl.org>,
<linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>,
"Ruinskiy, Dima" <dima.ruinskiy@intel.com>,
"Lifshits, Vitaly" <vitaly.lifshits@intel.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>
Subject: Re: [Intel-wired-lan] [BUG] e1000e, scheduling while atomic (stable)
Date: Thu, 25 Apr 2024 09:06:16 +0300 [thread overview]
Message-ID: <a9b7f1fc-7b07-41e4-8957-876d428399be@intel.com> (raw)
In-Reply-To: <2024042328-footprint-enrage-2db3@gregkh>
On 23/04/2024 19:23, Greg Kroah-Hartman wrote:
> On Fri, Apr 19, 2024 at 12:20:05PM -0400, Jérôme Carretero wrote:
>> Hi Sasha,
>>
>>
>> Thank you, sorry for the delay but I coudln't reboot.
>>
>> Adding Greg KH because I don't know if stable will receive my e-mail
>> (not subscribed) but the regression was integrated in stable:
>> commit 0a4e3c2d976aa4dd38951afd6267f74ef3fade0e
>> so they should get the fix ASAP too.
>
> The fix needs to show up in Linus's tree, is it on its way there?
yes. Routed via intel-wired-lan:
https://patchwork.ozlabs.org/project/intel-wired-lan/patch/20240417190320.3159360-1-vitaly.lifshits@intel.com/
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2024-04-25 6:06 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 [this message]
2024-04-27 10:54 ` Artem S. Tashkinov
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=a9b7f1fc-7b07-41e4-8957-876d428399be@intel.com \
--to=sasha.neftin@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=cJ-ko@zougloub.eu \
--cc=dima.ruinskiy@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=vitaly.lifshits@intel.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 read-only IMAP folder(s) and NNTP newsgroup(s).