From: "NeilBrown" <neilb@suse.de>
To: "Massimo Cetra" <mcetra@navynet.it>
Cc: "Frans Pop" <elendil@planet.nl>,
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>,
"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 22:12:05 +1100 [thread overview]
Message-ID: <9a9a41fd6c04a891d8b3c4279903edd9.squirrel@neil.brown.name> (raw)
In-Reply-To: <4AD6FF9B.6060109@navynet.it>
On Thu, October 15, 2009 9:55 pm, Massimo Cetra wrote:
> 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.
See http://lwn.net/Articles/356890/
"Ask a kernel developer, part 2"
(you'll have to wait a week if you aren't a subscriber).
(or try ./scripts/get_maintainer.pl)
NeilBrown
>
> Thanks again
> Massimo
>
prev parent reply other threads:[~2009-10-15 11:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 14:11 Massimo Cetra
2009-10-14 19:29 ` Massimo Cetra
2009-10-14 20:32 ` Frans Pop
2009-10-15 10:55 ` Massimo Cetra
2009-10-15 11:12 ` NeilBrown [this message]
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=9a9a41fd6c04a891d8b3c4279903edd9.squirrel@neil.brown.name \
--to=neilb@suse.de \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=mcetra@navynet.it \
--cc=mpatocka@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®