From: Greg KH <gregkh@linuxfoundation.org>
To: Sumanth Korikkar <sumanthk@linux.ibm.com>
Cc: stable@vger.kernel.org, debian-s390@lists.debian.org,
debian-kernel@lists.debian.org, svens@linux.ibm.com,
hca@linux.ibm.com, gor@linux.ibm.com, Ulrich.Weigand@de.ibm.com,
dipak.zope1@ibm.com
Subject: Re: [PATCH 1/1] s390/signal: fix endless loop in do_signal
Date: Wed, 15 Feb 2023 14:22:24 +0100 [thread overview]
Message-ID: <Y+zckC7f4J453O81@kroah.com> (raw)
In-Reply-To: <20230215120413.949348-2-sumanthk@linux.ibm.com>
On Wed, Feb 15, 2023 at 01:04:13PM +0100, Sumanth Korikkar wrote:
> No upstream commit exists.
Why not? Please explain how this was fixed in Linus's tree and why we
can't take the same change here as well.
thanks,
greg k-h
next prev parent reply other threads:[~2023-02-15 13:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 12:04 [PATCH 0/1] s390: fix endless loop in do_signal Sumanth Korikkar
2023-02-15 12:04 ` [PATCH 1/1] s390/signal: " Sumanth Korikkar
2023-02-15 13:22 ` Greg KH [this message]
2023-02-15 13:23 ` [PATCH 0/1] s390: " Greg KH
2023-02-15 13:35 ` Heiko Carstens
2023-02-15 13:49 ` Greg KH
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=Y+zckC7f4J453O81@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=debian-kernel@lists.debian.org \
--cc=debian-s390@lists.debian.org \
--cc=dipak.zope1@ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=stable@vger.kernel.org \
--cc=sumanthk@linux.ibm.com \
--cc=svens@linux.ibm.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).