From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shaya Potter Subject: nfs and printk's Date: Wed, 03 Nov 2004 21:26:29 -0500 Message-ID: <1099535189.27369.4.camel@dent> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from opus.cs.columbia.edu ([128.59.20.100]:48299 "EHLO opus.cs.columbia.edu") by vger.kernel.org with ESMTP id S262084AbUKDC0p (ORCPT ); Wed, 3 Nov 2004 21:26:45 -0500 Received: from 192.168.0.100 (user-0ccem0v.cable.mindspring.com [24.199.88.31]) (authenticated bits=0) by opus.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id iA42QcMd013044 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Wed, 3 Nov 2004 21:26:39 -0500 (EST) To: linux-fsdevel@vger.kernel.org Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org 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/ ? thanks, shaya