From: Kevin Wolf <kwolf@redhat.com>
To: ronnie sahlberg <ronniesahlberg@gmail.com>
Cc: qemu-devel@nongnu.org,
"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
Hannes Reinecke <hare@suse.de>
Subject: [Qemu-devel] Re: [PATCH 1/1] iscsi: add iSCSI block device support
Date: Mon, 22 Nov 2010 10:27:03 +0100 [thread overview]
Message-ID: <4CEA3767.6050707@redhat.com> (raw)
In-Reply-To: <AANLkTinke0r_ub4aqhbzG=LUjrvb4xEyM=5xFQwi1C3h@mail.gmail.com>
Am 21.11.2010 23:17, schrieb ronnie sahlberg:
> List,
>
> Please find attached a gzipped patch against master that adds support of iSCSI.
> It is sent in gz format because of its uncompressed size, >100kb.
I think there's something missing in your mail. :-)
Anyway, I got the code from the KVM list, and I have some general comments:
* Please split this into some smaller patches and send them as a patch
series. Inline the patches instead of a gzipped attachment, because
that makes it a lot easier to comment the code when replying to your
mail.
* Have a look at CODING_STYLE in the repository, especially at the
sections about 80 chars per line and whitespace.
* Don't use printf() but error_report() for error messages
* Try to use qemu functions instead of POSIX ones so that the code
will also work on Windows and other platforms. If you can't make it
run on Windows, still use qemu functions where possible and change
the Makefile to compile it only for POSIX hosts.
* Once you use qemu_malloc, you can drop your NULL checks. qemu_malloc
never returns an error.
* Use QLISTs (qemu-queue.h) instead of introducing a new SLIST
Kevin
next prev parent reply other threads:[~2010-11-22 9:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-21 22:17 [Qemu-devel] [PATCH 1/1] iscsi: add iSCSI block device support ronnie sahlberg
2010-11-21 23:13 ` FUJITA Tomonori
2010-11-21 23:39 ` ronnie sahlberg
2010-11-22 9:27 ` Kevin Wolf [this message]
2010-11-24 17:04 ` Christoph Hellwig
2010-11-24 19:14 ` Stefan Hajnoczi
2010-11-25 4:32 ` Nicholas A. Bellinger
2010-11-25 5:22 ` ronnie sahlberg
2010-11-25 9:30 ` Kevin Wolf
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=4CEA3767.6050707@redhat.com \
--to=kwolf@redhat.com \
--cc=hare@suse.de \
--cc=nab@linux-iscsi.org \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.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 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.