All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Ming Wen <mwen@ambarella.com>, Rongrong Cao <rrcao@ambarella.com>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Cc: "mchehab@kernel.org" <mchehab@kernel.org>,
	Long Li <longli@ambarella.com>, Jian Tang <jtang@ambarella.com>,
	Zhao-Yang Chen <zychen@ambarella.com>
Subject: RE: [EXT] Re: [Kernel 5.15/Kernle 6.1] About Sphinx Doc.
Date: Wed, 07 May 2025 14:03:29 -0600	[thread overview]
Message-ID: <87v7qctcha.fsf@trenco.lwn.net> (raw)
In-Reply-To: <IA0PPF7478C2D3A5F61C0E93BF2EE5CA242DD88A@IA0PPF7478C2D3A.namprd19.prod.outlook.com>

Ming Wen <mwen@ambarella.com> writes:

> Hi Rongrong:
>  
> Thanks for the update. Good to know!
> As the next, Jon may help to check a bit why this changelist is missed to be merged into LTS Kernel 5.15 and even LTS Kernel 6.1. It should definitely be needed.😊

The stable maintainers need to be told to apply a patch like this, and
nobody did that.  I will try to have a look in the near future to decide
whether that should be done in this case...sorry, I'm on the road, and
have a few balls to juggle at the moment.

jon

  reply	other threads:[~2025-05-07 20:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <IA0PPF7478C2D3A237C6EE1AD359301D79BDD802@IA0PPF7478C2D3A.namprd19.prod.outlook.com>
2025-04-30 12:47 ` [Kernel 5.15/Kernle 6.1] About Sphinx Doc Jonathan Corbet
2025-04-30 13:47   ` [EXT] " Ming Wen
2025-04-30 14:05     ` Jonathan Corbet
2025-04-30 15:15       ` Ming Wen
2025-05-06 10:39         ` Ming Wen
2025-05-07 10:11           ` Rongrong Cao
2025-05-07 12:55             ` Ming Wen
2025-05-07 20:03               ` Jonathan Corbet [this message]
2025-05-07 20:19                 ` Rongrong Cao
2025-05-08  3:43                 ` Ming Wen
2025-06-04 20:53               ` Jonathan Corbet
2025-06-05  4:14                 ` Ming Wen

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=87v7qctcha.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=jtang@ambarella.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=longli@ambarella.com \
    --cc=mchehab@kernel.org \
    --cc=mwen@ambarella.com \
    --cc=rrcao@ambarella.com \
    --cc=zychen@ambarella.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.