From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] (ata.mod) avoid passing grub_errno to upper layer
Date: Sat, 29 Nov 2008 19:37:46 +0100 [thread overview]
Message-ID: <20081129183746.GA2766@thorin> (raw)
In-Reply-To: <20081129124820.GA5612@thorin>
[-- Attachment #1: Type: text/plain, Size: 297 bytes --]
Okay, I think I got what you mean. So how about this one?
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
[-- Attachment #2: ata.diff --]
[-- Type: text/x-diff, Size: 878 bytes --]
2008-11-29 Robert Millan <rmh@aybabtu.com>
* disk/ata.c (grub_ata_pciinit): Handle errors rised by
grub_ata_device_initialize() calls.
Index: disk/ata.c
===================================================================
--- disk/ata.c (revision 1929)
+++ disk/ata.c (working copy)
@@ -542,6 +542,16 @@ grub_ata_pciinit (int bus, int device, i
{
grub_ata_device_initialize (controller * 2 + i, 0, rega, regb);
grub_ata_device_initialize (controller * 2 + i, 1, rega, regb);
+
+ /* Most errors rised by grub_ata_device_initialize() are harmless.
+ They just indicate this particular drive is not responding, most
+ likely because it doesn't exist. We might want to ignore specific
+ error types here, instead of printing them. */
+ if (grub_errno)
+ {
+ grub_print_error ();
+ grub_errno = GRUB_ERR_NONE;
+ }
}
}
next prev parent reply other threads:[~2008-11-29 18:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 15:35 [PATCH] (ata.mod) avoid passing grub_errno to upper layer Robert Millan
2008-11-25 21:17 ` Yoshinori K. Okuji
2008-11-28 19:37 ` Robert Millan
2008-11-29 10:01 ` Vesa Jääskeläinen
2008-11-29 12:48 ` Robert Millan
2008-11-29 18:37 ` Robert Millan [this message]
2008-11-29 21:06 ` Robert Millan
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=20081129183746.GA2766@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.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.