From: Greg KH <greg@kroah.com>
To: rananta@codeaurora.org
Cc: Sasha Levin <sashal@kernel.org>, stable@vger.kernel.org
Subject: Re: Request to backport a patch onto 5.4.y stable
Date: Fri, 1 May 2020 07:53:26 +0200 [thread overview]
Message-ID: <20200501055326.GA805178@kroah.com> (raw)
In-Reply-To: <ba319dc2e66986c7cc594f88ce98621c@codeaurora.org>
On Thu, Apr 30, 2020 at 08:23:54PM -0700, rananta@codeaurora.org wrote:
> On 2020-04-30 16:33, Sasha Levin wrote:
> > On Thu, Apr 30, 2020 at 01:36:45PM -0700, rananta@codeaurora.org wrote:
> > > Hi,
> > >
> > > I need help to backport the patch with the following details onto
> > > the 5.4.y stable branch:
> > > Subject: [PATCH] tty: hvc: Fix data abort due to race in hvc_open
> > > commit-id: e2bd1dcbe1aa34ff5570b3427c530e4332ecf0fe
> > > Reason: The issue addressed in the patch was discovered on 5.4.y
> > > branch
> >
> > Is it in Linus's tree?
> It's on linux-next tree:
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/tty/hvc/hvc_console.c?id=e2bd1dcbe1aa34ff5570b3427c530e4332ecf0fe
As per the rules documented at:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
a patch has to be in Linus's tree before it can be included in a stable
kernel.
Please work with the tty developer to get this into Linus's tree if you
feel it should be needed there. As it is, it is only scheduled to be
sent to him for 5.8-rc1 as your patch description did not make it seem
very urgent or relevant for 5.7-final.
thanks,
greg k-h
prev parent reply other threads:[~2020-05-01 5:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 20:36 Request to backport a patch onto 5.4.y stable rananta
2020-04-30 23:33 ` Sasha Levin
2020-05-01 3:23 ` rananta
2020-05-01 5:53 ` 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=20200501055326.GA805178@kroah.com \
--to=greg@kroah.com \
--cc=rananta@codeaurora.org \
--cc=sashal@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 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).