All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Michael Neuling <mikey@neuling.org>
Cc: linuxppc-dev@ozlabs.org, kexec@lists.infradead.org
Subject: Re: [PATCH] kexec ppc64: cleanup get_devtree_details
Date: Tue, 1 May 2007 14:54:24 +0900	[thread overview]
Message-ID: <20070501055422.GA20102@verge.net.au> (raw)
In-Reply-To: <10869.1177991234@neuling.org>

On Tue, May 01, 2007 at 01:47:14PM +1000, Michael Neuling wrote:
> Cleanup error paths in get_devtree_details.  Also convert fstat from a
> pointer to avoid malloc.

Thanks, applied.

-- 
Horms
  H: http://www.vergenet.net/~horms/
  W: http://www.valinux.co.jp/en/


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@verge.net.au>
To: Michael Neuling <mikey@neuling.org>
Cc: linuxppc-dev@ozlabs.org, kexec@lists.infradead.org
Subject: Re: [PATCH] kexec ppc64: cleanup get_devtree_details
Date: Tue, 1 May 2007 14:54:24 +0900	[thread overview]
Message-ID: <20070501055422.GA20102@verge.net.au> (raw)
In-Reply-To: <10869.1177991234@neuling.org>

On Tue, May 01, 2007 at 01:47:14PM +1000, Michael Neuling wrote:
> Cleanup error paths in get_devtree_details.  Also convert fstat from a
> pointer to avoid malloc.

Thanks, applied.

-- 
Horms
  H: http://www.vergenet.net/~horms/
  W: http://www.valinux.co.jp/en/

  reply	other threads:[~2007-05-01  5:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01  3:47 [PATCH] kexec ppc64: cleanup get_devtree_details Michael Neuling
2007-05-01  3:47 ` Michael Neuling
2007-05-01  5:54 ` Simon Horman [this message]
2007-05-01  5:54   ` Simon Horman

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=20070501055422.GA20102@verge.net.au \
    --to=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mikey@neuling.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.