From: Greg KH <gregkh@linuxfoundation.org>
To: Will Deacon <will.deacon@arm.com>
Cc: stable@vger.kernel.org, sasha.levin@oracle.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: fix off-by-one in compat syscall table for syscalls over 382
Date: Sun, 24 Jan 2016 13:41:59 -0800 [thread overview]
Message-ID: <20160124214159.GB9841@kroah.com> (raw)
In-Reply-To: <20160118122447.GE3693@arm.com>
On Mon, Jan 18, 2016 at 12:24:48PM +0000, Will Deacon wrote:
> Greg, Sasha,
>
> Is there anything else I need to do to get this queued in the 3.17.y
> and 3.18.y stable trees? There's no corresponding upstream commit since
> the issue was fixed by accident in 3.19+ as a result of something else.
I'm not releasing any 3.17.y or 3.18.y kernels, so there's nothing I can
do here, sorry.
greg k-h
prev parent reply other threads:[~2016-01-24 21:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 17:16 [PATCH] arm64: fix off-by-one in compat syscall table for syscalls over 382 Will Deacon
2016-01-18 12:24 ` Will Deacon
2016-01-24 21:41 ` Greg KH [this message]
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=20160124214159.GB9841@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=sasha.levin@oracle.com \
--cc=stable@vger.kernel.org \
--cc=will.deacon@arm.com \
/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).