All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] xbow.c kmalloc fixes
Date: Fri, 17 Oct 2003 20:11:16 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106642328707088@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106641220628729@msgid-missing>

>>>>> On Fri, 17 Oct 2003 18:47:51 +0100, Christoph Hellwig <hch@infradead.org> said:

  Christoph> On Fri, Oct 17, 2003 at 10:31:27AM -0700, David Mosberger
  Christoph> 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.

  Christoph> What about letting the SGI folks creeate a
  Christoph> sn-cleanups-2.6 BK tree and let them deal with Linus
  Christoph> themselves with your below blanket approval?

That's what I was suggesting (apart from patch vs bk; I don't care
about the mechanism of getting the updates into Linus tree; I just
don't want to be stuck with a large SN2 update which may or may not be
accepted by Linus/Andrew).

	--david

  parent reply	other threads:[~2003-10-17 20:11 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 [this message]
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-106642328707088@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 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.