From: Erik Andersen <andersen@codepoet.org>
To: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: test11-pre6
Date: Fri, 17 Nov 2000 00:30:46 -0700 [thread overview]
Message-ID: <20001117003046.A16984@codepoet.org> (raw)
In-Reply-To: <Pine.LNX.4.10.10011161832460.803-100000@penguin.transmeta.com> <20001116204510.B15356@vger.timpanogas.org>
In-Reply-To: <20001116204510.B15356@vger.timpanogas.org>; from jmerkey@vger.timpanogas.org on Thu, Nov 16, 2000 at 08:45:10PM -0700
On Thu Nov 16, 2000 at 08:45:10PM -0700, Jeff V. Merkey wrote:
> >
> > - pre6:
> > - Intel: start to add Pentium IV specific stuff (128-byte cacheline
> > etc)
> > - David Miller: search-and-destroy places that forget to mark us
> > running after removing us from a wait-queue.
> Level I
> > - me: NFS client write-back ref-counting SMP instability.
> > - me: fix up non-exclusive waiters
> > - Trond Myklebust: Be more careful about SMP in NFS and RPC code
> > - Trond Myklebust: inode attribute update race fix
> > - Charles White: don't do unaligned accesses in cpqarray driver.
> > - Jeff Garzik: continued driver cleanup and fixes
> > - Peter Anvin: integrate more of the Intel patches.
> > - Robert Love: add i815 signature to the intel AGP support
> > - Rik Faith: DRM update to make it easier to sync up 2.2.x
> > - David Woodhouse: make old 16-bit pcmcia controllers work
> > again (ie i82365 and TCIC)
> Level I
>
> The list is getting shorter.
WTF is "Level I" supposed to mean and why have you inserted it seemingly
randomly into the changelog and why are you telling the world about it? I've
seen you do this several times and I am completely baffled. Surely you have
some reason for wanting to share?
-Erik
--
Erik B. Andersen email: andersee@debian.org
--This message was written using 73% post-consumer electrons--
-
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/
next prev parent reply other threads:[~2000-11-17 7:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-17 2:33 test11-pre6 Linus Torvalds
2000-11-17 3:45 ` test11-pre6 Jeff V. Merkey
2000-11-17 7:30 ` Erik Andersen [this message]
2000-11-17 8:30 ` test11-pre6 David Lang
2000-11-17 8:53 ` test11-pre6 Jeff V. Merkey
2000-11-17 16:11 ` test11-pre6 Mike A. Harris
2000-11-17 7:33 ` test11-pre6 Chris Wedgwood
2000-11-17 11:57 ` test11-pre6 Jeff Garzik
2000-11-17 9:06 ` [PATCH-2.4.0-10] vgacon.c jani
2000-11-17 10:37 ` test11-pre6 David Woodhouse
2000-11-17 11:51 ` [patch] hotplug fixes test11-pre6 Tigran Aivazian
-- strict thread matches above, loose matches on Subject: below --
2000-11-17 3:02 test11-pre6 Ying Chen/Almaden/IBM
2000-11-17 3:09 ` test11-pre6 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=20001117003046.A16984@codepoet.org \
--to=andersen@codepoet.org \
--cc=jmerkey@vger.timpanogas.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