[Qemu-devel] [PULL 00/12] Block layer fixes for 2.9.0-rc1

Kevin Wolf posted 12 patches 8 years, 7 months ago
Failed in applying to current master (apply log)
Test checkpatch passed
Test docker passed
MAINTAINERS                      |    8 -
block.c                          |   23 +-
block/Makefile.objs              |    2 -
block/archipelago.c              | 1079 --------------------------------------
block/backup.c                   |   26 +-
block/commit.c                   |   28 +-
block/file-posix.c               |   47 ++
block/io.c                       |    2 +-
block/mirror.c                   |    9 +
block/vvfat.c                    |   22 +-
configure                        |   43 --
migration/block.c                |    2 +
qapi/block-core.json             |   33 +-
tests/qemu-iotests/025           |    2 +-
tests/qemu-iotests/common        |    6 -
tests/qemu-iotests/common.filter |    4 +-
tests/qemu-iotests/common.rc     |    8 -
17 files changed, 143 insertions(+), 1201 deletions(-)
delete mode 100644 block/archipelago.c
[Qemu-devel] [PULL 00/12] Block layer fixes for 2.9.0-rc1
Posted by Kevin Wolf 8 years, 7 months ago
The following changes since commit dd4d2578215cd380f40a38028a9904e15b135ef3:

  Merge remote-tracking branch 'remotes/kraxel/tags/pull-fixes-20170309-1' into staging (2017-03-09 13:16:05 +0000)

are available in the git repository at:


  git://repo.or.cz/qemu/kevin.git tags/for-upstream

for you to fetch changes up to dcbf37ce41a52698550f8f8b2f14b5e6fee22d2d:

  commit: Implement .bdrv_refresh_filename (2017-03-13 12:49:33 +0100)

----------------------------------------------------------------
Block layer fixes for 2.9.0-rc1

----------------------------------------------------------------
Eric Blake (4):
      block: Drop unmaintained 'archipelago' driver
      backup: React to bdrv_is_allocated() errors
      vvfat: React to bdrv_is_allocated() errors
      migration: Document handling of bdrv_is_allocated() errors

Fam Zheng (1):
      file-posix: Consider max_segments for BlockLimits.max_transfer

Kevin Wolf (6):
      block: Remove check_new_perm from bdrv_replace_child()
      block: Request block status from *file for BDRV_BLOCK_RAW
      commit: Implement bdrv_commit_top.bdrv_co_get_block_status
      block: Refresh filename after changing backing file
      mirror: Implement .bdrv_refresh_filename
      commit: Implement .bdrv_refresh_filename

Vladimir Sementsov-Ogievskiy (1):
      backup: allow target without .bdrv_get_info

 MAINTAINERS                      |    8 -
 block.c                          |   23 +-
 block/Makefile.objs              |    2 -
 block/archipelago.c              | 1079 --------------------------------------
 block/backup.c                   |   26 +-
 block/commit.c                   |   28 +-
 block/file-posix.c               |   47 ++
 block/io.c                       |    2 +-
 block/mirror.c                   |    9 +
 block/vvfat.c                    |   22 +-
 configure                        |   43 --
 migration/block.c                |    2 +
 qapi/block-core.json             |   33 +-
 tests/qemu-iotests/025           |    2 +-
 tests/qemu-iotests/common        |    6 -
 tests/qemu-iotests/common.filter |    4 +-
 tests/qemu-iotests/common.rc     |    8 -
 17 files changed, 143 insertions(+), 1201 deletions(-)
 delete mode 100644 block/archipelago.c

Re: [Qemu-devel] [PULL 00/12] Block layer fixes for 2.9.0-rc1
Posted by Peter Maydell 8 years, 7 months ago
On 13 March 2017 at 15:54, Kevin Wolf <kwolf@redhat.com> wrote:
> The following changes since commit dd4d2578215cd380f40a38028a9904e15b135ef3:
>
>   Merge remote-tracking branch 'remotes/kraxel/tags/pull-fixes-20170309-1' into staging (2017-03-09 13:16:05 +0000)
>
> are available in the git repository at:
>
>
>   git://repo.or.cz/qemu/kevin.git tags/for-upstream
>
> for you to fetch changes up to dcbf37ce41a52698550f8f8b2f14b5e6fee22d2d:
>
>   commit: Implement .bdrv_refresh_filename (2017-03-13 12:49:33 +0100)
>
> ----------------------------------------------------------------
> Block layer fixes for 2.9.0-rc1

We haven't had rc0 yet :-)

Applied, thanks.

-- PMM

Re: [Qemu-devel] [PULL 00/12] Block layer fixes for 2.9.0-rc1
Posted by Kevin Wolf 8 years, 7 months ago
Am 13.03.2017 um 19:05 hat Peter Maydell geschrieben:
> On 13 March 2017 at 15:54, Kevin Wolf <kwolf@redhat.com> wrote:
> > The following changes since commit dd4d2578215cd380f40a38028a9904e15b135ef3:
> >
> >   Merge remote-tracking branch 'remotes/kraxel/tags/pull-fixes-20170309-1' into staging (2017-03-09 13:16:05 +0000)
> >
> > are available in the git repository at:
> >
> >
> >   git://repo.or.cz/qemu/kevin.git tags/for-upstream
> >
> > for you to fetch changes up to dcbf37ce41a52698550f8f8b2f14b5e6fee22d2d:
> >
> >   commit: Implement .bdrv_refresh_filename (2017-03-13 12:49:33 +0100)
> >
> > ----------------------------------------------------------------
> > Block layer fixes for 2.9.0-rc1
> 
> We haven't had rc0 yet :-)

I was assuming that we'd just skip -rc0 then. Are we instead shifting
the release by a week or two?

Kevin

Re: [Qemu-devel] [PULL 00/12] Block layer fixes for 2.9.0-rc1
Posted by Peter Maydell 8 years, 7 months ago
On 14 March 2017 at 10:29, Kevin Wolf <kwolf@redhat.com> wrote:
> Am 13.03.2017 um 19:05 hat Peter Maydell geschrieben:
>> On 13 March 2017 at 15:54, Kevin Wolf <kwolf@redhat.com> wrote:
>> > The following changes since commit dd4d2578215cd380f40a38028a9904e15b135ef3:
>> >
>> >   Merge remote-tracking branch 'remotes/kraxel/tags/pull-fixes-20170309-1' into staging (2017-03-09 13:16:05 +0000)
>> >
>> > are available in the git repository at:
>> >
>> >
>> >   git://repo.or.cz/qemu/kevin.git tags/for-upstream
>> >
>> > for you to fetch changes up to dcbf37ce41a52698550f8f8b2f14b5e6fee22d2d:
>> >
>> >   commit: Implement .bdrv_refresh_filename (2017-03-13 12:49:33 +0100)
>> >
>> > ----------------------------------------------------------------
>> > Block layer fixes for 2.9.0-rc1
>>
>> We haven't had rc0 yet :-)
>
> I was assuming that we'd just skip -rc0 then. Are we instead shifting
> the release by a week or two?

I'm planning to push all the rcs back a week. Of course
if we get to rc1/rc2 and there's very little going into the
tree we can release early, but this basically never happens.

thanks
-- PMM