linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Breno Leitao <leitao@debian.org>
To: linuxppc-dev@lists.ozlabs.org
Cc: , mikey@neuling.org, stable@vger.kernel.org, gregkh@linuxfoundation.org
Subject: Re: [PATCH] powerpc/tm: Limit TM code inside PPC_TRANSACTIONAL_MEM
Date: Wed, 16 Jan 2019 13:35:59 +0000	[thread overview]
Message-ID: <20190116133600.BA78B2086D@mail.kernel.org> (raw)
In-Reply-To: <1547039805-7979-1-git-send-email-leitao@debian.org>

Hi,

[This is an automated email]

This commit has been processed because it contains a "Fixes:" tag,
fixing commit: e1c3743e1a20 powerpc/tm: Set MSR[TS] just prior to recheckpoint.

The bot has tested the following trees: v4.20.2, v4.19.15, v4.14.93, v4.9.150.

v4.20.2: Failed to apply! Possible dependencies:
    Unable to calculate

v4.19.15: Failed to apply! Possible dependencies:
    Unable to calculate

v4.14.93: Failed to apply! Possible dependencies:
    0d60619e1c0c ("powerpc: Add missing prototype for sys_debug_setcontext()")
    67b464a89c21 ("powerpc/32: Mark both tmp variables as unused")
    6f5b9f018f4c ("powerpc/tm: Unset MSR[TS] if not recheckpointing")
    b53875c4b4f2 ("powerpc: Add missing prototypes for sys_sigreturn() & sys_rt_sigreturn()")
    bf7fb32dd5fc ("powerpc: Add missing prototypes for ppc_select() & ppc_fadvise64_64()")
    f3675644e172 ("powerpc/syscalls: signal_{32, 64} - switch to SYSCALL_DEFINE")

v4.9.150: Failed to apply! Possible dependencies:
    0d60619e1c0c ("powerpc: Add missing prototype for sys_debug_setcontext()")
    67b464a89c21 ("powerpc/32: Mark both tmp variables as unused")
    6f5b9f018f4c ("powerpc/tm: Unset MSR[TS] if not recheckpointing")
    b53875c4b4f2 ("powerpc: Add missing prototypes for sys_sigreturn() & sys_rt_sigreturn()")
    bf7fb32dd5fc ("powerpc: Add missing prototypes for ppc_select() & ppc_fadvise64_64()")
    f3675644e172 ("powerpc/syscalls: signal_{32, 64} - switch to SYSCALL_DEFINE")


How should we proceed with this patch?

--
Thanks,
Sasha

  parent reply	other threads:[~2019-01-16 13:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-09 13:16 [PATCH] powerpc/tm: Limit TM code inside PPC_TRANSACTIONAL_MEM Breno Leitao
2019-01-14 10:12 ` Michael Ellerman
2019-01-16 13:35 ` Sasha Levin [this message]
2019-01-17 11:49   ` [PATCH] " Breno Leitao
2019-01-18 14:51     ` Sasha Levin

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=20190116133600.BA78B2086D@mail.kernel.org \
    --to=sashal@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=mikey@neuling.org \
    --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).