From: Massimo Cetra <mcetra@navynet.it>
To: Frans Pop <elendil@planet.nl>
Cc: linux-kernel@vger.kernel.org, Mark McLoughlin <markmc@redhat.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Mikulas Patocka <mpatocka@redhat.com>,
Alasdair G Kergon <agk@redhat.com>, Neil Brown <neilb@suse.de>,
virtualization <virtualization@lists.linux-foundation.org>,
dm-devel <dm-devel@redhat.com>
Subject: Re: Bug on barriers for virtio_blk device - end_request: I/O error, dev vda, sector 0
Date: Thu, 15 Oct 2009 12:55:23 +0200 [thread overview]
Message-ID: <4AD6FF9B.6060109@navynet.it> (raw)
In-Reply-To: <200910142232.14837.elendil@planet.nl>
Frans Pop ha scritto:
> Added CCs for the author of and people CCed on the patch.
>
> The patch has been submitted twice (6 Aug, 3 Sept), the first time there
> was one concern voiced which seems to have been addressed in replies. The
> second time there were no reactions.
>
> The patch seems to work for Massimo...
[CUT]
>> No one listening here ?
>
> It helps if you CC the people who maintain the relevant code.
Thanks, Frans.
By the way, where can i find a list of the mantainers of the various areas ?
I found it some years ago, but it seems i can't find it anymore.
It's probably under my eyes... but i'm blind.
Thanks again
Massimo
next prev parent reply other threads:[~2009-10-15 10:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 14:11 Bug on barriers for virtio_blk device - end_request: I/O error, dev vda, sector 0 Massimo Cetra
2009-10-14 19:29 ` Massimo Cetra
2009-10-14 20:32 ` Frans Pop
2009-10-14 20:32 ` Frans Pop
2009-10-15 10:55 ` Massimo Cetra
2009-10-15 10:55 ` Massimo Cetra [this message]
2009-10-15 11:12 ` NeilBrown
2009-10-15 11:12 ` NeilBrown
2009-10-15 11:12 ` NeilBrown
2009-10-14 20:32 ` Frans Pop
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=4AD6FF9B.6060109@navynet.it \
--to=mcetra@navynet.it \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=mpatocka@redhat.com \
--cc=neilb@suse.de \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.