From: Kevin Wolf <kwolf@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: fam@euphon.net, berto@igalia.com, qemu-block@nongnu.org,
qemu-devel@nongnu.org, mreitz@redhat.com, stefanha@redhat.com,
den@openvz.org
Subject: Re: [PATCH 0/4] block: prepare for 64bit
Date: Tue, 8 Dec 2020 18:13:17 +0100 [thread overview]
Message-ID: <20201208171317.GA24068@merkur.fritz.box> (raw)
In-Reply-To: <20201203222713.13507-1-vsementsov@virtuozzo.com>
Am 03.12.2020 um 23:27 hat Vladimir Sementsov-Ogievskiy geschrieben:
> Hi all!
>
> This is a preparation series for v4 of "[PATCH v3 00/17] 64bit
> block-layer".
>
> The whole thing is in 04, and 01-03 are small preparations.
Thanks, applied to the block branch.
Kevin
next prev parent reply other threads:[~2020-12-08 17:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 22:27 [PATCH 0/4] block: prepare for 64bit Vladimir Sementsov-Ogievskiy
2020-12-03 22:27 ` [PATCH 1/4] block/file-posix: fix workaround in raw_do_pwrite_zeroes() Vladimir Sementsov-Ogievskiy
2020-12-03 22:27 ` [PATCH 2/4] block/io: bdrv_refresh_limits(): use ERRP_GUARD Vladimir Sementsov-Ogievskiy
2020-12-04 15:08 ` Alberto Garcia
2020-12-03 22:27 ` [PATCH 3/4] block/io: bdrv_check_byte_request(): drop bdrv_is_inserted() Vladimir Sementsov-Ogievskiy
2020-12-04 15:16 ` Alberto Garcia
2020-12-03 22:27 ` [PATCH 4/4] block: introduce BDRV_MAX_LENGTH Vladimir Sementsov-Ogievskiy
2021-01-07 9:58 ` Richard W.M. Jones
2021-01-07 10:56 ` Richard W.M. Jones
2021-01-07 12:20 ` Richard W.M. Jones
2021-01-08 11:14 ` Vladimir Sementsov-Ogievskiy
2021-01-08 11:27 ` Daniel P. Berrangé
2021-02-04 14:05 ` Eric Blake
2021-01-08 10:51 ` Vladimir Sementsov-Ogievskiy
2021-01-08 11:02 ` Richard W.M. Jones
2020-12-08 17:13 ` Kevin Wolf [this message]
2020-12-08 17:32 ` [PATCH 0/4] block: prepare for 64bit Vladimir Sementsov-Ogievskiy
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=20201208171317.GA24068@merkur.fritz.box \
--to=kwolf@redhat.com \
--cc=berto@igalia.com \
--cc=den@openvz.org \
--cc=fam@euphon.net \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vsementsov@virtuozzo.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;
as well as URLs for NNTP newsgroup(s).