On Sat, Aug 19, 2017 at 3:49 AM, Masahiro Yamada
[off-list ref] wrote:

*.tab.[ch] files are artifacts generated from *.y by using bison.
Instead of running bison, we conventionally version-control
*.tab.[ch]_shipped files and copy them to *.tab.[ch] during build.

It is true that this approach can minimize external tool dependency,
but we need to update the shipped files from time to time.  This
commit switches to build-time generation of the intermediate C files.

When do we need to update them?

Signed-off-by: Masahiro Yamada <redacted>
---

 Documentation/process/changes.rst    |   12 +
 scripts/Makefile.lib                 |   14 +-
 scripts/dtc/Makefile                 |    9 +-
 scripts/dtc/dtc-parser.tab.c_shipped | 2303 -------------------------------
 scripts/dtc/dtc-parser.tab.h_shipped |  125 --

The script to import dtc normally creates these. If you change this,
please make sure the script still works.

 scripts/genksyms/Makefile            |    5 +-
 scripts/genksyms/parse.tab.c_shipped | 2394 --------------------------------
 scripts/genksyms/parse.tab.h_shipped |  119 --
 scripts/kconfig/Makefile             |    2 +-
 scripts/kconfig/zconf.tab.c_shipped  | 2471 ----------------------------------
 10 files changed, 24 insertions(+), 7430 deletions(-)
 delete mode 100644 scripts/dtc/dtc-parser.tab.c_shipped
 delete mode 100644 scripts/dtc/dtc-parser.tab.h_shipped
 delete mode 100644 scripts/genksyms/parse.tab.c_shipped
 delete mode 100644 scripts/genksyms/parse.tab.h_shipped
 delete mode 100644 scripts/kconfig/zconf.tab.c_shipped

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html