From: Petr Vorel <pvorel@suse.cz>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>, Martijn Coenen <maco@android.com>,
linux-block@vger.kernel.org
Subject: Re: loop uevent fix
Date: Thu, 12 Nov 2020 20:31:00 +0100 [thread overview]
Message-ID: <20201112193100.GC14767@pevik> (raw)
In-Reply-To: <20201112165005.4022502-1-hch@lst.de>
Hi Jens, Christoph,
> Hi Peter and Jens,
> this is how I'd slightly respin the patch from Petr on top of the
> set_capacity_revalidate_and_notify I need for 5.11. Let me know what
> you think.
+1, thanks.
From your discussion on my original patch I understand that these 2 fixes will
make it to v5.10-rc4. Will they go also to v5.9 stable tree? (it affects also
v5.8, but that version is EOL).
Kind regards,
Petr
next prev parent reply other threads:[~2020-11-12 19:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 16:50 loop uevent fix Christoph Hellwig
2020-11-12 16:50 ` [PATCH 1/2] block: add a return value to set_capacity_revalidate_and_notify Christoph Hellwig
2020-11-12 19:13 ` Petr Vorel
2020-11-12 16:50 ` [PATCH 2/2] loop: Fix occasional uevent drop Christoph Hellwig
2020-11-12 19:25 ` Petr Vorel
2020-11-12 19:31 ` Petr Vorel [this message]
2020-11-12 20:59 ` loop uevent fix Jens Axboe
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=20201112193100.GC14767@pevik \
--to=pvorel@suse.cz \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=maco@android.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