* Backport status of "aio: fix async fsync creds" (530f32fc370fd1431ea9802dbc53ab5601dfccdb)
@ 2020-06-15 5:27 Avi Kivity
2020-06-15 12:30 ` Greg KH
0 siblings, 1 reply; 3+ messages in thread
From: Avi Kivity @ 2020-06-15 5:27 UTC (permalink / raw)
To: stable
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?
Thanks, Avi
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Backport status of "aio: fix async fsync creds" (530f32fc370fd1431ea9802dbc53ab5601dfccdb)
2020-06-15 5:27 Backport status of "aio: fix async fsync creds" (530f32fc370fd1431ea9802dbc53ab5601dfccdb) Avi Kivity
@ 2020-06-15 12:30 ` Greg KH
2020-06-15 14:47 ` Avi Kivity
0 siblings, 1 reply; 3+ messages in thread
From: Greg KH @ 2020-06-15 12:30 UTC (permalink / raw)
To: Avi Kivity; +Cc: stable
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Backport status of "aio: fix async fsync creds" (530f32fc370fd1431ea9802dbc53ab5601dfccdb)
2020-06-15 12:30 ` Greg KH
@ 2020-06-15 14:47 ` Avi Kivity
0 siblings, 0 replies; 3+ messages in thread
From: Avi Kivity @ 2020-06-15 14:47 UTC (permalink / raw)
To: Greg KH; +Cc: stable
On 15/06/2020 15.30, Greg KH wrote:
> 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...
Thanks, I wasn't aware of this extra gate.
> 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.
In fact, I've been waiting for this patch to do into mainline for a few
months, so waiting a little longer isn't a problem. Knowing it hasn't
been dropped is sufficient for me.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-06-15 14:47 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-06-15 5:27 Backport status of "aio: fix async fsync creds" (530f32fc370fd1431ea9802dbc53ab5601dfccdb) Avi Kivity
2020-06-15 12:30 ` Greg KH
2020-06-15 14:47 ` Avi Kivity
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).