From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Dike Subject: Re: [uml-devel] [PATCH 1/5] um/... convert #include "linux/..." to #include Date: Wed, 22 Aug 2007 12:25:08 -0400 Message-ID: <20070822162508.GA11022@c2.user-mode-linux.org> References: <1187561903.4200.138.camel@localhost> <200708211909.23027.blaisorblade@yahoo.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <200708211909.23027.blaisorblade@yahoo.it> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org To: Blaisorblade Cc: Miklos Szeredi , Maxim Krasnyansky , Jeff Dike , kernel-janitors@vger.kernel.org, Jason Lunz , Jan Beulich , vtun@office.satix.net, Jens Axboe , Stephen Hemminger , Nick Piggin , Davide Brini , Fernando Luis Vazquez Cao , virtualization@lists.osdl.org, Ingo Molnar , Alexey Dobriyan , Peter Zijlstra , user-mode-linux-devel@lists.sourceforge.net, Jeff Dike , Eduard-Gabriel Munteanu , Chris Wright , user-mode-linux-user@lists.sourceforge.net List-Id: virtualization@lists.linuxfoundation.org On Tue, Aug 21, 2007 at 07:09:17PM +0200, Blaisorblade wrote: > Wait, this patch may or may not be sane (Jeff will tell more I guess). It's sane. > Since > we use two different sets of headers (the host ones from userspace and the > guest ones from Linux), this peculiar style has been used till now to make > clear the difference (#include is used for host headers) - at least > that's what I think (I've never asked to Jeff, but I silently deduced this > and followed this practice). Yeah, and it makes some sense to extend the practice to the kernel side, where <> is used for generic headers and "" for UML-specific ones. Jeff -- Work email - jdike at linux dot intel dot com