public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Glauber de Oliveira Costa <gcosta@redhat.com>
Cc: linux-kernel@vger.kernel.org, rusty@rustycorp.com.au,
	akpm@linux-foundation.org, ak@suse.de, lguest@ozlabs.org
Subject: Re: [Lguest] [PATCH] turn err into errx in lguest call sites
Date: Wed, 22 Aug 2007 16:51:43 +1000	[thread overview]
Message-ID: <1187765503.6174.58.camel@localhost.localdomain> (raw)
In-Reply-To: <1187728117715-git-send-email-gcosta@redhat.com>

On Tue, 2007-08-21 at 17:28 -0300, Glauber de Oliveira Costa wrote:
> These two callsites should really be errx instead of err, since there is
> no errno associated with them in the moment they are issued.
> 
> Signed-off-by: Glauber de Oliveira Costa <gcosta@redhat.com>

Thanks, applied!

Rusty.



      reply	other threads:[~2007-08-22  6:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-21 20:28 [PATCH] turn err into errx in lguest call sites Glauber de Oliveira Costa
2007-08-22  6:51 ` Rusty Russell [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=1187765503.6174.58.camel@localhost.localdomain \
    --to=rusty@rustcorp.com.au \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=gcosta@redhat.com \
    --cc=lguest@ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustycorp.com.au \
    /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