From: Sasha Levin <sashal@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: mikey@neuling.org, linuxppc-dev@lists.ozlabs.org,
stable@vger.kernel.org, gregkh@linuxfoundation.org
Subject: Re: [PATCH] powerpc/tm: Limit TM code inside PPC_TRANSACTIONAL_MEM
Date: Fri, 18 Jan 2019 09:51:21 -0500 [thread overview]
Message-ID: <20190118145121.GE202535@sasha-vm> (raw)
In-Reply-To: <bc20e375-09a0-1672-f61c-f90375c31a61@debian.org>
On Thu, Jan 17, 2019 at 09:49:05AM -0200, Breno Leitao wrote:
>hi Sasha,
>
>On 1/16/19 11:35 AM, Sasha Levin wrote:
>> 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?
>
>I understand that the commit that this patch fixes is not integrated into
>stable tree.
>
>I think it does not need to make stable at this moment, thus.
The commit it fixes (e1c3743e1a20) exists in all 4.9+ stable trees as it
itself was tagged for stable.
--
Thanks,
Sasha
WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sashal@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: linuxppc-dev@lists.ozlabs.org, mikey@neuling.org,
mpe@ellerman.id.au, gregkh@linuxfoundation.org,
stable@vger.kernel.org
Subject: Re: [PATCH] powerpc/tm: Limit TM code inside PPC_TRANSACTIONAL_MEM
Date: Fri, 18 Jan 2019 09:51:21 -0500 [thread overview]
Message-ID: <20190118145121.GE202535@sasha-vm> (raw)
In-Reply-To: <bc20e375-09a0-1672-f61c-f90375c31a61@debian.org>
On Thu, Jan 17, 2019 at 09:49:05AM -0200, Breno Leitao wrote:
>hi Sasha,
>
>On 1/16/19 11:35 AM, Sasha Levin wrote:
>> 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?
>
>I understand that the commit that this patch fixes is not integrated into
>stable tree.
>
>I think it does not need to make stable at this moment, thus.
The commit it fixes (e1c3743e1a20) exists in all 4.9+ stable trees as it
itself was tagged for stable.
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-01-18 14:53 UTC|newest]
Thread overview: 9+ 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-09 13:16 ` Breno Leitao
2019-01-14 10:12 ` Michael Ellerman
2019-01-14 10:12 ` Michael Ellerman
2019-01-16 13:35 ` [PATCH] " Sasha Levin
2019-01-17 11:49 ` Breno Leitao
2019-01-17 11:49 ` Breno Leitao
2019-01-18 14:51 ` Sasha Levin [this message]
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=20190118145121.GE202535@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=leitao@debian.org \
--cc=linuxppc-dev@lists.ozlabs.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 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.