From: Eric Anholt <eric@anholt.net>
To: Richard Yao <ryao@cs.stonybrook.edu>, intel-gfx@lists.freedesktop.org
Cc: gentoo-bsd@lists.gentoo.org, David Shao <davshao@gmail.com>
Subject: Re: [PATCH] intel: Fix missing ETIME on BSD operating systems
Date: Sat, 10 Nov 2012 12:12:25 -0800 [thread overview]
Message-ID: <87ip9d1al2.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <1352525096-10345-1-git-send-email-ryao@cs.stonybrook.edu>
[-- Attachment #1.1: Type: text/plain, Size: 556 bytes --]
Richard Yao <ryao@cs.stonybrook.edu> writes:
> From: David Shao <davshao@gmail.com>
>
> Originally posted to Free Desktop bug #52549 by David Shao.
> Resolves Gentoo Bug #433403.
> Commit message by Richard Yao.
Are you really unable to get the same errnos in your port of the kernel
modules? Having mismatched errno returns from upstream is a great way
to have obscure bugs on your port, given that our kernel guys like to
look for alternative errnos to be able to distinguish failure modes from
userland.
I don't like the idea of this patch landing.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2012-11-10 20:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-10 5:24 [PATCH] intel: Fix missing ETIME on BSD operating systems Richard Yao
2012-11-10 20:01 ` Ben Widawsky
2012-11-10 20:12 ` Eric Anholt [this message]
2012-11-10 21:36 ` Richard Yao
2012-11-11 17:26 ` Ben Widawsky
-- strict thread matches above, loose matches on Subject: below --
2012-11-10 5:23 Richard Yao
2012-11-10 5:06 Richard Yao
2012-11-09 22:06 Richard Yao
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=87ip9d1al2.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--cc=davshao@gmail.com \
--cc=gentoo-bsd@lists.gentoo.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ryao@cs.stonybrook.edu \
/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