From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] kernel 2.5.69 doesn't compile for UP
Date: Wed, 14 May 2003 19:30:31 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705807@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705787@msgid-missing>
>>>>> On Wed, 14 May 2003 19:05:45 +0100, Matthew Wilcox <willy@debian.org> said:
Matthew> Yes, I'd love to ;-) I just need to fix your 2.5.69 patch
Matthew> so it'll compile :-P $ find -type f |xargs grep
Matthew> compat_sys_setaffinity ./arch/ia64/ia32/ia32_entry.S: data8
The ia32 subsystem does NOT work at the moment, as I mentioned in my
announcement. If you chose to ignore my messages, tough luck.
Matthew> Seriously, this is an attitude I see way too much of in
Matthew> this port. Something's broken so it gets kludged inside
Matthew> arch/ia64 (or worse yet,
It's always nice to hear your opinions.
Matthew> Maybe it's a relic of the "secret beginnings" of this port,
Matthew> or maybe people from certain companies have too narrow a
Matthew> focus, but it has to stop. I think the attitude is
Matthew> starting to change but there's a lot of cruft built up.
Oh, yeah, bring out your conspiracy theories. Yawn.
Perhaps you might want to consider a more obvious scenario? Like,
there is much more work to go around than time/people to do it all and
hence certain things get lower priority?
In fact, why not start with yourself? If you see something that you
absolutely hate, send in a patch to fix it. That's how Linux works.
--david
next prev parent reply other threads:[~2003-05-14 19:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 13:31 [Linux-ia64] kernel 2.5.69 doesn't compile for UP Eric Piel
2003-05-14 14:16 ` Matthew Wilcox
2003-05-14 17:32 ` David Mosberger
2003-05-14 18:05 ` Matthew Wilcox
2003-05-14 18:55 ` Andreas Schwab
2003-05-14 19:30 ` David Mosberger [this message]
2003-05-14 23:31 ` David Mosberger
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=marc-linux-ia64-105590723705807@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.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