From: "Kyle Moffett" <kyle@moffetthome.net>
To: "Russ Anderson" <rja@sgi.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
mingo@elte.hu, tglx@linutronix.de, linux-kernel@vger.kernel.org,
"Jack Steiner" <steiner@sgi.com>
Subject: Re: x86 BIOS interface for partitioning and system serial number on SGI UV
Date: Tue, 5 Aug 2008 01:21:46 -0400 [thread overview]
Message-ID: <f73f7ab80808042221v5bebcea9o7e536093373647cd@mail.gmail.com> (raw)
In-Reply-To: <20080804221951.GA252105@sgi.com>
On Mon, Aug 4, 2008 at 6:19 PM, Russ Anderson <rja@sgi.com> wrote:
> On Fri, Aug 01, 2008 at 10:34:30AM -0700, H. Peter Anvin wrote:
>>Russ Anderson wrote:
>>>+# define BIOS_CALL(result, a0, a1, a2, a3, a4, a5, a6, a7) \
>>>+ do { \
>>>+ /* XXX - the real call goes here */ \
>>>+ result.status = BIOS_STATUS_UNIMPLEMENTED; \
>>>+ result.v0 = 0; \
>>>+ result.v1 = 0; \
>>>+ } while (0)
>>
>> I have more than a little problem with submitting patches like this. We
>> have no way to judge the suitability of the coding or the interface with
>> the "meat" of the driver stubbed out!
>
> This is also code for hardware that does not exist. In order for the
> code to be in distro releases in time for the hardware to ship, we
> must push it _before_ we have hardware. The main concern is getting in
> interfaces now, because the interfaces cannot change in a minor release.
> Providing more "meat" is on the ToDo list.
These kinds of statements are not the way to get things done on LKML.
Quite a number of people have gotten flamed/ignored/etc lately by
making statements "We need this (unfinished code) in the kernel by
2.6.27 because RHEL6 is going to use 2.6.27 and otherwise we won't be
supported in RHEL6".
Cheers,
Kyle Moffett
next prev parent reply other threads:[~2008-08-05 5:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 19:57 Russ Anderson
2008-08-01 17:34 ` H. Peter Anvin
2008-08-04 22:19 ` Russ Anderson
2008-08-05 0:50 ` H. Peter Anvin
2008-08-05 0:59 ` H. Peter Anvin
2008-08-05 3:54 ` Greg KH
2008-08-05 16:32 ` Russ Anderson
2008-08-05 16:53 ` Greg KH
2008-08-05 19:22 ` Russ Anderson
2008-08-05 23:06 ` Russ Anderson
2008-08-05 5:21 ` Kyle Moffett [this message]
2008-08-05 14:35 ` Mike Travis
2008-08-05 15:40 ` H. Peter Anvin
2008-08-05 15:56 ` Mike Travis
2008-08-05 17:24 H. Peter Anvin
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=f73f7ab80808042221v5bebcea9o7e536093373647cd@mail.gmail.com \
--to=kyle@moffetthome.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rja@sgi.com \
--cc=steiner@sgi.com \
--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
Powered by JetHome