[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160822123745.7921a88d@xeon-e3>
Date: Mon, 22 Aug 2016 12:37:45 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Mikko Rapeli <mikko.rapeli@....fi>
Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH v05 21/72] include/uapi/linux/if_pppox.h: include
linux/if.h
On Mon, 22 Aug 2016 20:32:38 +0200
Mikko Rapeli <mikko.rapeli@....fi> wrote:
> Fixes userspace compilation error:
>
> error: ‘IFNAMSIZ’ undeclared here (not in a function)
>
> Signed-off-by: Mikko Rapeli <mikko.rapeli@....fi>
> ---
> include/uapi/linux/if_pppox.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/uapi/linux/if_pppox.h b/include/uapi/linux/if_pppox.h
> index e128769..473c3c4 100644
> --- a/include/uapi/linux/if_pppox.h
> +++ b/include/uapi/linux/if_pppox.h
> @@ -21,6 +21,7 @@
> #include <asm/byteorder.h>
>
> #include <linux/socket.h>
> +#include <linux/if.h>
> #include <linux/if_ether.h>
> #include <linux/if_pppol2tp.h>
>
I went back to the first patch in LKML for this series.
It seems your goal is that every include file should be standalone,
i.e it must include every definition it uses.
I disagree with this premise. It just makes things harder to maintain with
no real gain for any existing program. What is the motivation for all this
useless churn? Is there some silly style rule that should be fixed instead?
Powered by blists - more mailing lists