From: Olaf Titz <olaf@bigred.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.19: OOPS in cat /proc/fs/nfs/exports
Date: Wed, 06 Dec 2006 23:58:01 +0100 [thread overview]
Message-ID: <E1Gs5iD-0001m0-00@bigred.inka.de> (raw)
In-Reply-To: E1Gripc-0004KC-00@bigred.inka.de
> Will try your patch tomorrow.
...which does not change anything. (As expected.)
Olaf
next prev parent reply other threads:[~2006-12-06 23:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 19:14 2.6.19: OOPS in cat /proc/fs/nfs/exports Olaf Titz
2006-12-05 4:24 ` Neil Brown
2006-12-05 22:32 ` Olaf Titz
2006-12-06 22:58 ` Olaf Titz [this message]
2006-12-07 1:38 ` Neil Brown
2006-12-10 22:04 ` Olaf Titz
2006-12-10 22:36 ` Neil Brown
2006-12-19 21:23 ` Olaf Titz
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=E1Gs5iD-0001m0-00@bigred.inka.de \
--to=olaf@bigred.inka.de \
--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