All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org
Subject: Re: [Qemu-trivial] [PATCH 0/3] util/uri: Cleanups and a bug fix
Date: Wed, 04 Feb 2015 10:48:25 +0100	[thread overview]
Message-ID: <87d25q80t2.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <1422375232-29283-1-git-send-email-armbru@redhat.com> (Markus Armbruster's message of "Tue, 27 Jan 2015 17:13:49 +0100")

Ping?

Markus Armbruster <armbru@redhat.com> writes:

> Note: checkpatch is unhappy with the first patch, because I refrained
> from cleaning up the ugly return(NULL).  They're all over the place.
>
> Markus Armbruster (3):
>   util/uri: uri_new() can't fail, drop dead error handling
>   util/uri: realloc2n() can't fail, drop dead error handling
>   util/uri: URI member path can be null, compare more carfully
>
>  util/uri.c | 61 +++++++++++++------------------------------------------------
>  1 file changed, 13 insertions(+), 48 deletions(-)


WARNING: multiple messages have this Message-ID (diff)
From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] util/uri: Cleanups and a bug fix
Date: Wed, 04 Feb 2015 10:48:25 +0100	[thread overview]
Message-ID: <87d25q80t2.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <1422375232-29283-1-git-send-email-armbru@redhat.com> (Markus Armbruster's message of "Tue, 27 Jan 2015 17:13:49 +0100")

Ping?

Markus Armbruster <armbru@redhat.com> writes:

> Note: checkpatch is unhappy with the first patch, because I refrained
> from cleaning up the ugly return(NULL).  They're all over the place.
>
> Markus Armbruster (3):
>   util/uri: uri_new() can't fail, drop dead error handling
>   util/uri: realloc2n() can't fail, drop dead error handling
>   util/uri: URI member path can be null, compare more carfully
>
>  util/uri.c | 61 +++++++++++++------------------------------------------------
>  1 file changed, 13 insertions(+), 48 deletions(-)

  parent reply	other threads:[~2015-02-04  9:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27 16:13 [Qemu-trivial] [PATCH 0/3] util/uri: Cleanups and a bug fix Markus Armbruster
2015-01-27 16:13 ` [Qemu-devel] " Markus Armbruster
2015-01-27 16:13 ` [Qemu-trivial] [PATCH 1/3] util/uri: uri_new() can't fail, drop dead error handling Markus Armbruster
2015-01-27 16:13   ` [Qemu-devel] " Markus Armbruster
2015-01-27 16:13 ` [Qemu-trivial] [PATCH 2/3] util/uri: realloc2n() " Markus Armbruster
2015-01-27 16:13   ` [Qemu-devel] " Markus Armbruster
2015-01-27 16:13 ` [Qemu-trivial] [PATCH 3/3] util/uri: URI member path can be null, compare more carfully Markus Armbruster
2015-01-27 16:13   ` [Qemu-devel] " Markus Armbruster
2015-01-27 16:43 ` [Qemu-trivial] [PATCH 0/3] util/uri: Cleanups and a bug fix Paolo Bonzini
2015-01-27 16:43   ` [Qemu-devel] " Paolo Bonzini
2015-01-28 11:21   ` [Qemu-trivial] " Markus Armbruster
2015-01-28 11:21     ` Markus Armbruster
2015-01-28 13:30     ` [Qemu-trivial] " Paolo Bonzini
2015-01-28 13:30       ` [Qemu-devel] " Paolo Bonzini
2015-02-04  9:48 ` Markus Armbruster [this message]
2015-02-04  9:48   ` Markus Armbruster
2015-02-07 20:43 ` [Qemu-trivial] " Michael Tokarev
2015-02-07 20:43   ` [Qemu-devel] " Michael Tokarev

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=87d25q80t2.fsf@blackfin.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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 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.