mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH] compatmac is not needed
Date: Wed, 9 Apr 2003 18:03:27 +0200	[thread overview]
Message-ID: <20030409180327.K626@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <1049877554.31462.24.camel@passion.cambridge.redhat.com>; from dwmw2@infradead.org on Wed, Apr 09, 2003 at 09:39:15AM +0100

On Wed, Apr 09, 2003 at 09:39:15AM +0100, David Woodhouse wrote:
> On Tue, 2003-04-08 at 17:42, Linux Kernel Mailing List wrote:
> > ChangeSet 1.1089, 2003/04/08 09:42:06-07:00, alan@lxorguk.ukuu.org.uk
> > 
> > 	[PATCH] compatmac is not needed
> 
> So compatmac.h ends up _empty_ in the latest kernel, but that doesn't
> mean it's not needed.
> 
> Please don't break stuff just for the sake of it.

So this is still a valid API? Good to know.

What I don't know: Can it be product specific? So the net people
ship a version for new networking APIs and filesystem people ship
new filesystem methods along with their filesystem support.

Reason I ask: There are many such frameworks floating around, but
none was complete. Many miss BUG_ON(), likely()/unlikely(),
seq_file support and many more interesting stuff.

Regards

Ingo Oeser
-- 
Marketing ist die Kunst, Leuten Sachen zu verkaufen, die sie
nicht brauchen, mit Geld, was sie nicht haben, um Leute zu
beeindrucken, die sie nicht moegen.

  reply	other threads:[~2003-04-09 16:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200304081725.h38HPeSV012611@hera.kernel.org>
2003-04-09  8:39 ` David Woodhouse
2003-04-09 16:03   ` Ingo Oeser [this message]
2003-04-09 16:59     ` David Woodhouse

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=20030409180327.K626@nightmaster.csn.tu-chemnitz.de \
    --to=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dwmw2@infradead.org \
    --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

all inboxes | Powered by JetHome®