From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Shaya Potter <spotter@cs.columbia.edu>
Cc: Linux Filesystem Development <linux-fsdevel@vger.kernel.org>
Subject: Re: nfs and printk's
Date: Thu, 04 Nov 2004 10:17:38 -0800 [thread overview]
Message-ID: <1099592258.11255.6.camel@lade.trondhjem.org> (raw)
In-Reply-To: <1099535189.27369.4.camel@dent>
on den 03.11.2004 Klokka 21:26 (-0500) skreiv Shaya Potter:
> is there any reason why printk's I'm putting in nfs_readdir() don't
> appear at all (when other's, such as in nfsd) do appear. If it matters,
> this is a 2.4.23 kernel. Is printk somehow defined out in fs/nfs/ ?
printk() should always work. Just make sure that you are not confusing
it with "dprintk()".
Cheers,
Trond
--
Trond Myklebust <trond.myklebust@fys.uio.no>
next prev parent reply other threads:[~2004-11-04 18:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 2:26 nfs and printk's Shaya Potter
2004-11-04 18:17 ` Trond Myklebust [this message]
2004-11-04 18:20 ` Shaya Potter
2004-11-04 18:19 ` Randy.Dunlap
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=1099592258.11255.6.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=linux-fsdevel@vger.kernel.org \
--cc=spotter@cs.columbia.edu \
/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).