From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Saravana Kannan <saravanak@google.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>, "JC Kuo" <jckuo@nvidia.com>,
"Vinod Koul" <vkoul@kernel.org>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Jonathan Hunter" <jonathanh@nvidia.com>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
kernel-team@android.com, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-phy@lists.infradead.org,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 0/3] A few minor fw_devlink fixes
Date: Thu, 24 Oct 2024 09:08:06 +0200 [thread overview]
Message-ID: <2024102457-manager-counting-ff68@gregkh> (raw)
In-Reply-To: <20241024061347.1771063-1-saravanak@google.com>
On Wed, Oct 23, 2024 at 11:13:41PM -0700, Saravana Kannan wrote:
> Probably easiest for Greg to pull in these changes?
>
> PSA: Do not pull any of these patches into stable kernels. fw_devlink
> had a lot of changes that landed in the last year. It's hard to ensure
> cherry-picks have picked up all the dependencies correctly. If any of
> these really need to get cherry-picked into stable kernels, cc me and
> wait for my explicit Ack.
You can do that with the correct tag in the commit as per the stable
documentation if you really want to :)
But why would these not be able to go backwards? What changed to
require them now and not be ok for older kernels?
thanks,
greg k-h
next prev parent reply other threads:[~2024-10-24 7:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 6:13 [PATCH 0/3] A few minor fw_devlink fixes Saravana Kannan
2024-10-24 6:13 ` [PATCH 1/3] drm: display: Set fwnode for aux bus devices Saravana Kannan
2024-10-24 17:27 ` Thierry Reding
2024-10-25 0:22 ` Dmitry Baryshkov
2024-10-24 6:13 ` [PATCH 2/3] phy: tegra: xusb: Set fwnode for xusb port devices Saravana Kannan
2024-10-24 17:27 ` Thierry Reding
2024-10-24 6:13 ` [PATCH 3/3] drivers: core: fw_devlink: Make the error message a bit more useful Saravana Kannan
2024-10-24 6:16 ` Saravana Kannan
2024-10-24 7:06 ` Greg Kroah-Hartman
2024-10-24 7:08 ` Greg Kroah-Hartman [this message]
2024-10-24 16:45 ` [PATCH 0/3] A few minor fw_devlink fixes Saravana Kannan
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=2024102457-manager-counting-ff68@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=airlied@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jckuo@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=kernel-team@android.com \
--cc=kishon@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthias.bgg@gmail.com \
--cc=mripard@kernel.org \
--cc=nfraprado@collabora.com \
--cc=rafael@kernel.org \
--cc=saravanak@google.com \
--cc=simona@ffwll.ch \
--cc=thierry.reding@gmail.com \
--cc=tzimmermann@suse.de \
--cc=vkoul@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 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).