[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140930073829.GA32613@infradead.org>
Date: Tue, 30 Sep 2014 00:38:29 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Joe Perches <joe@...ches.com>
Cc: Nicholas Mc Guire <der.herr@...r.at>,
Randy Dunlap <rdunlap@...radead.org>,
Michael Elizabeth Chastain <mec@...ut.net>,
Kai Germaschewski <kai@....ruhr-uni-bochum.de>,
Sam Ravnborg <sam@...nborg.org>,
Jan Engelhardt <jengelh@....de>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] description and restrictions of _shipped
On Sun, Sep 28, 2014 at 11:16:21AM -0700, Joe Perches wrote:
> *_shipped files are not just binary.
>
> Perhaps these are better described as "auto-generated" files.
The use case for them is to ship generated files that require tools we
don't want to require for "just" a kernel build. The only exception
is ./drivers/net/wan/wanxlfw.inc_shipped, which really should use
the firmware loader instead, or given that the driver has seen no
work since git history probably just be removed.
So please remove the bullshit language that seems to imply allowing to ship
binaries code, and resend the patch.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists