qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org,
	pbonzini@redhat.com, Kevin Wolf <kwolf@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 0/3] block: Fix libbz2 library dependency regresssion
Date: Thu, 15 Sep 2016 09:42:51 +0800	[thread overview]
Message-ID: <20160915014251.GA10143@lemon> (raw)
In-Reply-To: <aa3dafdd-bba4-2315-93ce-51abd6431f16@redhat.com>

On Wed, 09/14 16:48, Max Reitz wrote:
> On 2016-09-14 at 16:35, Stefan Hajnoczi wrote:
> > On Mon, Sep 05, 2016 at 10:50:42AM +0800, Fam Zheng wrote:
> > > v4: Remove unused variable in patch 1 and unwanted warning in patch 2. [Max]
> > > 
> > > v3: Fix typo in copyright header. [Max]
> > >     Fix pre-existing type casting. [Max]
> > > 
> > > v2: Rebase on top of Max's block-next tree, which has Colin's patches to
> > >     dynamically load block modules.
> > >     Two more tweaks to the module system is added.
> > > 
> > > v1 was submitted as a single patch:
> > > 
> > > https://lists.gnu.org/archive/html/qemu-devel/2016-08/msg00508.html
> > > 
> > > Fam Zheng (3):
> > >   scripts: Allow block module to not define BlockDriver
> > >   module: Don't load the same module if requested multiple times
> > >   dmg: Move libbz2 code to dmg-bz2.so
> > > 
> > >  block/Makefile.objs             |  3 +-
> > >  block/dmg-bz2.c                 | 62 ++++++++++++++++++++++++++++++++++++
> > >  block/dmg.c                     | 69 ++++++++++-------------------------------
> > >  block/dmg.h                     | 59 +++++++++++++++++++++++++++++++++++
> > >  scripts/modules/module_block.py |  7 -----
> > >  util/module.c                   | 18 +++++++++--
> > >  6 files changed, 156 insertions(+), 62 deletions(-)
> > >  create mode 100644 block/dmg-bz2.c
> > >  create mode 100644 block/dmg.h
> > 
> > Max was the last one to comment on this series.  I'll wait for him to
> > review this before applying it.
> 
> Looks good to me, but I'm afraid this series might depend on my block-next
> (now block) branch which has not been merged to master yet, actually. So
> maybe I should apply it instead? ;-)

Yes, please!

Fam

  reply	other threads:[~2016-09-15  3:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-05  2:50 [Qemu-devel] [PATCH v4 0/3] block: Fix libbz2 library dependency regresssion Fam Zheng
2016-09-05  2:50 ` [Qemu-devel] [PATCH v4 1/3] scripts: Allow block module to not define BlockDriver Fam Zheng
2016-09-05  2:50 ` [Qemu-devel] [PATCH v4 2/3] module: Don't load the same module if requested multiple times Fam Zheng
2016-09-05  2:50 ` [Qemu-devel] [PATCH v4 3/3] dmg: Move libbz2 code to dmg-bz2.so Fam Zheng
2016-09-14 14:34 ` [Qemu-devel] [PATCH v4 0/3] block: Fix libbz2 library dependency regresssion Stefan Hajnoczi
2016-09-14 14:35 ` Stefan Hajnoczi
2016-09-14 14:48   ` Max Reitz
2016-09-15  1:42     ` Fam Zheng [this message]
2016-09-15 11:51     ` Stefan Hajnoczi
2016-09-23 14:55 ` Max Reitz

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=20160915014251.GA10143@lemon \
    --to=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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).