All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Wongi Lee <qw3rtyp0@gmail.com>
Cc: stable@vger.kernel.org, Sasha Levin <sashal@kernel.org>,
	netdev@vger.kernel.org, David Ahern <dsahern@kernel.org>,
	Ido Schimmel <idosch@nvidia.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>,
	Jungwoo Lee <jwlee2217@gmail.com>
Subject: Re: Please apply 736b380e28d0 and eca856950f7c down to 6.1.y
Date: Wed, 24 Jun 2026 11:37:29 +0200	[thread overview]
Message-ID: <2026062416-amulet-paradox-cf7c@gregkh> (raw)
In-Reply-To: <ajujm9+82N1g/HgF@DESKTOP-19IMU7U.localdomain>

On Wed, Jun 24, 2026 at 06:30:03PM +0900, Wongi Lee wrote:
> On Wed, Jun 24, 2026 at 11:00:45AM +0200, Greg Kroah-Hartman wrote:
> > On Wed, Jun 24, 2026 at 05:14:38PM +0900, Wongi Lee wrote:
> > > Hi,
> > > 
> > > Could the following upstream commits be queued for the active stable
> > > trees?
> > > 
> > >   commit 736b380e28d0480c7bc3e022f1950f31fe53a7c5
> > >   ("ipv6: account for fraggap on the paged allocation path")
> > 
> > I do not see that commit id in Linus's tree, are you sure it is correct?
> > 
> > >   commit eca856950f7cb1a221e02b99d758409f2c5cec42
> > >   ("ipv4: account for fraggap on the paged allocation path")
> > 
> > Same here, no id of that one in Linus's tree that I can see.
> > 
> > thanks,
> > 
> > greg k-h
> 
> 
> Hi Greg,
> 
> First, sorry for confusing you.
> 
> The commit IDs are from netdev/net.git:
> 
>   736b380e28d0480c7bc3e022f1950f31fe53a7c5
>   https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=736b380e28d0
> 
>   eca856950f7cb1a221e02b99d758409f2c5cec42
>   https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=eca856950f7c
> 
> They were applied to netdev without Cc: stable@vger.kernel.org, so I
> wanted to flag them for stable handling but I send it too fast (before
> merge).
> 
> I will resend the request with the Linus tree commit ID.

They have to be in Linus's tree, before we can take them in a stable
release, right?

And why were they not originally tagged with the cc: stable?  That would
save you time in the future as it would all just happen automatically.

thanks,

greg k-h

  reply	other threads:[~2026-06-24  9:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-24  8:14 Please apply 736b380e28d0 and eca856950f7c down to 6.1.y Wongi Lee
2026-06-24  9:00 ` Greg Kroah-Hartman
2026-06-24  9:30   ` Wongi Lee
2026-06-24  9:37     ` Greg Kroah-Hartman [this message]
2026-06-24  9:44       ` Wongi Lee

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=2026062416-amulet-paradox-cf7c@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=jwlee2217@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=qw3rtyp0@gmail.com \
    --cc=sashal@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 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.