From: Greg KH <greg@kroah.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: stable@vger.kernel.org, tglx@linutronix.de, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH stable 4.14 00/23] powerpc backports for 4.14
Date: Fri, 25 May 2018 13:26:01 +0200 [thread overview]
Message-ID: <20180525112601.GA348@kroah.com> (raw)
In-Reply-To: <87bmd4q9ow.fsf@concordia.ellerman.id.au>
On Fri, May 25, 2018 at 09:03:11PM +1000, Michael Ellerman wrote:
> Michael Ellerman <mpe@ellerman.id.au> writes:
> > Hi Greg,
> >
> > Please queue up this series of patches for 4.14 if you have no objections.
>
> I just realised I didn't fix up the cherry-pick markings on these, so
> they still say eg:
>
> (cherry picked from commit bdcb1aefc5b3f7d0f1dc8b02673602bca2ff7a4b)
>
> Not the proper "commit bdcb1... upstream" style.
>
> I'll hold off resending in case you have some sed magic to fix that, but
> let me know if you'd like me to do it and resend the series.
I don't have any sed magic for that, sorry. Can you fix up and resend?
thanks,
greg k-h
next prev parent reply other threads:[~2018-05-25 11:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 10:09 [PATCH stable 4.14 00/23] powerpc backports for 4.14 Michael Ellerman
2018-05-25 10:09 ` [PATCH stable 4.14 01/23] powerpc/64s: Improve RFI L1-D cache flush fallback Michael Ellerman
2018-05-25 10:09 ` [PATCH stable 4.14 02/23] powerpc/pseries: Support firmware disable of RFI flush Michael Ellerman
2018-05-25 10:09 ` [PATCH stable 4.14 03/23] powerpc/powernv: " Michael Ellerman
2018-05-25 10:09 ` [PATCH stable 4.14 04/23] powerpc/rfi-flush: Move the logic to avoid a redo into the debugfs code Michael Ellerman
2018-05-25 10:09 ` [PATCH stable 4.14 05/23] powerpc/rfi-flush: Make it possible to call setup_rfi_flush() again Michael Ellerman
2018-05-25 10:09 ` [PATCH stable 4.14 06/23] powerpc/rfi-flush: Always enable fallback flush on pseries Michael Ellerman
2018-05-25 10:09 ` [PATCH stable 4.14 07/23] powerpc/rfi-flush: Differentiate enabled and patched flush types Michael Ellerman
2018-05-25 10:09 ` [PATCH stable 4.14 08/23] powerpc/rfi-flush: Call setup_rfi_flush() after LPM migration Michael Ellerman
2018-05-25 10:09 ` [PATCH stable 4.14 09/23] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags Michael Ellerman
2018-05-25 10:09 ` [PATCH stable 4.14 10/23] powerpc: Add security feature flags for Spectre/Meltdown Michael Ellerman
2018-05-25 10:09 ` [PATCH stable 4.14 11/23] powerpc/pseries: Set or clear security feature flags Michael Ellerman
2018-05-25 10:09 ` [PATCH stable 4.14 12/23] powerpc/powernv: " Michael Ellerman
2018-05-25 10:09 ` [PATCH stable 4.14 13/23] powerpc/64s: Move cpu_show_meltdown() Michael Ellerman
2018-05-25 10:09 ` [PATCH stable 4.14 14/23] powerpc/64s: Enhance the information in cpu_show_meltdown() Michael Ellerman
2018-05-25 10:09 ` [PATCH stable 4.14 15/23] powerpc/powernv: Use the security flags in pnv_setup_rfi_flush() Michael Ellerman
2018-05-25 10:09 ` [PATCH stable 4.14 16/23] powerpc/pseries: Use the security flags in pseries_setup_rfi_flush() Michael Ellerman
2018-05-25 10:09 ` [PATCH stable 4.14 17/23] powerpc/64s: Wire up cpu_show_spectre_v1() Michael Ellerman
2018-05-25 10:09 ` [PATCH stable 4.14 18/23] powerpc/64s: Wire up cpu_show_spectre_v2() Michael Ellerman
2018-05-25 10:09 ` [PATCH stable 4.14 19/23] powerpc/pseries: Fix clearing of security feature flags Michael Ellerman
2018-05-25 10:09 ` [PATCH stable 4.14 20/23] powerpc: Move default " Michael Ellerman
2018-05-25 10:09 ` [PATCH stable 4.14 21/23] powerpc/pseries: Restore default security feature flags on setup Michael Ellerman
2018-05-25 10:09 ` [PATCH stable 4.14 22/23] powerpc/64s: Fix section mismatch warnings from setup_rfi_flush() Michael Ellerman
2018-05-25 10:09 ` [PATCH stable 4.14 23/23] powerpc/64s: Add support for a store forwarding barrier at kernel entry/exit Michael Ellerman
2018-05-25 11:03 ` [PATCH stable 4.14 00/23] powerpc backports for 4.14 Michael Ellerman
2018-05-25 11:26 ` Greg KH [this message]
2018-05-26 4:41 ` Michael Ellerman
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=20180525112601.GA348@kroah.com \
--to=greg@kroah.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).