linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kyle Sanderson <kyle.leet@gmail.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	torvalds@linux-foundation.org, stable@vger.kernel.org,
	lwn@lwn.net, jslaby@suse.cz
Subject: Re: [REGRESSION] - BROKEN NETWORKING Re: Linux 6.16.3
Date: Mon, 25 Aug 2025 09:29:05 +0200	[thread overview]
Message-ID: <2025082553-overripe-sanction-bc82@gregkh> (raw)
In-Reply-To: <2025082529-reporter-frays-73a5@gregkh>

On Mon, Aug 25, 2025 at 09:00:14AM +0200, Greg Kroah-Hartman wrote:
> On Sun, Aug 24, 2025 at 11:31:01AM -0700, Kyle Sanderson wrote:
> > On 8/23/2025 7:51 AM, Greg Kroah-Hartman wrote:
> > > I'm announcing the release of the 6.16.3 kernel.
> > > 
> > > All users of the 6.16 kernel series that use the ext4 filesystem should
> > > upgrade.
> > > 
> > > The updated 6.16.y git tree can be found at:
> > > 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-6.16.y
> > > and can be browsed at the normal kernel.org git web browser:
> > > 	https://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
> > > 
> > > thanks,
> > > 
> > > greg k-h
> > 
> > Hi Greg,
> > 
> > Thanks for maintaining these as always. For the first time in a long time, I
> > booted the latest stable (6.15.x -> 6.16.3) and somehow lost my networking.
> > It looks like there is a patch from Intel (reported by AMD) that did not
> > make it into stable 6.16.
> > 
> > e67a0bc3ed4fd8ee1697cb6d937e2b294ec13b5e - ixgbe
> > https://lore.kernel.org/all/94d7d5c0bb4fc171154ccff36e85261a9f186923.1755661118.git.calvin@wbinvd.org/
> > - i40e
> 
> Any specific reason why this hasn't been asked to be backported to
> stable trees if it fixes an issue?   Please cc: the developers involved
> so that they know to let us pick it up.

I've picked it up now, simple enough.

  reply	other threads:[~2025-08-25  7:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-23 14:51 Linux 6.16.3 Greg Kroah-Hartman
2025-08-23 14:51 ` Greg Kroah-Hartman
2025-08-24 18:31 ` [REGRESSION] - BROKEN NETWORKING " Kyle Sanderson
2025-08-24 18:55   ` Willy Tarreau
2025-08-24 19:29     ` Calvin Owens
2025-08-24 19:51       ` Kyle Sanderson
2025-08-25  7:00   ` Greg Kroah-Hartman
2025-08-25  7:29     ` Greg Kroah-Hartman [this message]
2025-08-25  7:30       ` Greg Kroah-Hartman

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=2025082553-overripe-sanction-bc82@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=jslaby@suse.cz \
    --cc=kyle.leet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwn@lwn.net \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 NNTP newsgroup(s).