From: Willy Tarreau <wtarreau@free.fr>
To: Michael Rothwell <rothwell@holly-springs.nc.us>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: Linux 2.2.19pre1 : procfs api
Date: Sat, 16 Dec 2000 08:05:24 +0100 (MET) [thread overview]
Message-ID: <976950324.3a3b1434d9519@imp.free.fr> (raw)
In-Reply-To: <E1470sk-0001kp-00@the-village.bc.nu> <3A3A7915.5060006@holly-springs.nc.us>
In-Reply-To: <3A3A7915.5060006@holly-springs.nc.us>
Hello Michael, I wonder about this patch which only fixes an Id/author but no
code. It may be perfectly normal, but could also come from a mangled file in
one of your trees. Just for info anyway...
Cheers,
Willy
> diff -r -u -x CVS -x *.o linux-2.2.18pre25-VIRGIN/fs/proc/openpromfs.c
zinux/fs/proc/openpromfs.c
> --- linux-2.2.18pre25-VIRGIN/fs/proc/openpromfs.c Fri Dec 8 14:57:07 2000
> +++ zinux/fs/proc/openpromfs.c Fri Dec 8 15:08:59 2000
> @@ -1,4 +1,4 @@
> -/* $Id: openpromfs.c,v 1.33 1999/04/28 11:57:33 davem Exp $
> +/* $Id: openpromfs.c,v 1.1.1.1 2000/12/08 20:08:59 zapman Exp $
> * openpromfs.c: /proc/openprom handling routines
> *
> * Copyright (C) 1996-1998 Jakub Jelinek (jj@sunsite.mff.cuni.cz)
-
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-12-16 7:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-15 19:51 Linux 2.2.19pre1 Alan Cox
2000-12-15 20:03 ` [PATCH] Re: Linux 2.2.19pre1 : procfs api Michael Rothwell
2000-12-16 7:05 ` Willy Tarreau [this message]
2000-12-16 14:34 ` Michael Rothwell
2000-12-15 20:05 ` [PATCH] Re: Linux 2.2.19pre1 64-bit printk Michael Rothwell
2000-12-15 20:56 ` Linux 2.2.19pre1 Tom Rini
2000-12-16 14:13 ` Andrea Arcangeli
2000-12-16 16:19 ` Alan Cox
2000-12-16 16:26 ` Andrea Arcangeli
2000-12-16 21:40 ` Andre Hedrick
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=976950324.3a3b1434d9519@imp.free.fr \
--to=wtarreau@free.fr \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rothwell@holly-springs.nc.us \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.