From: Jes Sorensen <jes@wildopensource.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] xbow.c kmalloc fixes
Date: Mon, 20 Oct 2003 08:34:35 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106663954514393@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106641220628729@msgid-missing>
>>>>> "Colin" = Colin Ngam <cngam@sgi.com> writes:
Colin> It does not matter to me if you want us to wait until this
Colin> code-fixes-only period is over. We will be doing all our
Colin> regression on 2.4 and when we merge over to 2.6, we will also
Colin> do our regression tests there too. None of these changes will
Colin> have any effect on any other platform except to ensure that
Colin> Generic builds and boots on other Platforms(including SGI).
Hi Colin,
I think we need to get moving on the 2.6 push asap, the 2.6 tree is
closing soon so we need to get it in as soon as possible ot we risk
missing the train.
I don't think the new hardware supports is as big a problem to put in
later since it's always legal to push new 'drivers' to a stable
kernel.
Cheers,
Jes
next prev parent reply other threads:[~2003-10-20 8:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 17:31 [patch] xbow.c kmalloc fixes David Mosberger
2003-10-17 17:37 ` Jesse Barnes
2003-10-17 17:47 ` Christoph Hellwig
2003-10-17 20:08 ` David Mosberger
2003-10-17 20:11 ` David Mosberger
2003-10-18 1:17 ` Colin Ngam
2003-10-20 8:34 ` Jes Sorensen [this message]
2003-10-20 8:46 ` Jes Sorensen
2003-10-20 18:25 ` David Mosberger
2003-10-20 18:50 ` Colin Ngam
2003-10-20 20:43 ` David Mosberger
-- strict thread matches above, loose matches on Subject: below --
2003-10-17 13:04 Jes Sorensen
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-106663954514393@msgid-missing \
--to=jes@wildopensource.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