All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Lieven <pl@kamp.de>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: kwolf@redhat.com, famz@redhat.com, qemu-devel@nongnu.org,
	owasserm@redhat.com, ronniesahlberg@gmail.com,
	pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCHv3] block: add native support for NFS
Date: Fri, 20 Dec 2013 14:23:42 +0100	[thread overview]
Message-ID: <52B444DE.1090301@kamp.de> (raw)
In-Reply-To: <20131220130729.GC5905@stefanha-thinkpad.redhat.com>

On 20.12.2013 14:07, Stefan Hajnoczi wrote:
> On Fri, Dec 20, 2013 at 12:31:57PM +0100, Peter Lieven wrote:
>> - DID NOT add full implementation of bdrv_get_allocated_file_size because
>>    we are not in a coroutine context and I cannot do an async call here.
>>    I could do a sync call if there would be a guarantee that no requests
>>    are in flight. [Stefan]
> Let's discuss in the other email thread where we started.
Okay.
>
>> +static int64_t nfs_client_open(NFSClient *client, const char *filename,
>> +                               int flags, Error **errp)
>> +{
>> +    int ret = -EINVAL;
>> +    URI *uri;
>> +    char *file = NULL, *strp = NULL;
>> +    struct stat st;
>> +
>> +    uri = uri_parse(filename);
>> +    if (!uri) {
>> +        error_setg(errp, "Invalid URL specified.\n");
> \n should not be included in error_setg() messages.
>
>> +        goto fail;
>> +    }
>> +    strp = strrchr(uri->path, '/');
>> +    if (strp == NULL) {
>> +        error_setg(errp, "Invalid URL specified.\n");
> \n should not be included in error_setg() messages.

If thats the only objection you have, please remove the \n
when picking.

Thanks,
Peter

      reply	other threads:[~2013-12-20 13:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-20 11:31 [Qemu-devel] [PATCHv3] block: add native support for NFS Peter Lieven
2013-12-20 13:07 ` Stefan Hajnoczi
2013-12-20 13:23   ` Peter Lieven [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=52B444DE.1090301@kamp.de \
    --to=pl@kamp.de \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=owasserm@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=ronniesahlberg@gmail.com \
    --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 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.