All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Стас Ничипорович" <stasn77@gmail.com>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.6 000/326] 6.6.16-rc2 review
Date: Sun, 4 Feb 2024 17:25:06 -0800	[thread overview]
Message-ID: <2024020433-universal-resolute-024d@gregkh> (raw)
In-Reply-To: <CAH37n11Tr9_2A=nFG7N8gi9DoC0ZdEQBGH3herTuP+C-s+3isg@mail.gmail.com>

On Mon, Feb 05, 2024 at 01:08:47AM +0300, Стас Ничипорович wrote:
> I meant that there is no place for the patch in the stable branch
> until fix. In 6.6.15 there is no issue.

I understand, but again, please work with the networking developers to
get this fixed otherwise this will happen soon for newer kernels.

thanks,

greg k-h

  reply	other threads:[~2024-02-05  1:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-04  4:43 [PATCH 6.6 000/326] 6.6.16-rc2 review Стас Ничипорович
2024-02-04 12:49 ` Greg KH
2024-02-04 13:15   ` Стас Ничипорович
2024-02-04 14:13     ` Greg KH
2024-02-04 22:08       ` Стас Ничипорович
2024-02-05  1:25         ` Greg KH [this message]
2024-02-05  1:26           ` Greg KH
2024-02-07  7:04 ` Linux regression tracking (Thorsten Leemhuis)
2024-02-07 10:09   ` Greg KH
2024-02-07 10:22     ` Linux regression tracking (Thorsten Leemhuis)
  -- strict thread matches above, loose matches on Subject: below --
2024-02-03 17:52 Greg Kroah-Hartman
2024-02-03 19:51 ` SeongJae Park
2024-02-03 21:57 ` Florian Fainelli
2024-02-03 22:58 ` Takeshi Ogasawara
2024-02-04  6:51 ` Bagas Sanjaya
2024-02-04 17:04 ` Naresh Kamboju
2024-02-04 19:13 ` Justin Forbes
2024-02-04 21:27 ` Ron Economos
2024-02-05  9:46 ` Shreeya Patel
2024-02-05 13:18 ` Jon Hunter
2024-02-05 16:40 ` Allen

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=2024020433-universal-resolute-024d@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=stasn77@gmail.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 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.