From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Fedor Pchelkin <pchelkin@ispras.ru>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
Daniel Starke <daniel.starke@siemens.com>,
jirislaby@kernel.org, Alexey Khoroshilov <khoroshilov@ispras.ru>,
lvc-project@linuxtesting.org
Subject: Re: [PATCH 5.10] Revert "tty: n_gsm: avoid call of sleeping functions from atomic context"
Date: Sun, 4 Dec 2022 16:57:18 +0100 [thread overview]
Message-ID: <Y4zDXrMEeCTElmRs@kroah.com> (raw)
In-Reply-To: <Y4tQjdqL2vbDnTX8@kroah.com>
On Sat, Dec 03, 2022 at 02:35:09PM +0100, Greg Kroah-Hartman wrote:
> On Wed, Nov 23, 2022 at 09:19:16PM +0300, Fedor Pchelkin wrote:
> > From: Fedor Pchelkin <pchelkin@ispras.ru>
> >
> > [ Upstream commit acdab4cb4ba7e5f94d2b422ebd7bf4bf68178fb2 ]
> >
> > This reverts commit eb75efdec8dd0f01ac85c88feafa6e63b34a2521.
>
> What about for 5.15? This should also be needed there, right?
Odd, it never got applied to 5.15, so nevermind about that, sorry for
the noise.
greg k-h
next prev parent reply other threads:[~2022-12-04 15:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 18:19 [PATCH 5.10] Revert "tty: n_gsm: avoid call of sleeping functions from atomic context" Fedor Pchelkin
2022-11-28 14:20 ` Pavel Machek
2022-12-03 13:35 ` Greg Kroah-Hartman
2022-12-03 22:35 ` [PATCH 5.19 0/2] tty: n_gsm: revert tx_mutex usage Fedor Pchelkin
2022-12-03 22:35 ` [PATCH 5.19 1/2] Revert "tty: n_gsm: avoid call of sleeping functions from atomic context" Fedor Pchelkin
2022-12-03 22:35 ` [PATCH 5.19 2/2] Revert "tty: n_gsm: replace kicktimer with delayed_work" Fedor Pchelkin
2022-12-04 15:56 ` [PATCH 5.19 0/2] tty: n_gsm: revert tx_mutex usage Greg Kroah-Hartman
2022-12-04 15:57 ` Greg Kroah-Hartman [this message]
2022-12-03 13:38 ` [PATCH 5.10] Revert "tty: n_gsm: avoid call of sleeping functions from atomic context" Greg Kroah-Hartman
2022-12-03 21:55 ` [PATCH v2 " Fedor Pchelkin
2022-12-04 15:59 ` Greg Kroah-Hartman
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=Y4zDXrMEeCTElmRs@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=daniel.starke@siemens.com \
--cc=jirislaby@kernel.org \
--cc=khoroshilov@ispras.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=pchelkin@ispras.ru \
--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.