From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: linux-stable <stable@vger.kernel.org>,
lkft-triage@lists.linaro.org, Sasha Levin <sashal@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Cristian Marussi <cristian.marussi@arm.com>,
Bjorn Andersson <andersson@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Anders Roxell <anders.roxell@linaro.org>
Subject: Re: stable-rc: 5.15: arm: fsl_dcu_drm_plane.c:176:20: error: 'drm_plane_helper_destroy' undeclared here
Date: Wed, 9 Aug 2023 08:59:39 +0200 [thread overview]
Message-ID: <2023080946-wow-cross-1079@gregkh> (raw)
In-Reply-To: <CA+G9fYvTjm2oa6mXR=HUe6gYuVaS2nFb_otuvPfmPeKHDoC+Tw@mail.gmail.com>
On Wed, Aug 09, 2023 at 11:47:45AM +0530, Naresh Kamboju wrote:
> While building Linux stable rc 5.15 arm with gcc-13 failed due to
> following warnings / errors.
I appreciate you attempting to build older LTS trees with newer
compilers, but note that usually, as you are finding out, this doesn't
work.
Right now I've finally gotten support for gcc-12 in all active stable
kernel trees, gcc-13 takes more work as you are finding out so I'm only
testing with newer trees (6.1 and newer).
So when you run into issues like this, that obviously work in newer
kernel releases, a report doesn't do much, BUT a git commit id of what
the commit that needs to be backported IS appreciated.
thanks,
greg k-h
next prev parent reply other threads:[~2023-08-09 6:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 6:17 stable-rc: 5.15: arm: fsl_dcu_drm_plane.c:176:20: error: 'drm_plane_helper_destroy' undeclared here Naresh Kamboju
2023-08-09 6:59 ` Greg Kroah-Hartman [this message]
2023-08-09 7:28 ` Naresh Kamboju
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=2023080946-wow-cross-1079@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=anders.roxell@linaro.org \
--cc=andersson@kernel.org \
--cc=arnd@arndb.de \
--cc=cristian.marussi@arm.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=sudeep.holla@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox