From: Joe Perches <joe@perches.com>
To: Nicholas Mc Guire <der.herr@hofr.at>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Michael Elizabeth Chastain <mec@shout.net>,
Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>,
Sam Ravnborg <sam@ravnborg.org>, Jan Engelhardt <jengelh@gmx.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] description and restrictions of _shipped
Date: Sun, 28 Sep 2014 11:16:21 -0700 [thread overview]
Message-ID: <1411928181.21874.19.camel@joe-AO725> (raw)
In-Reply-To: <20140928175513.GA5517@opentech.at>
On Sun, 2014-09-28 at 19:55 +0200, Nicholas Mc Guire wrote:
> This patch adds a section on handling of _shipped files
> and their limitations.
Good idea but:
> While it is not actually the right place to rant about binary
> modules, it probably would also be bad not to clearly state that
> this option is not preferred.
[]
> diff --git a/Documentation/kbuild/makefiles.txt b/Documentation/kbuild/makefiles.txt
[]
> @@ -19,6 +19,7 @@ This document describes the Linux kernel Makefiles.
> --- 3.10 Special Rules
> --- 3.11 $(CC) support functions
> --- 3.12 $(LD) support functions
> + --- 3.13 _shipped binary blobs
*_shipped files are not just binary.
Perhaps these are better described as "auto-generated" files.
The _shipped files in drivers/scsi/aic7xxx/ should probably
just be renamed.
$ git ls-files -- "*_shipped"
arch/arm/crypto/aesbs-core.S_shipped
arch/powerpc/platforms/cell/spufs/spu_restore_dump.h_shipped
arch/powerpc/platforms/cell/spufs/spu_save_dump.h_shipped
drivers/net/wan/wanxlfw.inc_shipped
drivers/scsi/53c700_d.h_shipped
drivers/scsi/aic7xxx/aic79xx_reg.h_shipped
drivers/scsi/aic7xxx/aic79xx_reg_print.c_shipped
drivers/scsi/aic7xxx/aic79xx_seq.h_shipped
drivers/scsi/aic7xxx/aic7xxx_reg.h_shipped
drivers/scsi/aic7xxx/aic7xxx_reg_print.c_shipped
drivers/scsi/aic7xxx/aic7xxx_seq.h_shipped
drivers/tty/vt/defkeymap.c_shipped
scripts/dtc/dtc-lexer.lex.c_shipped
scripts/dtc/dtc-parser.tab.c_shipped
scripts/dtc/dtc-parser.tab.h_shipped
scripts/genksyms/keywords.hash.c_shipped
scripts/genksyms/lex.lex.c_shipped
scripts/genksyms/parse.tab.c_shipped
scripts/genksyms/parse.tab.h_shipped
scripts/kconfig/zconf.hash.c_shipped
scripts/kconfig/zconf.lex.c_shipped
scripts/kconfig/zconf.tab.c_shipped
next prev parent reply other threads:[~2014-09-28 18:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-28 17:55 Nicholas Mc Guire
2014-09-28 18:16 ` Joe Perches [this message]
2014-09-30 7:38 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1411928181.21874.19.camel@joe-AO725 \
--to=joe@perches.com \
--cc=der.herr@hofr.at \
--cc=jengelh@gmx.de \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mec@shout.net \
--cc=rdunlap@infradead.org \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®