From: Sasha Neftin <sasha.neftin@intel.com>
To: "Jérôme Carretero" <cJ-ko@zougloub.eu>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: <netdev@vger.kernel.org>, <intel-wired-lan@lists.osuosl.org>,
<linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>,
"Lifshits, Vitaly" <vitaly.lifshits@intel.com>,
"Meir, NaamaX" <naamax.meir@intel.com>,
naamax.meir <naamax.meir@linux.intel.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>
Subject: Re: [Intel-wired-lan] [BUG] e1000e, scheduling while atomic (stable)
Date: Sat, 20 Apr 2024 19:17:52 +0300 [thread overview]
Message-ID: <0e428380-a3b1-4930-b4de-2b13e7185647@intel.com> (raw)
In-Reply-To: <2259bbeb9a012548779e3bf09a393fdb7d62dd0c.camel@zougloub.eu>
On 19/04/2024 19:20, 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.
>
>
> Tested-by: Jérôme Carretero <cJ-ko@zougloub.eu>
Hello Jérôme,
Can you put your "Tested-by:" tag under
https://patchwork.ozlabs.org/project/intel-wired-lan/patch/20240417190320.3159360-1-vitaly.lifshits@intel.com/
?
(then we will forward it via fixes, hopefully v6.9 candidate will pick
up it)
Thanks,
Sasha
>
>
> Best regards,
>
next prev parent reply other threads:[~2024-04-20 16:18 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 [this message]
2024-04-23 16:23 ` Greg Kroah-Hartman
2024-04-25 6:06 ` Sasha Neftin
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=0e428380-a3b1-4930-b4de-2b13e7185647@intel.com \
--to=sasha.neftin@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=cJ-ko@zougloub.eu \
--cc=gregkh@linuxfoundation.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naamax.meir@intel.com \
--cc=naamax.meir@linux.intel.com \
--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
all inboxes | Powered by JetHome®