From: Steve Dickson <SteveD@redhat.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Andrew Ryan <andrewr@collab.net>, nfs@lists.sourceforge.net
Subject: Re: oops in FC1 update kernel, in refile_inode
Date: Wed, 28 Apr 2004 11:36:09 -0400 [thread overview]
Message-ID: <408FCF69.7050806@RedHat.com> (raw)
In-Reply-To: <1083016592.15282.107.camel@lade.trondhjem.org>
Trond Myklebust wrote:
>Steve, could you make sure that patch makes it into any future errata
>kernels?
>
>
Yes... I will look into it...
Thanks for pointing this out!
SteveD.
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2004-04-28 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 21:26 oops in FC1 update kernel, in refile_inode Andrew Ryan
2004-04-26 21:56 ` Trond Myklebust
2004-04-28 15:36 ` Steve Dickson [this message]
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=408FCF69.7050806@RedHat.com \
--to=steved@redhat.com \
--cc=andrewr@collab.net \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.