From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Amit Pundir <amit.pundir@linaro.org>
Cc: ebiederm@xmission.com, alexander.levin@microsoft.com,
rmk@flint.arm.linux.org.uk, stable <stable@vger.kernel.org>,
stable-commits@vger.kernel.org
Subject: Re: Patch "signal/arm: Document conflicts with SI_USER and SIGFPE" has been added to the 4.4-stable tree
Date: Tue, 10 Apr 2018 23:15:53 +0200 [thread overview]
Message-ID: <20180410211553.GC19732@kroah.com> (raw)
In-Reply-To: <CAMi1Hd3JCCSJJabu50qb9TH=Se7GmXF+TJvvSQ3tiUiQOHygTQ@mail.gmail.com>
On Wed, Apr 11, 2018 at 12:11:29AM +0530, Amit Pundir wrote:
> On 10 April 2018 at 14:36, <gregkh@linuxfoundation.org> wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > signal/arm: Document conflicts with SI_USER and SIGFPE
> >
> > to the 4.4-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > signal-arm-document-conflicts-with-si_user-and-sigfpe.patch
> > and it can be found in the queue-4.4 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
>
> It broke ARM builds at kernelci
> https://kernelci.org/build/stable-rc/branch/linux-4.4.y/kernel/v4.4.127-170-g7914585b83e0/
>
> Eric has already pointed out in earlier emails that this a noop so it
> can be dropped from all stable queues.
Yes, they are now dropped.
thanks,
greg k-h
prev parent reply other threads:[~2018-04-10 21:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 9:06 Patch "signal/arm: Document conflicts with SI_USER and SIGFPE" has been added to the 4.4-stable tree gregkh
2018-04-10 18:41 ` Amit Pundir
2018-04-10 21:15 ` Greg Kroah-Hartman [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=20180410211553.GC19732@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.levin@microsoft.com \
--cc=amit.pundir@linaro.org \
--cc=ebiederm@xmission.com \
--cc=rmk@flint.arm.linux.org.uk \
--cc=stable-commits@vger.kernel.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.