From: Greg KH <gregkh@linuxfoundation.org>
To: Avi Kivity <avi@scylladb.com>
Cc: stable@vger.kernel.org
Subject: Re: Backport status of "aio: fix async fsync creds" (530f32fc370fd1431ea9802dbc53ab5601dfccdb)
Date: Mon, 15 Jun 2020 14:30:45 +0200 [thread overview]
Message-ID: <20200615123045.GA615921@kroah.com> (raw)
In-Reply-To: <a88009bc-dcea-eaee-7fe9-943bc8aae781@scylladb.com>
On Mon, Jun 15, 2020 at 08:27:22AM +0300, Avi Kivity wrote:
> Commit "aio: fix async fsync creds"
> (530f32fc370fd1431ea9802dbc53ab5601dfccdb) was committed for v5.8-rc1, but I
> don't see it in any stable branches or rc queues (it is marked for 4.18+).
> Did it slip through the cracks? Or is it on some other queue?
It had to wait until 5.8-rc1 was out before I could take it into a
stable release. That just happened a few hours ago, and now I have 250+
patches to dig through that people decided to push in the -rc1 cycle,
yet are valid for stable trees...
I'll go queue this up now, but note that this just take longer during
the -rc1 cycle, and if you need it into a stable tree sooner, please let
us know.
thanks,
greg k-h
next prev parent reply other threads:[~2020-06-15 12:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 5:27 Backport status of "aio: fix async fsync creds" (530f32fc370fd1431ea9802dbc53ab5601dfccdb) Avi Kivity
2020-06-15 12:30 ` Greg KH [this message]
2020-06-15 14:47 ` Avi Kivity
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=20200615123045.GA615921@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=avi@scylladb.com \
--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