From: Greg KH <gregkh@linuxfoundation.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: matoro_mailinglist_kernel@matoro.tk,
linuxppc-dev@lists.ozlabs.org, stable@vger.kernel.org
Subject: Re: Please backport feea65a338e5 ("powerpc/powernv: Fix fortify source warnings in opal-prd.c")
Date: Fri, 24 Nov 2023 16:03:16 +0000 [thread overview]
Message-ID: <2023112409-undusted-grasp-e11e@gregkh> (raw)
In-Reply-To: <87edgl72ky.fsf@mail.lhotse>
On Mon, Nov 20, 2023 at 10:20:13AM +1100, Michael Ellerman wrote:
> 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.
Now queued up, thanks.
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: stable@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
matoro_mailinglist_kernel@matoro.tk
Subject: Re: Please backport feea65a338e5 ("powerpc/powernv: Fix fortify source warnings in opal-prd.c")
Date: Fri, 24 Nov 2023 16:03:16 +0000 [thread overview]
Message-ID: <2023112409-undusted-grasp-e11e@gregkh> (raw)
In-Reply-To: <87edgl72ky.fsf@mail.lhotse>
On Mon, Nov 20, 2023 at 10:20:13AM +1100, Michael Ellerman wrote:
> 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.
Now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2023-11-24 16:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-19 23:20 Please backport feea65a338e5 ("powerpc/powernv: Fix fortify source warnings in opal-prd.c") Michael Ellerman
2023-11-19 23:20 ` Michael Ellerman
2023-11-24 16:03 ` Greg KH [this message]
2023-11-24 16:03 ` 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=2023112409-undusted-grasp-e11e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=matoro_mailinglist_kernel@matoro.tk \
--cc=mpe@ellerman.id.au \
--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 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.