From: jbarnes@sgi.com (Jesse Barnes)
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] xbow.c kmalloc fixes
Date: Fri, 17 Oct 2003 17:37:54 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106641239528981@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106641220628729@msgid-missing>
On Fri, Oct 17, 2003 at 10:31:27AM -0700, David Mosberger wrote:
> So what should be done about these SN2 cleanups? I don't want to
> accept dozens of small "fixes" (which really are mostly cleanups) as
> that would defeat the idea of the code-fixes-only decree. On the
> other hand, I really would like to see the SN2 code cleaned up so we actually
> have a sane base to do bug fixes on top of.
Unfortunately, many of the cleanups and fixes (of which there are many)
are now intertwined.
> Perhaps it would actually be a better idea to have one big SN2 cleanup
> patch which gets applied directly by Andrew? It seems like he would
> be OK with a one-time exception (since the code had been in the works
> and since the old code is so gross) and as long as the patch doesn't
> break GENERIC compiles, I'm going to be OK with it anyhow. How about
> it?
Sounds good to me. Pat, do you have one big patch you can send to
Andrew that includes Jes' latest checkins? Let me know if you need help
testing it.
Thanks,
Jesse
next prev parent reply other threads:[~2003-10-17 17:37 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 [this message]
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
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-106641239528981@msgid-missing \
--to=jbarnes@sgi.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