From: Michael Ellerman <mpe@ellerman.id.au>
To: stable@vger.kernel.org
Cc: matoro_mailinglist_kernel@matoro.tk, linuxppc-dev@lists.ozlabs.org
Subject: Please backport feea65a338e5 ("powerpc/powernv: Fix fortify source warnings in opal-prd.c")
Date: Mon, 20 Nov 2023 10:20:13 +1100 [thread overview]
Message-ID: <87edgl72ky.fsf@mail.lhotse> (raw)
Hi,
Please backport feea65a338e5 ("powerpc/powernv: Fix fortify source
warnings in opal-prd.c") to the 6.5, 6.1, 5.15, 5.10 stable trees.
cheers
next reply other threads:[~2023-11-19 23:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-19 23:20 Michael Ellerman [this message]
2023-11-24 16:03 ` Please backport feea65a338e5 ("powerpc/powernv: Fix fortify source warnings in opal-prd.c") Greg KH
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=87edgl72ky.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=matoro_mailinglist_kernel@matoro.tk \
--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 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).