From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: [PATCH] Break out types from to . Date: Sat, 3 Jul 2010 11:00:43 +0200 Message-ID: <201007031100.43158.arnd@arndb.de> References: <201007021811.04197.arnd@arndb.de> <4C2E3F1F.3010202@tilera.com> <20100702204817.GB5842@parisc-linux.org> Mime-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from moutng.kundenserver.de ([212.227.17.9]:62585 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750814Ab0GCJBD (ORCPT ); Sat, 3 Jul 2010 05:01:03 -0400 In-Reply-To: <20100702204817.GB5842@parisc-linux.org> Sender: linux-arch-owner@vger.kernel.org List-ID: To: Matthew Wilcox Cc: Chris Metcalf , linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org On Friday 02 July 2010 22:48:17 Matthew Wilcox wrote: > I wouldn't mind seeing kvm_types.h, rwlock_types.h and spinlock_types.h > merged into types.h, personally. They're all pretty fundamental kernel > kind of types. It's a matter of taste, and I'm not particularly fussed > one way or the other. > > mm_types.h is complex and full of mm-specific information, so keeping > it separate makes sense to me. > > I just object to the unnecessary creation of tiny files like this. > Which is how we ended up with atomic_t and atomic64_t in there in the > first place :-) Ah, I didn't notice you had moved the atomic types in there. I agree that the list types are in the same general category and it makes sense to treat them the same way. For rwlock_types.h and spinlock_types.h, I think including them in types.h would really cause too much other crap to be pulled in through lockdep and other things we might need in there in the future, which would in turn cause the same problems with types.h that Chris is trying to avoid in the first place by moving stuff out of list.h. Arnd