From: Seth Goldberg <seth.goldberg@oracle.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH 1/3] efinet: handle get_status() properly
Date: Wed, 05 Aug 2015 13:57:17 -0700 [thread overview]
Message-ID: <55C278AD.7040801@oracle.com> (raw)
In-Reply-To: <55C27179.6020104@fb.com>
> Anyway that's not important, what is
> important is that the current code doesn't work with hardware that
> exists in the wild. If it's a firmware bug then fine, what do users do
> if they have buggy firmware that isn't being updated anymore? I think
> making grub more tolerant to crappy firmware is a good thing. Thanks,
Absolutely agree.
--S
next prev parent reply other threads:[~2015-08-05 20:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 18:36 [PATCH 1/3] efinet: handle get_status() properly Josef Bacik
2015-08-05 18:36 ` [PATCH 2/3] net: add local route when creating link local ipv6 interface Josef Bacik
2015-08-07 8:38 ` Andrei Borzenkov
2015-08-05 18:36 ` [PATCH 3/3] net: fix ipv6 routing Josef Bacik
2015-08-09 14:58 ` Andrei Borzenkov
2015-08-10 14:00 ` Josef Bacik
2015-08-10 14:07 ` Andrei Borzenkov
2015-08-05 20:04 ` [PATCH 1/3] efinet: handle get_status() properly Andrei Borzenkov
2015-08-05 20:26 ` Josef Bacik
2015-08-05 20:32 ` Vladimir 'phcoder' Serbinenko
2015-08-05 20:39 ` Josef Bacik
2015-08-05 20:50 ` Josef Bacik
2015-08-05 20:52 ` Vladimir 'phcoder' Serbinenko
2015-08-06 3:42 ` Andrei Borzenkov
2015-08-06 14:26 ` Josef Bacik
2015-08-05 20:57 ` Seth Goldberg [this message]
2015-08-06 17:49 ` [PATCH V2] efinet: handle get_status() on buggy firmware properly Josef Bacik
2015-08-09 13:48 ` Andrei Borzenkov
-- strict thread matches above, loose matches on Subject: below --
2015-08-05 17:50 [PATCH 0/3] fix ipv6 support Josef Bacik
2015-08-05 17:50 ` [PATCH 1/3] efinet: handle get_status() properly Josef Bacik
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=55C278AD.7040801@oracle.com \
--to=seth.goldberg@oracle.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 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).