From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yura Pakhuchiy Subject: Re: Print inode number if name can not be represented in the local charset Date: Thu, 21 Jul 2005 16:27:34 +0300 Message-ID: <1121952454.2027.25.camel@chaos.void> References: <1120183436.2758.2.camel@chaos.void> <1121952107.17221.84.camel@imp.csi.cam.ac.uk> Reply-To: Yura Pakhuchiy Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org Return-path: Received: from www.iptel.by ([80.94.225.5]:46020 "EHLO iptel.by") by vger.kernel.org with ESMTP id S261782AbVGUN0K (ORCPT ); Thu, 21 Jul 2005 09:26:10 -0400 To: Anton Altaparmakov In-Reply-To: <1121952107.17221.84.camel@imp.csi.cam.ac.uk> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, 2005-07-21 at 14:21 +0100, Anton Altaparmakov wrote: > On Fri, 2005-07-01 at 05:03 +0300, Yura Pakhuchiy wrote: > > This patch changes message type from ntfs_error to ntfs_debug in the > > unistr.c when unicode filename contains characters that can not be > > converted into the local charset, because it's not useful for user and > > actually it's not a error. Instead of this print warning in dir.c, this > > warning includes inode number for further investigation (e.g. with > > ntfsinfo). > > I applied something simillar to your patch to my private tree so it will > be in the next ntfs release. Thanks for the patch. Great! Thanks. -- Best regards, Yura