linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Jan Beulich <jbeulich@novell.com>
Cc: mingo@elte.hu, tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: check function status in EDD boot code
Date: Fri, 18 Jul 2008 14:33:33 -0700	[thread overview]
Message-ID: <48810C2D.6070807@zytor.com> (raw)
In-Reply-To: <4880AA39.76E4.0078.0@novell.com>

Jan Beulich wrote:
> Without checking the return value of get_edd_info() and adding the
> entry only in the success case, 6 devices show up under
> /sys/firmware/edd/, no matter how many devices are actually present.
> 
> Signed-off-by: Jan Beulich <jbeulich@novell.com>

Applied to x86/setup, thanks.

	-hpa

      reply	other threads:[~2008-07-18 21:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-18 12:35 [PATCH] x86: check function status in EDD boot code Jan Beulich
2008-07-18 21:33 ` H. Peter Anvin [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=48810C2D.6070807@zytor.com \
    --to=hpa@zytor.com \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).