| Date | Fri, 10 May 2019 08:24:07 +0200 | From | Greg Kroah-Hartman <> | Subject | Re: [PATCH 4.19 32/66] xtensa: fix initialization of pt_regs::syscall in start_thread |
| |
On Thu, May 09, 2019 at 11:55:31AM -0700, Max Filippov wrote: > Hello, > > On Thu, May 9, 2019 at 11:48 AM Greg Kroah-Hartman > <gregkh@linuxfoundation.org> wrote: > > > > [ Upstream commit 2663147dc7465cb29040a05cc4286fdd839978b5 ] > > > > New pt_regs should indicate that there's no syscall, not that there's > > syscall #0. While at it wrap macro body in do/while and parenthesize > > macro arguments. > > > > Signed-off-by: Max Filippov <jcmvbkbc@gmail.com> > > Signed-off-by: Sasha Levin <sashal@kernel.org> > > --- > > arch/xtensa/include/asm/processor.h | 21 ++++++++++++--------- > > 1 file changed, 12 insertions(+), 9 deletions(-) > > This patch should not be taken to any of the stable trees, except maybe > 5.0.y, because NO_SYSCALL was introduced to arch/xtensa in 5.0.
Now dropped from everywhere except 5.0.y, thanks.
> This patch doesn't have any cc:stable tags, I'm curious why was it chosen > for stable and what can I do to prevent that in the future?
Sasha's tools picked this up and you should have been cc:ed on it when it was selected a few weeks ago.
thanks,
greg k-h
|