Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753525AbbFRHxG (ORCPT ); Thu, 18 Jun 2015 03:53:06 -0400 Received: from mail-lb0-f171.google.com ([209.85.217.171]:35304 "EHLO mail-lb0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752667AbbFRHw6 (ORCPT ); Thu, 18 Jun 2015 03:52:58 -0400 MIME-Version: 1.0 Reply-To: mtk.manpages@gmail.com In-Reply-To: References: From: "Michael Kerrisk (man-pages)" Date: Thu, 18 Jun 2015 09:52:36 +0200 Message-ID: Subject: Re: UAPI headers including non-UAPI headers by accident? To: Andy Lutomirski Cc: "linux-kernel@vger.kernel.org" , Linux API , David Woodhouse Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 861 Lines: 27 [CC += David] On 2 June 2015 at 18:36, Andy Lutomirski wrote: > include/uapi/linux/signal.h starts with: > > #ifndef _UAPI_LINUX_SIGNAL_H > #define _UAPI_LINUX_SIGNAL_H > > #include > #include > > This causes it to include , which is not the same thing > as . Changing that will break userspace use of > this header, though, as the uapi/ won't get removed. > > What's the correct fix? This is causing trouble with a UML build for me. Perhaps David has some insight, since he architected the original UAPI split. Cheers, Michael -- 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/