linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@transmeta.com>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: test12-pre2
Date: Mon, 27 Nov 2000 18:45:31 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.10.10011271838080.15454-100000@penguin.transmeta.com> (raw)


Oh, well. Some people saw the (unannounced, and not for public
consumption) pre1, so here's pre2. pre1 was just meant to be an interim
patch to sync up with the ISDN patches.

Due to the birth of my third daughter last week (yes, I got /.'ed), if you
sent me patches that aren't in pre2, you can pretty much consider them
lost.

		Linus

---

 - pre2:
    - Peter Anvin: more P4 configuration parsing
    - Stephen Tweedie: O_SYNC patches. Make O_SYNC/fsync/fdatasync
      do the right thing.
    - Keith Owens: make mdule loading use the right struct module size
    - Boszormenyi Zoltan: get MTRR's right for the >32-bit case
    - Alan Cox: various random documentation etc
    - Dario Ballabio: EATA and u14-34f update
    - Ivan Kokshaysky: unbreak alpha ruffian
    - Richard Henderson: PCI bridge initialization on alpha
    - Zach Brown: correct locking in Maestro driver
    - Geert Uytterhoeven: more m68k updates
    - Andrey Savochkin: eepro100 update
    - Dag Brattli: irda update
    - Johannes Erdfelt: USB update

 - pre1: (for ISDN synchronization _ONLY_! Not complete!)
    - Byron Stanoszek: correct decimal precision for CPU MHz in
      /proc/cpuinfo
    - Ollie Lho: SiS pirq routing.
    - Andries Brouwer: isofs cleanups
    - Matt Kraai: /proc read() on directories should return EISDIR, not EINVAL
    - me: be stricter about what we accept as a PCI bridge setup.
    - me: always set PCI interrupts to be level-triggered when we enable them.
    - me: updated PageDirty and swap cache handling
    - Peter Anvin: update A20 code to work without keyboard controller
    - Kai Germaschewski: ISDN updates
    - Russell King: ARM updates
    - Geert Uytterhoeven: m68k updates

-
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-28  3:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-28  2:45 Linus Torvalds [this message]
2000-11-28  2:55 ` Linus daughter John B. Jacobsen
2000-11-28 12:13   ` George R. Kasica
2000-11-28  3:46 ` test12-pre2 Neil Brown
2000-11-28  3:53   ` test12-pre2 Alan Cox
2000-11-28  4:38   ` test12-pre2 Linus Torvalds
2000-11-28  4:17 ` test12-pre2 Mohammad A. Haque
2000-11-29  2:30 ` test12-pre2 Wakko Warner
     [not found]   ` <20001129121504.A1794@jurassic.park.msu.ru>
     [not found]     ` <20001129072631.A4193@animx.eu.org>
     [not found]       ` <20001129165011.A2205@jurassic.park.msu.ru>
2000-11-29 17:15         ` test12-pre2 Wakko Warner
2000-11-30 17:24   ` [patch] test12-pre2 Ivan Kokshaysky
     [not found]     ` <20001201171033.A10915@animx.eu.org>
     [not found]       ` <20001202162614.A2738@jurassic.park.msu.ru>
2000-12-03 19:46         ` Wakko Warner
2000-11-29 14:35 ` test12-pre2 Ingo Oeser
2000-11-29 16:16   ` test12-pre2 Kai Germaschewski

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=Pine.LNX.4.10.10011271838080.15454-100000@penguin.transmeta.com \
    --to=torvalds@transmeta.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;
as well as URLs for NNTP newsgroup(s).