From: Mike Travis <travis@sgi.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Kyle Moffett <kyle@moffetthome.net>, Russ Anderson <rja@sgi.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, 05 Aug 2008 08:56:25 -0700 [thread overview]
Message-ID: <48987829.1060002@sgi.com> (raw)
In-Reply-To: <4898745F.2070902@zytor.com>
H. Peter Anvin wrote:
> Mike Travis wrote:
>>
>> Hi Kyle,
>>
>> As I'm very new to this development arena, could you explain a bit more
>> on why this is considered "bad manners"?
>>
>> I'm not speaking of any particular change, but there are some
>> realities in
>> bringing a new product to market that depends heavily on new "features"
>> being accepted into a specific kernel release. I certainly do not want
>> to "taint" any kernel code (and I'm always amazed at the dedication of
>> so many individuals to insure this doesn't happen), but the line between
>> acceptability (and not) seems to waver all over the place... ;-)
>>
>
> It's because it's your responsibility to get the code in by whenever you
> need it to, but trying to push unfinished code with the motivation "we
> need it in by <release>" violates the development model *and* is just
> plain rude.
>
> This comes down to the old saying "lack of planning on your part does
> not constitute an emergency on my part."
>
> In other words, if you want to push code in by a specific release, the
> code needs to be *done* and properly submitted. Submitting code that
> has a big "real code goes here" comment, is ridiculous.
>
> Unfortunately we have seen a *lot* of that from several people at SGI
> over the last year.
>
> -hpa
Hi Peter,
Ok, thanks, I do see your point (very clearly), as I prepare yet another
"we really, really need this" patch... ;-)
[ok, it's only a led driver and the world won't stop if it doesn't show up
in the kernel... ;-)]
Cheers,
Mike
next prev parent reply other threads:[~2008-08-05 15:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 19:57 x86 BIOS interface for partitioning and system serial number on SGI UV 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
2008-08-05 14:35 ` Mike Travis
2008-08-05 15:40 ` H. Peter Anvin
2008-08-05 15:56 ` Mike Travis [this message]
-- strict thread matches above, loose matches on Subject: below --
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=48987829.1060002@sgi.com \
--to=travis@sgi.com \
--cc=hpa@zytor.com \
--cc=kyle@moffetthome.net \
--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 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.