qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alberto Garcia <berto@igalia.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] [PULL v3 00/43] Block layer patches (Stefan's tree)
Date: Thu, 12 Nov 2015 17:26:43 +0100	[thread overview]
Message-ID: <20151112162643.GA21450@igalia.com> (raw)
In-Reply-To: <1447342628-11546-1-git-send-email-kwolf@redhat.com>

On Thu, Nov 12, 2015 at 04:37:08PM +0100, Kevin Wolf wrote:
> The following changes since commit 17e50a72a3aade0eddfebc012a5d7bdd40a03573:
> 
>   Merge remote-tracking branch 'remotes/jasowang/tags/net-pull-request' into staging (2015-11-12 14:15:32 +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 aece5edc96f211eec6febdafc9bbbb99315a2efd:
> 
>   block: Update copyright of the accounting code (2015-11-12 16:22:47 +0100)
> 
> ----------------------------------------------------------------
> Block layer patches (rebased Stefan's pull request)
> 
> ----------------------------------------------------------------
> Alberto Garcia (21):
>       xen_disk: Account for flush operations
>       ide: Account for write operations correctly
>       block: define 'clock_type' for the accounting code
>       util: Infrastructure for computing recent averages
>       block: Add idle_time_ns to BlockDeviceStats
>       block: Add statistics for failed and invalid I/O operations
>       block: Allow configuring whether to account failed and invalid ops
>       block: Compute minimum, maximum and average I/O latencies
>       block: Add average I/O queue depth to BlockDeviceTimedStats
>       block: New option to define the intervals for collecting I/O statistics
>       qemu-io: Account for failed, invalid and flush operations
>       block: Use QEMU_CLOCK_VIRTUAL for the accounting code in qtest mode
>       iotests: Add test for the block device statistics
>       nvme: Account for failed and invalid operations
>       virtio-blk: Account for failed and invalid operations
>       xen_disk: Account for failed and invalid operations
>       atapi: Account for failed and invalid operations
>       ide: Account for failed and invalid operations
>       macio: Account for failed operations
>       scsi-disk: Account for failed operations
>       block: Update copyright of the accounting code

Hi Kevin,

Are you not including this one as well?

https://patchwork.ozlabs.org/patch/542872/

Berto

  reply	other threads:[~2015-11-12 16:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12 15:37 [Qemu-devel] [PULL v3 00/43] Block layer patches (Stefan's tree) Kevin Wolf
2015-11-12 16:26 ` Alberto Garcia [this message]
2015-11-13  2:34   ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2015-11-12 18:07 ` [Qemu-devel] " Peter Maydell
2015-11-13  2:33 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi

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=20151112162643.GA21450@igalia.com \
    --to=berto@igalia.com \
    --cc=kwolf@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /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).