Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758175AbYFIE70 (ORCPT ); Mon, 9 Jun 2008 00:59:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751886AbYFIE7S (ORCPT ); Mon, 9 Jun 2008 00:59:18 -0400 Received: from terminus.zytor.com ([198.137.202.10]:33900 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751846AbYFIE7S (ORCPT ); Mon, 9 Jun 2008 00:59:18 -0400 Message-ID: <484CB475.7070707@zytor.com> Date: Sun, 08 Jun 2008 21:41:25 -0700 From: "H. Peter Anvin" User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: OGAWA Hirofumi CC: "H. Peter Anvin" , Adrian Bunk , =?UTF-8?B?IlMuw4dhxJ9sYXIgT251ciI=?= , linux-kernel@vger.kernel.org, Linus Torvalds , Frank Seidel , =?UTF-8?B?T251ciBLw7zDp8O8aw==?= , Andrew Morton Subject: Re: [2.6.26 patch] fat_valid_media() isn't for userspace References: <200806082116.50355.caglar@pardus.org.tr> <20080608184310.GD4048@cs181133002.pp.htv.fi> <87prqrn4d8.fsf@duaron.myhome.or.jp> <484C83D9.2020402@kernel.org> <87iqwjmekq.fsf@duaron.myhome.or.jp> In-Reply-To: <87iqwjmekq.fsf@duaron.myhome.or.jp> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 737 Lines: 22 OGAWA Hirofumi wrote: >> >> We need to make this either __kernel_dirent_t[*] or something like >> struct __msdos_fs_dirent. > > I see. "struct dirent" in linux/dirent.h has very few users in kernel, > and probably userland doesn't use it, so it seems it should be renamed. > > Well, the patch is like this (sorry, other cleanup is in this patch)? > BTW, does typedef help it in this case? > If we're using a FAT-specific structure, then no, there is no reason to use a typedef. -hpa -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/