From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-qg0-x22c.google.com ([2607:f8b0:400d:c04::22c]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1aO5Nr-00083h-OC for barebox@lists.infradead.org; Tue, 26 Jan 2016 15:18:20 +0000 Received: by mail-qg0-x22c.google.com with SMTP id b35so140523996qge.0 for ; Tue, 26 Jan 2016 07:17:59 -0800 (PST) MIME-Version: 1.0 From: Yegor Yefremov Date: Tue, 26 Jan 2016 16:17:39 +0100 Message-ID: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "barebox" Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Linux headers To: barebox AFAIK include/linux/barebox-wrapper.h was introduced to simplify Linux driver porting. During my current effort to port SquashFS driver I had to repeatedly remove such includes like: #include #include #include #include #include #include and so on. Would it be better to provide such headers even if they would almost always include dummy code? Though it would pollute the include folder somehow, but it will be easier to port/sync Linux drivers and it will help to preserve the structure of this drivers. What do you think about this? Yegor _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox