All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>,
	Greg KH <gregkh@linuxfoundation.org>,
	"Artem S. Tashkinov" <aros@gmx.com>
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: Mon, 29 Apr 2024 10:13:08 -0700	[thread overview]
Message-ID: <95e3e9af-a7e7-732c-1e76-680765414ef1@intel.com> (raw)
In-Reply-To: <fd85f305-6540-4551-95c8-f75c9288f21a@leemhuis.info>

On 4/28/2024 1:01 AM, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 27.04.24 13:14, Greg KH wrote:
>> On Sat, Apr 27, 2024 at 10:54:23AM +0000, Artem S. Tashkinov wrote:
>>> This fix is still not queued in 6.8 stable:
>> What fix?
> 
> FWIW, this one:
> https://lore.kernel.org/all/20240417190320.3159360-1-vitaly.lifshits@intel.com/
> 
> But sadly the review is still pending (and hence it's not yet eligible
> for inclusion in stable afaics):
> https://lore.kernel.org/lkml/ded3e7ae-6a7d-48b2-8acc-c125874ee09f@leemhuis.info/

The team that deals with this driver had holidays last week so that 
delayed things a bit. I was able to touch base with them today and the 
patch has been sent to netdev.

https://lore.kernel.org/netdev/20240429171040.1152516-1-anthony.l.nguyen@intel.com/

Thanks,
Tony

> HTH, Ciao, Thorsten

WARNING: multiple messages have this Message-ID (diff)
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>,
	Greg KH <gregkh@linuxfoundation.org>,
	"Artem S. Tashkinov" <aros@gmx.com>
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: Mon, 29 Apr 2024 10:13:08 -0700	[thread overview]
Message-ID: <95e3e9af-a7e7-732c-1e76-680765414ef1@intel.com> (raw)
In-Reply-To: <fd85f305-6540-4551-95c8-f75c9288f21a@leemhuis.info>

On 4/28/2024 1:01 AM, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 27.04.24 13:14, Greg KH wrote:
>> On Sat, Apr 27, 2024 at 10:54:23AM +0000, Artem S. Tashkinov wrote:
>>> This fix is still not queued in 6.8 stable:
>> What fix?
> 
> FWIW, this one:
> https://lore.kernel.org/all/20240417190320.3159360-1-vitaly.lifshits@intel.com/
> 
> But sadly the review is still pending (and hence it's not yet eligible
> for inclusion in stable afaics):
> https://lore.kernel.org/lkml/ded3e7ae-6a7d-48b2-8acc-c125874ee09f@leemhuis.info/

The team that deals with this driver had holidays last week so that 
delayed things a bit. I was able to touch base with them today and the 
patch has been sent to netdev.

https://lore.kernel.org/netdev/20240429171040.1152516-1-anthony.l.nguyen@intel.com/

Thanks,
Tony

> HTH, Ciao, Thorsten

  reply	other threads:[~2024-04-29 17:13 UTC|newest]

Thread overview: 16+ 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-17 18:46 ` [Intel-wired-lan] " Jérôme Carretero
2024-04-18  3:44 ` Sasha Neftin
2024-04-18  3:44   ` 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-20 16:17       ` Sasha Neftin
2024-04-23 16:23     ` Greg Kroah-Hartman
2024-04-23 16:23       ` Greg Kroah-Hartman
2024-04-25  6:06       ` Sasha Neftin
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 [this message]
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=95e3e9af-a7e7-732c-1e76-680765414ef1@intel.com \
    --to=anthony.l.nguyen@intel.com \
    --cc=aros@gmx.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.