public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Morten Helgesen <admin@nextframe.net>
To: linux-kernel@vger.kernel.org
Subject: Re:  [PATCH] remove last references to linux/malloc.h
Date: Thu, 22 Nov 2001 15:07:38 +0100	[thread overview]
Message-ID: <20011122150738.D117@sexything> (raw)
In-Reply-To: <20011122145527.A117@sexything> <27400.1006437269@redhat.com>
In-Reply-To: <27400.1006437269@redhat.com>

Hey David.

I see your point - but someone has obiously decided to switch from malloc.h to slab.h, and I do not
see the point in having three references to malloc.h when malloc.h only prints a warning and then includes
slab.h

== Morten


On Thu, Nov 22, 2001 at 01:54:29PM +0000, David Woodhouse wrote:
> 
> 
> admin@nextframe.net said:
> >  Ok people - stop submitting patches which include malloc.h. Include
> > slab.h instead. :)
> 
> Bah. I was sort of hoping we'd come to our collective senses and switch 
> them all back.
> 
> What does malloc.h do? Stuff to do with memory allocation, one presumes.
> What does slab.h do? Some random implementation detail that people have no 
> business knowing about.
> 
> --
> dwmw2
> 
> 

-- 
mvh
Morten Helgesen 
UNIX System Administrator & C Developer 
Nextframe AS
admin@nextframe.net / 93445641
http://www.nextframe.net

  parent reply	other threads:[~2001-11-22 14:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-22 13:55 [PATCH] remove last references to linux/malloc.h Morten Helgesen
     [not found] ` <27400.1006437269@redhat.com>
2001-11-22 14:07   ` Morten Helgesen [this message]
2001-11-24  3:57     ` Randy.Dunlap
2001-11-24 15:56       ` Jeff Garzik

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=20011122150738.D117@sexything \
    --to=admin@nextframe.net \
    --cc=linux-kernel@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