mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: jgarzik@mandrakesoft.com (Jeff Garzik)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox), linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.0test11pre1ac1
Date: Wed, 8 Nov 2000 23:58:32 +0000 (GMT)	[thread overview]
Message-ID: <E13tf6v-0000cW-00@the-village.bc.nu> (raw)
In-Reply-To: <3A09E3E5.7A8EB9DB@mandrakesoft.com> from "Jeff Garzik" at Nov 08, 2000 06:38:13 PM

> * CARDBUS is never defined.  Should that be CONFIG_CARDBUS?

Yep

> * just increment the version number.  There's no need to add "a" on the
> end...  this version number just differentiates us from the 'canonical'
> Donald Becker version of epic100.c.

Ok

> net/atm/pvc:  return the error value from sock_register, not toss it
> away.

> 
> 
> ramfs comments:

Note: the ramfs changes are in there for one reason only - that Im hacking
on some bits with a pda type box and I cannot be bothered to keep two
sets of trees

> That's one API change we shouldn't throw in without discussion, IMHO...
> it screams "ramfs-specific hack in core code!"

Absolutely

> And finally, don't you need to EXPORT_SYMBOL pm_devs_lock ?

Yep


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-08 23:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-08 23:01 Alan Cox
2000-11-08 23:38 ` Jeff Garzik
2000-11-08 23:58   ` Alan Cox [this message]
2000-11-09  3:14     ` VPN Masquerade patch going into 2.2.18final? Dan Browning
2000-11-09 13:09       ` Alan Cox
2000-11-09  0:49 ` Linux 2.4.0test11pre1ac1 David S. Miller

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=E13tf6v-0000cW-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=jgarzik@mandrakesoft.com \
    --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®