qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: Karl Rister <krister@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Max Reitz <mreitz@redhat.com>,
	qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 2/6] stubs: Add stubs for ram block notifier API
Date: Thu, 23 Feb 2017 10:49:06 +0100	[thread overview]
Message-ID: <b59e8052-971c-d6ff-de1d-7758adc01d91@redhat.com> (raw)
In-Reply-To: <20170223091845.18523-3-famz@redhat.com>



On 23/02/2017 10:18, Fam Zheng wrote:
> These two functions will be wanted by block-obj-y but the actual
> definition is in obj-y which is correctly placed, so stub them to keep
> the linker happy.
> 
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
>  stubs/Makefile.objs        |  1 +
>  stubs/ram-block-notifier.c | 10 ++++++++++
>  2 files changed, 11 insertions(+)
>  create mode 100644 stubs/ram-block-notifier.c
> 
> diff --git a/stubs/Makefile.objs b/stubs/Makefile.objs
> index aa6050f..38e3bdc 100644
> --- a/stubs/Makefile.objs
> +++ b/stubs/Makefile.objs
> @@ -36,3 +36,4 @@ stub-obj-y += qmp_pc_dimm_device_list.o
>  stub-obj-y += target-monitor-defs.o
>  stub-obj-y += target-get-monitor-def.o
>  stub-obj-y += pc_madt_cpu_entry.o
> +stub-obj-y += ram-block-notifier.o
> diff --git a/stubs/ram-block-notifier.c b/stubs/ram-block-notifier.c
> new file mode 100644
> index 0000000..ea5d528
> --- /dev/null
> +++ b/stubs/ram-block-notifier.c
> @@ -0,0 +1,10 @@
> +#include "qemu/osdep.h"
> +#include "exec/ramlist.h"
> +
> +void ram_block_notifier_add(RAMBlockNotifier *n)
> +{
> +}
> +
> +void ram_block_notifier_remove(RAMBlockNotifier *n)
> +{
> +}
> 

Acked-by: Paolo Bonzini <pbonzini@redhat.com>

  reply	other threads:[~2017-02-23  9:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-23  9:18 [Qemu-devel] [PATCH v2 0/6] block: Add VFIO based driver for NVMe device Fam Zheng
2017-02-23  9:18 ` [Qemu-devel] [PATCH v2 1/6] nvme: Move NVMe definitions to a separate header Fam Zheng
2017-02-23  9:18 ` [Qemu-devel] [PATCH v2 2/6] stubs: Add stubs for ram block notifier API Fam Zheng
2017-02-23  9:49   ` Paolo Bonzini [this message]
2017-02-23  9:18 ` [Qemu-devel] [PATCH v2 3/6] block: Add VFIO based NVMe driver Fam Zheng
2017-02-23  9:43   ` Paolo Bonzini
2017-02-23 10:01     ` Fam Zheng
2017-02-23  9:18 ` [Qemu-devel] [PATCH v2 4/6] block: Introduce bdrv_dma_map and bdrv_dma_unmap Fam Zheng
2017-02-23  9:18 ` [Qemu-devel] [PATCH v2 5/6] block/nvme: Implement .bdrv_dma_map and .bdrv_dma_unmap Fam Zheng
2017-02-23  9:18 ` [Qemu-devel] [PATCH v2 6/6] qemu-img: dma map buffers Fam Zheng
2017-02-23  9:28 ` [Qemu-devel] [PATCH v2 0/6] block: Add VFIO based driver for NVMe device no-reply
2017-02-23 10:48 ` Fam Zheng
2017-02-23 10:50   ` Paolo Bonzini
2017-02-23 11:19     ` Fam Zheng

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=b59e8052-971c-d6ff-de1d-7758adc01d91@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=famz@redhat.com \
    --cc=krister@redhat.com \
    --cc=mreitz@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).