Re: [Cocci] [PATCH] coccinelle: misc: add excluded_middle.cocci script

On Wed, Sep 2, 2020 at 8:19 AM Denis Efremov wrote: > > Check for "!A || A && B" condition. It's equivalent to > "!A || B" condition. > > Signed-off-by: Denis Efremov > --- > scripts/coccinelle/misc/excluded_middle.cocci | 40 +++ > 1 file changed, 40 insertions(+) > create

Re: [PATCH] kbuild: pkg: make out-of-tree rpm/deb-pkg build immediately fail

"; \ > + echo >&2 " kernel source tree. Don't set KBUILD_OUTPUT, or use the"; > \ > + echo >&2 " binrpm-pkg or bindeb-pkg target instead."; \ > + echo >&2; \ > false; \ > fi ; \ > $(srctree)/scripts/setlocalversion --save-scmversion; \ > -- > 2.7.4 > Tested-by: Jim Davis <jim.ep...@gmail.com> -- Jim

Re: [PATCH] kbuild: pkg: make out-of-tree rpm/deb-pkg build immediately fail

m-pkg or bindeb-pkg target instead."; \ > + echo >&2; \ > + echo >&2 " ERROR:"; \ > + echo >&2 " Building source tarball is not possible outside the"; \ > + echo >&2 " kernel source tree. Don't set KBUILD_OUTPUT, or use the"; > \ > + echo >&2 " binrpm-pkg or bindeb-pkg target instead."; \ > + echo >&2; \ > false; \ > fi ; \ > $(srctree)/scripts/setlocalversion --save-scmversion; \ > -- > 2.7.4 > Tested-by: Jim Davis -- Jim

Re: [PATCH v3] scripts/package: snap-pkg target

On Tue, Dec 5, 2017 at 4:43 AM, Paolo Pisati wrote: >> I noticed that if I tried to make snap-pkg with the O=/some/dir option >> the tar step failed but the rest of the build continued, and seems to >> have finished successfully. Should the snap-pkg target stop after

Re: [PATCH v3] scripts/package: snap-pkg target

On Tue, Dec 5, 2017 at 4:43 AM, Paolo Pisati wrote: >> I noticed that if I tried to make snap-pkg with the O=/some/dir option >> the tar step failed but the rest of the build continued, and seems to >> have finished successfully. Should the snap-pkg target stop after a >> tar failure? > > That

Re: [PATCH v3] scripts/package: snap-pkg target

On Wed, Nov 29, 2017 at 10:05 AM, Paolo Pisati wrote: > On Wed, Nov 29, 2017 at 8:33 AM, Masahiro Yamada > wrote: >> >> Worked for me too, >> after updating snapcraft. >> >> >> Is it really impossible to check the snapcraft version? >>

Re: [PATCH v3] scripts/package: snap-pkg target

On Wed, Nov 29, 2017 at 10:05 AM, Paolo Pisati wrote: > On Wed, Nov 29, 2017 at 8:33 AM, Masahiro Yamada > wrote: >> >> Worked for me too, >> after updating snapcraft. >> >> >> Is it really impossible to check the snapcraft version? >> What is the minimum version? 2.35 ? > > The minimum

Re: [PATCH v3] scripts/package: snap-pkg target

On Tue, Nov 28, 2017 at 10:14 AM, Paolo Pisati <paolo.pis...@canonical.com> wrote: > On Mon, Nov 27, 2017 at 7:33 PM, Jim Davis <jim.ep...@gmail.com> wrote: >> >> With this patch applied to the 4.14 kernel source, and running make >> snap-pkg on a Ubuntu 16.0

Re: [PATCH v3] scripts/package: snap-pkg target

On Tue, Nov 28, 2017 at 10:14 AM, Paolo Pisati wrote: > On Mon, Nov 27, 2017 at 7:33 PM, Jim Davis wrote: >> >> With this patch applied to the 4.14 kernel source, and running make >> snap-pkg on a Ubuntu 16.04 VM with the latest 16.04 kernel config >> file, I ran

Re: [PATCH] builddeb: introduce variables for control-file customization

On Mon, Nov 27, 2017 at 9:13 AM, Henning Schild wrote: > The debian packages coming out of "make *deb-pkg" lack some critical > information in the control-files e.g. the "Depends:" field. If one > tries to install a fresh system with such a "linux-image" debootstrap or

Re: [PATCH] builddeb: introduce variables for control-file customization

On Mon, Nov 27, 2017 at 9:13 AM, Henning Schild wrote: > The debian packages coming out of "make *deb-pkg" lack some critical > information in the control-files e.g. the "Depends:" field. If one > tries to install a fresh system with such a "linux-image" debootstrap or > multistrap might try to

Re: [PATCH v3] scripts/package: snap-pkg target

On Mon, Nov 27, 2017 at 4:07 AM, Paolo Pisati wrote: > Following in footsteps of other targets like 'deb-pkg, 'rpm-pkg' and > 'tar-pkg', > this patch adds a 'snap-pkg' target for the creation of a Linux kernel snap > package using the kbuild infrastructure. With this

Re: [PATCH v3] scripts/package: snap-pkg target

On Mon, Nov 27, 2017 at 4:07 AM, Paolo Pisati wrote: > Following in footsteps of other targets like 'deb-pkg, 'rpm-pkg' and > 'tar-pkg', > this patch adds a 'snap-pkg' target for the creation of a Linux kernel snap > package using the kbuild infrastructure. With this patch applied to the 4.14

Re: [PATCH 2/7] kbuild: Add P= command line flag to run checkpatch

On Tue, Nov 21, 2017 at 1:10 AM, Knut Omang wrote: > Would you like to keep the checkpatch changes in some form, or would you > rather > see everything happening in the wrapper? I don't have a strong preference one way or another, but keeping everything in a wrapper

Re: [PATCH 2/7] kbuild: Add P= command line flag to run checkpatch

On Tue, Nov 21, 2017 at 1:10 AM, Knut Omang wrote: > Would you like to keep the checkpatch changes in some form, or would you > rather > see everything happening in the wrapper? I don't have a strong preference one way or another, but keeping everything in a wrapper script might be easier if

Re: [PATCH 2/7] kbuild: Add P= command line flag to run checkpatch

On Mon, Nov 20, 2017 at 2:22 PM, Luc Van Oostenryck wrote: > Should it be possible to somehow keep the distinction between > the flags coming from KBUILD_CFLAGS and the pure CHECKFLAGS? Well, the practical problem seems to be that $(CHECK) is called in

Re: [PATCH 2/7] kbuild: Add P= command line flag to run checkpatch

On Mon, Nov 20, 2017 at 2:22 PM, Luc Van Oostenryck wrote: > Should it be possible to somehow keep the distinction between > the flags coming from KBUILD_CFLAGS and the pure CHECKFLAGS? Well, the practical problem seems to be that $(CHECK) is called in scripts/Makefile.build with both

Re: [PATCH 2/7] kbuild: Add P= command line flag to run checkpatch

On Mon, Nov 20, 2017 at 9:18 AM, Masahiro Yamada wrote: > > I am unhappy about adding a new interface > for each checker. > > The default of CHECK is "sparse", but > users can override it to use another checker. > > > > As Decumentation/dev-tools/coccinelle.rst

Re: [PATCH 2/7] kbuild: Add P= command line flag to run checkpatch

On Mon, Nov 20, 2017 at 9:18 AM, Masahiro Yamada wrote: > > I am unhappy about adding a new interface > for each checker. > > The default of CHECK is "sparse", but > users can override it to use another checker. > > > > As Decumentation/dev-tools/coccinelle.rst says, > if you want to use

Re: [PATCH] coccinelle: fix verbose message about .cocci file being run

On Wed, Oct 25, 2017 at 9:55 PM, Masahiro Yamada wrote: > If you run coccicheck with V=1 and COCCI=, you will see a strange > path to the semantic patch file. For example, run the following: > > $ make V=1 COCCI=scripts/coccinelle/free/kfree.cocci coccicheck > [

Re: [PATCH] coccinelle: fix verbose message about .cocci file being run

On Wed, Oct 25, 2017 at 9:55 PM, Masahiro Yamada wrote: > If you run coccicheck with V=1 and COCCI=, you will see a strange > path to the semantic patch file. For example, run the following: > > $ make V=1 COCCI=scripts/coccinelle/free/kfree.cocci coccicheck > [ snip ] > The semantic patch

make linkcheckdocs error with 4.13-rc7

On my Fedora 26 desktop (with Sphinx 1.6.3), make linkcheckdocs is failing with InputError: [Errno 2] No such file or directory: '/data/linux-rc/Documentation/output/cec.h.rst'. reST markup error: /data/linux-rc/Documentation/media/uapi/cec/cec-header.rst:9: (SEVERE/4) Problems with

make linkcheckdocs error with 4.13-rc7

On my Fedora 26 desktop (with Sphinx 1.6.3), make linkcheckdocs is failing with InputError: [Errno 2] No such file or directory: '/data/linux-rc/Documentation/output/cec.h.rst'. reST markup error: /data/linux-rc/Documentation/media/uapi/cec/cec-header.rst:9: (SEVERE/4) Problems with

Re: make clean all broken with -j? + question regarding modpost

On Thu, Aug 10, 2017 at 11:28 AM, Randy Dunlap wrote: > [adding linux-kbuild] > > On 08/10/2017 08:42 AM, Thomas Meyer wrote: >> Hi, >> >> 1.) make with multiple targets >> >> When running >> $ make -j4 clean all >> I get error from make (probably in

Re: make clean all broken with -j? + question regarding modpost

On Thu, Aug 10, 2017 at 11:28 AM, Randy Dunlap wrote: > [adding linux-kbuild] > > On 08/10/2017 08:42 AM, Thomas Meyer wrote: >> Hi, >> >> 1.) make with multiple targets >> >> When running >> $ make -j4 clean all >> I get error from make (probably in scripts/Makefile.modbuiltin): With 4.13-rc4 I

make pdfdocs problem with 4.13-rc4

On my Fedora 26 workstation, with the latest patches, running make pdfdocs stops with [jim@krebstar ~]$ tail /tmp/make-pdfdocs.out Underfull \hbox (badness 1) in paragraph at lines 3980--3983 []\EU1/DejaVuSans(0)/m/n/10 Threshold below [31] ! Missing \endgroup inserted.

make pdfdocs problem with 4.13-rc4

On my Fedora 26 workstation, with the latest patches, running make pdfdocs stops with [jim@krebstar ~]$ tail /tmp/make-pdfdocs.out Underfull \hbox (badness 1) in paragraph at lines 3980--3983 []\EU1/DejaVuSans(0)/m/n/10 Threshold below [31] ! Missing \endgroup inserted.

Re: [PATCH] scripts/package: snap-pkg target

On Mon, Jul 10, 2017 at 11:13 PM, Paolo Pisati <paolo.pis...@canonical.com> wrote: > On Mon, Jul 10, 2017 at 6:46 PM, Jim Davis <jim.ep...@gmail.com> wrote: >>> >>> For more information on snap packages: https://snapcraft.io/docs/ >> >> Is this so

Re: [PATCH] scripts/package: snap-pkg target

On Mon, Jul 10, 2017 at 11:13 PM, Paolo Pisati wrote: > On Mon, Jul 10, 2017 at 6:46 PM, Jim Davis wrote: >>> >>> For more information on snap packages: https://snapcraft.io/docs/ >> >> Is this something a user could do with the existing deb tar

Re: [PATCH v2 00/53] Get rid of Docbook

On Thu, Jul 6, 2017 at 1:54 AM, Markus Heiser wrote: > 52b3f23 Docs: clean up some DocBook loose ends Speaking of minor loose ends, make SPHINXDIRS=userspace-api pdfdocs works -- though now that it's all sphinx, wouldn't just DIRS be better? -- and make

Re: [PATCH v2 00/53] Get rid of Docbook

On Thu, Jul 6, 2017 at 1:54 AM, Markus Heiser wrote: > 52b3f23 Docs: clean up some DocBook loose ends Speaking of minor loose ends, make SPHINXDIRS=userspace-api pdfdocs works -- though now that it's all sphinx, wouldn't just DIRS be better? -- and make DOCBOOKS=userspace-api pdfdocs still

Re: [PATCH RFC] scripts/sphinx-pre-install: add a script to check Sphinx install

On Fri, Jul 14, 2017 at 10:35 AM, Markus Heiser wrote: > > > Ok, this won't solve TeX installation problems of Linux distros, Which seems to be the thorniest problem. It's one thing to identify which sphinx versions work, and another to figure out which of the metric

Re: [PATCH RFC] scripts/sphinx-pre-install: add a script to check Sphinx install

On Fri, Jul 14, 2017 at 10:35 AM, Markus Heiser wrote: > > > Ok, this won't solve TeX installation problems of Linux distros, Which seems to be the thorniest problem. It's one thing to identify which sphinx versions work, and another to figure out which of the metric boatload of TeX packages

Re: [PATCH] scripts/package: snap-pkg target

On Mon, Jul 10, 2017 at 7:59 AM, Paolo Pisati wrote: > eg. Ubuntu Core, and it's subsequent upgrades. its > > For more information on snap packages: https://snapcraft.io/docs/ Is this something a user could do with the existing deb target, and then running

Re: [PATCH] scripts/package: snap-pkg target

On Mon, Jul 10, 2017 at 7:59 AM, Paolo Pisati wrote: > eg. Ubuntu Core, and it's subsequent upgrades. its > > For more information on snap packages: https://snapcraft.io/docs/ Is this something a user could do with the existing deb target, and then running deb2snap? -- Jim

Re: [PATCH v2 00/53] Get rid of Docbook

On Fri, Jun 16, 2017 at 7:03 AM, Markus Heiser wrote: > > docproc and some lines in the Makefile & .gitignore > > ./scripts/docproc.c > ./scripts/.docproc.cmd > ./scripts/Makefile > ./scripts/.gitignore With 4.12, running make xmldocs (or any other working target) and

Re: [PATCH v2 00/53] Get rid of Docbook

On Fri, Jun 16, 2017 at 7:03 AM, Markus Heiser wrote: > > docproc and some lines in the Makefile & .gitignore > > ./scripts/docproc.c > ./scripts/.docproc.cmd > ./scripts/Makefile > ./scripts/.gitignore With 4.12, running make xmldocs (or any other working target) and then "make cleandocs; git

Re: [PATCH 0/5] Make PDF builds work again

On Mon, Jul 3, 2017 at 5:44 AM, Jonathan Corbet wrote: > On Mon, 3 Jul 2017 10:25:38 +0200 > Daniel Vetter wrote: > >> Only now stumbled over the full thread, but the drm patch is already >> queued up for at least 4.13 (Dave was out and all that). I guess we

Re: [PATCH 0/5] Make PDF builds work again

On Mon, Jul 3, 2017 at 5:44 AM, Jonathan Corbet wrote: > On Mon, 3 Jul 2017 10:25:38 +0200 > Daniel Vetter wrote: > >> Only now stumbled over the full thread, but the drm patch is already >> queued up for at least 4.13 (Dave was out and all that). I guess we could >> try to cherry-pick through

make pdfdoc errors with 4.12-rc2

make pdfdocs, on my Fedora 25 desktop with the latest patches, fails with Running Sphinx v1.5.2 [...lots-o-stuff...] make PDFLATEX=xelatex LATEXOPTS="-interaction=batchmode" -C Documentation/output/./latex || exit; xelatex -interaction=batchmode 'linux-input.tex' This is XeTeX, Version

make pdfdoc errors with 4.12-rc2

make pdfdocs, on my Fedora 25 desktop with the latest patches, fails with Running Sphinx v1.5.2 [...lots-o-stuff...] make PDFLATEX=xelatex LATEXOPTS="-interaction=batchmode" -C Documentation/output/./latex || exit; xelatex -interaction=batchmode 'linux-input.tex' This is XeTeX, Version

Re: making documentation targets on v4.10 with Fedora 25

On Mon, Feb 20, 2017 at 4:20 PM, Jonathan Corbet wrote: >> Exception occurred: >> File "/usr/lib/python3.5/site-packages/docutils/writers/_html_base.py", >> line >> 671, in depart_document >> assert not self.context, 'len(context) = %s' % len(self.context) >>

Re: making documentation targets on v4.10 with Fedora 25

On Mon, Feb 20, 2017 at 4:20 PM, Jonathan Corbet wrote: >> Exception occurred: >> File "/usr/lib/python3.5/site-packages/docutils/writers/_html_base.py", >> line >> 671, in depart_document >> assert not self.context, 'len(context) = %s' % len(self.context) >> AssertionError: len(context)

Re: making documentation targets on v4.10 with Fedora 25

On Thu, Feb 23, 2017 at 2:59 AM, Jani Nikula <jani.nik...@linux.intel.com> wrote: > On Mon, 20 Feb 2017, Jim Davis <jim.ep...@gmail.com> wrote: >> For the Sphinx targets, htmldocs, pdfdocs, epubdocs, and cleandocs >> failed. cleandocs works without the O= argument, a

Re: making documentation targets on v4.10 with Fedora 25

On Thu, Feb 23, 2017 at 2:59 AM, Jani Nikula wrote: > On Mon, 20 Feb 2017, Jim Davis wrote: >> For the Sphinx targets, htmldocs, pdfdocs, epubdocs, and cleandocs >> failed. cleandocs works without the O= argument, and arguably the O= >> thing isn't very useful with

Re: making documentation targets on v4.10 with Fedora 25

On Mon, Feb 20, 2017 at 4:20 PM, Jonathan Corbet <cor...@lwn.net> wrote: > On Mon, 20 Feb 2017 12:19:24 -0700 > Jim Davis <jim.ep...@gmail.com> wrote: > >> pdfdocs (Sphinx or DocBook) has been broken for some time, while >> psdocs hasn't worked in ages. Th

Re: making documentation targets on v4.10 with Fedora 25

On Mon, Feb 20, 2017 at 4:20 PM, Jonathan Corbet wrote: > On Mon, 20 Feb 2017 12:19:24 -0700 > Jim Davis wrote: > >> pdfdocs (Sphinx or DocBook) has been broken for some time, while >> psdocs hasn't worked in ages. The errors with the Sphinx htmldocs and >> epubd

making documentation targets on v4.10 with Fedora 25

I ran a script like the one below to make the various Sphinx and DocBook documentations targets for v4.10 on my Fedora 25 desktop make O=/tmp/sphinx-out DOCBOOKS="" htmldocs make O=/tmp/sphinx-out DOCBOOKS="" latexdocs make O=/tmp/sphinx-out DOCBOOKS="" pdfdocs make O=/tmp/sphinx-out DOCBOOKS=""

making documentation targets on v4.10 with Fedora 25

I ran a script like the one below to make the various Sphinx and DocBook documentations targets for v4.10 on my Fedora 25 desktop make O=/tmp/sphinx-out DOCBOOKS="" htmldocs make O=/tmp/sphinx-out DOCBOOKS="" latexdocs make O=/tmp/sphinx-out DOCBOOKS="" pdfdocs make O=/tmp/sphinx-out DOCBOOKS=""

make pdfdocs errors with 4.10-rc8

On a Fedora 25 system, [...] build succeeded, 32 warnings. make PDFLATEX=xelatex LATEXOPTS="-interaction=batchmode" -C Documentation/output/./latex; xelatex -interaction=batchmode 'linux-user.tex' This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016) (preloaded format=xelatex) restricted

make pdfdocs errors with 4.10-rc8

On a Fedora 25 system, [...] build succeeded, 32 warnings. make PDFLATEX=xelatex LATEXOPTS="-interaction=batchmode" -C Documentation/output/./latex; xelatex -interaction=batchmode 'linux-user.tex' This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016) (preloaded format=xelatex) restricted

[PATCH] Documentation: DocBook/Makefile comment typo

Fix a se for so typo. Signed-off-by: Jim Davis <jim.ep...@gmail.com> --- Documentation/DocBook/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/DocBook/Makefile b/Documentation/DocBook/Makefile index a6eb7dcd4dd5..1f23567bf76e 100644 --- a/Documen

[PATCH] Documentation: DocBook/Makefile comment typo

Fix a se for so typo. Signed-off-by: Jim Davis --- Documentation/DocBook/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/DocBook/Makefile b/Documentation/DocBook/Makefile index a6eb7dcd4dd5..1f23567bf76e 100644 --- a/Documentation/DocBook/Makefile

[PATCH] Documentation: make Makefile.sphinx no-ops quieter

Silence the "make[1]: Nothing to be done for ..." messages for the no-op targets in Makefile.sphinx. Signed-off-by: Jim Davis <jim.ep...@gmail.com> --- Documentation/Makefile.sphinx | 4 1 file changed, 4 insertions(+) diff --git a/Documentation/Makefile.sphinx

[PATCH] Documentation: make Makefile.sphinx no-ops quieter

Silence the "make[1]: Nothing to be done for ..." messages for the no-op targets in Makefile.sphinx. Signed-off-by: Jim Davis --- Documentation/Makefile.sphinx | 4 1 file changed, 4 insertions(+) diff --git a/Documentation/Makefile.sphinx b/Documentation/Makefile.sp

make pdfdoc errors with 4.10-rc7

On a Fedora 25 system, make pdfdocs is failing with [jim@krebstar linux-rc]$ grep -v -i 'warning:' /tmp/make-pdfdocs.err /data/linux-rc/Documentation/doc-guide/sphinx.rst:110: ERROR: Unknown target name: "sphinx c domain". ./include/net/cfg80211.h:3154: ERROR: Unexpected indentation.

make pdfdoc errors with 4.10-rc7

On a Fedora 25 system, make pdfdocs is failing with [jim@krebstar linux-rc]$ grep -v -i 'warning:' /tmp/make-pdfdocs.err /data/linux-rc/Documentation/doc-guide/sphinx.rst:110: ERROR: Unknown target name: "sphinx c domain". ./include/net/cfg80211.h:3154: ERROR: Unexpected indentation.

Re: [PATCH 2/2] Documentation/kconfig: add search jump feature description

On Mon, Feb 6, 2017 at 12:46 AM, wrote: > From: Changbin Du > > Kernel menuconfig support direct jumping function from the search > result. This is a very convenient feature but not documented. So > add a short description to the kconfig

Re: [PATCH 2/2] Documentation/kconfig: add search jump feature description

On Mon, Feb 6, 2017 at 12:46 AM, wrote: > From: Changbin Du > > Kernel menuconfig support direct jumping function from the search > result. This is a very convenient feature but not documented. So > add a short description to the kconfig documentation to let more > developer know it. > >

Extra messages from Makefile.sphinx

On a sphinx-free Ubuntu system with 4.10-rc5, make installmandocs works just fine, but the garrulous Makefile.sphinx twice tells me I don't have sphinx-build installed: Documentation/Makefile.sphinx:22: The 'sphinx-build' command was not found. Make sure you have Sphinx installed and in PATH, or

Extra messages from Makefile.sphinx

On a sphinx-free Ubuntu system with 4.10-rc5, make installmandocs works just fine, but the garrulous Makefile.sphinx twice tells me I don't have sphinx-build installed: Documentation/Makefile.sphinx:22: The 'sphinx-build' command was not found. Make sure you have Sphinx installed and in PATH, or

make pdfdoc errors with v4.9

On my Ubuntu 16.04 desktop, make pdfdocs fails with Makefile:58: recipe for target 'media.pdf' failed make[2]: *** [media.pdf] Error 1 Documentation/Makefile.sphinx:79: recipe for target 'pdfdocs' failed make[1]: *** [pdfdocs] Error 2 Makefile:1450: recipe for target 'pdfdocs' failed make: ***

make pdfdoc errors with v4.9

On my Ubuntu 16.04 desktop, make pdfdocs fails with Makefile:58: recipe for target 'media.pdf' failed make[2]: *** [media.pdf] Error 1 Documentation/Makefile.sphinx:79: recipe for target 'pdfdocs' failed make[1]: *** [pdfdocs] Error 2 Makefile:1450: recipe for target 'pdfdocs' failed make: ***

Re: [PATCH RESEND 2/2] builddeb: allow building without headers/firmware packages

ename > Section: devel > @@ -380,10 +386,15 @@ Description: Linux support headers for userspace > development > This package provides userspaces headers from the Linux kernel. These > headers > are used by the installed headers for GNU glibc and other system libraries. > EOF > +fi > > if [ "$ARCH" != "um" ]; then > - create_package "$kernel_headers_packagename" "$kernel_headers_dir" > - create_package "$libc_headers_packagename" "$libc_headers_dir" > + if [ -z "$KDEB_NO_HEADERS" ]; then > + create_package "$kernel_headers_packagename" > "$kernel_headers_dir" > + fi > + if [ -z "$KDEB_NO_LIBC_HEADERS" ]; then > + create_package "$libc_headers_packagename" "$libc_headers_dir" > + fi > fi > > create_package "$packagename" "$tmpdir" > -- > Andrew Donnellan OzLabs, ADL Canberra > andrew.donnel...@au1.ibm.com IBM Australia Limited > > -- > To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html Worked fine with Ubuntu 16.04, and it's nice speedup. Tested-by: Jim Davis <jim.ep...@gmail.com> -- Jim

Re: [PATCH RESEND 2/2] builddeb: allow building without headers/firmware packages

x support headers for userspace > development > This package provides userspaces headers from the Linux kernel. These > headers > are used by the installed headers for GNU glibc and other system libraries. > EOF > +fi > > if [ "$ARCH" != "um" ]; then > - create_package "$kernel_headers_packagename" "$kernel_headers_dir" > - create_package "$libc_headers_packagename" "$libc_headers_dir" > + if [ -z "$KDEB_NO_HEADERS" ]; then > + create_package "$kernel_headers_packagename" > "$kernel_headers_dir" > + fi > + if [ -z "$KDEB_NO_LIBC_HEADERS" ]; then > + create_package "$libc_headers_packagename" "$libc_headers_dir" > + fi > fi > > create_package "$packagename" "$tmpdir" > -- > Andrew Donnellan OzLabs, ADL Canberra > andrew.donnel...@au1.ibm.com IBM Australia Limited > > -- > To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html Worked fine with Ubuntu 16.04, and it's nice speedup. Tested-by: Jim Davis -- Jim

Re: [PATCH] cxl: Fix error handling

On Wed, Nov 2, 2016 at 4:12 AM, Michael Ellerman <m...@ellerman.id.au> wrote: > Jim Davis <jim.ep...@gmail.com> writes: > >> On Sun, Oct 30, 2016 at 10:37 PM, Michael Ellerman <m...@ellerman.id.au> >> wrote: >>> More here: >>> >>>

Re: [PATCH] cxl: Fix error handling

On Wed, Nov 2, 2016 at 4:12 AM, Michael Ellerman wrote: > Jim Davis writes: > >> On Sun, Oct 30, 2016 at 10:37 PM, Michael Ellerman >> wrote: >>> More here: >>> >>> https://github.com/linuxppc/linux/wiki/Building-powerpc-kernels >> >&g

Re: [PATCH] cxl: Fix error handling

On Sun, Oct 30, 2016 at 10:37 PM, Michael Ellerman wrote: > Christophe JAILLET writes: > >> 'cxl_dev_context_init()' returns an error pointer in case of error, not >> NULL. So test it with IS_ERR. >> >> Signed-off-by: Christophe JAILLET

Re: [PATCH] cxl: Fix error handling

On Sun, Oct 30, 2016 at 10:37 PM, Michael Ellerman wrote: > Christophe JAILLET writes: > >> 'cxl_dev_context_init()' returns an error pointer in case of error, not >> NULL. So test it with IS_ERR. >> >> Signed-off-by: Christophe JAILLET >> --- >> un-compiled because I don't have the required

Re: make pdfdocs fails with v4.9-rc3

On Mon, Oct 31, 2016 at 3:41 PM, Mauro Carvalho Chehab <mche...@infradead.org> wrote: > Em Mon, 31 Oct 2016 16:40:02 -0600 > Mauro Carvalho Chehab <mche...@infradead.org> escreveu: > >> Em Mon, 31 Oct 2016 15:04:42 -0700 >> Jim Davis <jim.ep...@gmail.com>

Re: make pdfdocs fails with v4.9-rc3

On Mon, Oct 31, 2016 at 3:41 PM, Mauro Carvalho Chehab wrote: > Em Mon, 31 Oct 2016 16:40:02 -0600 > Mauro Carvalho Chehab escreveu: > >> Em Mon, 31 Oct 2016 15:04:42 -0700 >> Jim Davis escreveu: >> >> > On Mon, Oct 31, 2016 at 1:58 PM, Mauro Carvalho Cheha

Re: make pdfdocs fails with v4.9-rc3

screveu: >> >> > On Mon, 31 Oct 2016 11:51:20 -0700 >> > Jim Davis <jim.ep...@gmail.com> wrote: >> > >> > > Running make pdfdocs on a Ubuntu 16.04 system fails with >> > > >> > > Makefile:58: recipe for target 'media.pdf'

Re: make pdfdocs fails with v4.9-rc3

On Mon, Oct 31, 2016 at 1:58 PM, Mauro Carvalho Chehab wrote: > Em Mon, 31 Oct 2016 14:17:59 -0600 > Mauro Carvalho Chehab escreveu: > >> Em Mon, 31 Oct 2016 13:15:24 -0600 >> Jonathan Corbet escreveu: >> >> > On Mon, 31 Oct 2016 11:51:20 -0700 >> &g

make cleandocs missing files with v4.9-rc3

On my Ubuntu 16.04 system, make htmldocs works just fine (hurrah!) but make cleandocs misses a fair number of files: HTMLDocumentation/DocBook/index.html jim@krebstar:~/linux-rc$ make cleandocs jim@krebstar:~/linux-rc$ git status HEAD detached at v4.9-rc3 nothing to commit, working

make cleandocs missing files with v4.9-rc3

On my Ubuntu 16.04 system, make htmldocs works just fine (hurrah!) but make cleandocs misses a fair number of files: HTMLDocumentation/DocBook/index.html jim@krebstar:~/linux-rc$ make cleandocs jim@krebstar:~/linux-rc$ git status HEAD detached at v4.9-rc3 nothing to commit, working

make psdocs fails with v4.9-rc3

Running make psdocs on a Ubuntu 16.04 system fails with Documentation/DocBook/Makefile:142: recipe for target 'Documentation/DocBook/kernel-hacking.ps' failed make[1]: *** [Documentation/DocBook/kernel-hacking.ps] Error 9 Makefile:1442: recipe for target 'psdocs' failed make: *** [psdocs] Error 2

make psdocs fails with v4.9-rc3

Running make psdocs on a Ubuntu 16.04 system fails with Documentation/DocBook/Makefile:142: recipe for target 'Documentation/DocBook/kernel-hacking.ps' failed make[1]: *** [Documentation/DocBook/kernel-hacking.ps] Error 9 Makefile:1442: recipe for target 'psdocs' failed make: *** [psdocs] Error 2

make pdfdocs fails with v4.9-rc3

Running make pdfdocs on a Ubuntu 16.04 system fails with Makefile:58: recipe for target 'media.pdf' failed make[2]: *** [media.pdf] Error 1 Documentation/Makefile.sphinx:79: recipe for target 'pdfdocs' failed make[1]: *** [pdfdocs] Error 2 Makefile:1442: recipe for target 'pdfdocs' failed make:

make pdfdocs fails with v4.9-rc3

Running make pdfdocs on a Ubuntu 16.04 system fails with Makefile:58: recipe for target 'media.pdf' failed make[2]: *** [media.pdf] Error 1 Documentation/Makefile.sphinx:79: recipe for target 'pdfdocs' failed make[1]: *** [pdfdocs] Error 2 Makefile:1442: recipe for target 'pdfdocs' failed make:

Re: [PATCH 09/10] scripts/basic/fixdep: Complete error handling in print_cmdline()

On Fri, Oct 28, 2016 at 1:40 AM, SF Markus Elfring wrote: > + if (printf("cmd_%s := %s\n\n", target, cmdline) < 10) { Rather than scatter fragile magic numbers, like 10, throughout the code, if you're hell-bent on checking for printf errors you could write a

Re: [PATCH 09/10] scripts/basic/fixdep: Complete error handling in print_cmdline()

On Fri, Oct 28, 2016 at 1:40 AM, SF Markus Elfring wrote: > + if (printf("cmd_%s := %s\n\n", target, cmdline) < 10) { Rather than scatter fragile magic numbers, like 10, throughout the code, if you're hell-bent on checking for printf errors you could write a little wrapper function that

Re: [PATCH 01/10] scripts/basic/bin2c: Complete error handling in main()

On Fri, Oct 28, 2016 at 1:31 AM, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 27 Oct 2016 16:15:04 +0200 > > Return values were not checked from five calls of the function "printf". > > This issue was detected also by

Re: [PATCH 01/10] scripts/basic/bin2c: Complete error handling in main()

On Fri, Oct 28, 2016 at 1:31 AM, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 27 Oct 2016 16:15:04 +0200 > > Return values were not checked from five calls of the function "printf". > > This issue was detected also by using the Coccinelle software. > > > * Add a bit of exception

Re: Challenges around the usage of different "HOSTCFLAGS" for kernel build configuration and module generation

On Wed, Oct 19, 2016 at 12:25 AM, SF Markus Elfring wrote: > > Are you interested that a software generation parameter like "-S" > (for output of assembler source files) could be directly supported > for a special build variant? No, if you want to see the assembly

Re: Challenges around the usage of different "HOSTCFLAGS" for kernel build configuration and module generation

On Wed, Oct 19, 2016 at 12:25 AM, SF Markus Elfring wrote: > > Are you interested that a software generation parameter like "-S" > (for output of assembler source files) could be directly supported > for a special build variant? No, if you want to see the assembly code then something like make

Re: Difficulties around "fixdep" for the usage of a kernel build output directory

On Tue, Oct 18, 2016 at 10:25 AM, SF Markus Elfring wrote: > Can it be that the passing of the adjusted parameter "HOSTCFLAGS" has got a > significant > influence (with unwanted side effects) in this use case? That's probably it. If I strip down your advanced

Re: Difficulties around "fixdep" for the usage of a kernel build output directory

On Tue, Oct 18, 2016 at 10:25 AM, SF Markus Elfring wrote: > Can it be that the passing of the adjusted parameter "HOSTCFLAGS" has got a > significant > influence (with unwanted side effects) in this use case? That's probably it. If I strip down your advanced original example to just make

Re: Difficulties around "fixdep" for the usage of a kernel build output directory

On Tue, Oct 18, 2016 at 9:38 AM, SF Markus Elfring wrote: >>> elfring@Sonne:~/Projekte/Linux/next-patched> my_off=-O0 && for X in off; do >>> my_output_dir=${my_build_dir}unchanged/optimisation/${X} && >>> my_var="my_${X}" && my_parameters="-Wall -std=gnu89

Re: Difficulties around "fixdep" for the usage of a kernel build output directory

On Tue, Oct 18, 2016 at 9:38 AM, SF Markus Elfring wrote: >>> elfring@Sonne:~/Projekte/Linux/next-patched> my_off=-O0 && for X in off; do >>> my_output_dir=${my_build_dir}unchanged/optimisation/${X} && >>> my_var="my_${X}" && my_parameters="-Wall -std=gnu89 -fomit-frame-pointer >>> ${!my_var}"

Re: Difficulties around "fixdep" for the usage of a kernel build output directory

On Tue, Oct 18, 2016 at 6:54 AM, SF Markus Elfring wrote: > Hello, > > The file "README" contains a section "BUILD directory for the kernel". > I would like to use the functionality which is described there. > > One of my commands for such a build try is working as

Re: Difficulties around "fixdep" for the usage of a kernel build output directory

On Tue, Oct 18, 2016 at 6:54 AM, SF Markus Elfring wrote: > Hello, > > The file "README" contains a section "BUILD directory for the kernel". > I would like to use the functionality which is described there. > > One of my commands for such a build try is working as desired. > > >

Re: [PATCH 2/2] kbuild: add shell cache

On Mon, Jun 27, 2016 at 11:28 AM, Rabin Vincent wrote: > Running make results in over 40 invocations of the compiler just during > processing of the Makefile, before any actual rules are run. > > To reduce this overhead, cache the results of $(shell) calls to the > compiler.

Re: [PATCH 2/2] kbuild: add shell cache

On Mon, Jun 27, 2016 at 11:28 AM, Rabin Vincent wrote: > Running make results in over 40 invocations of the compiler just during > processing of the Makefile, before any actual rules are run. > > To reduce this overhead, cache the results of $(shell) calls to the > compiler. Clever. Looks like

randconfig build error with next-20151216, in drivers/i2c/busses

Building with the attached random configuration file, ERROR: "i2c_parse_fw_timings" [drivers/i2c/busses/i2c-rcar.ko] undefined! -- Jim # # Automatically generated file; DO NOT EDIT. # Linux/x86 4.4.0-rc5 Kernel Configuration # CONFIG_64BIT=y CONFIG_X86_64=y CONFIG_X86=y

randconfig build error with next-20151216, in drivers/i2c/busses

Building with the attached random configuration file, ERROR: "i2c_parse_fw_timings" [drivers/i2c/busses/i2c-rcar.ko] undefined! -- Jim # # Automatically generated file; DO NOT EDIT. # Linux/x86 4.4.0-rc5 Kernel Configuration # CONFIG_64BIT=y CONFIG_X86_64=y CONFIG_X86=y

randconfig build error with next-20151215, in arch/x86/entry/vdso/vma.c

Building with the attached random configuration file, arch/x86/built-in.o: In function `map_vdso': vma.c:(.text+0x13fc): undefined reference to `pvclock_pvti_cpu0_va' -- Jim # # Automatically generated file; DO NOT EDIT. # Linux/x86 4.4.0-rc5 Kernel Configuration # CONFIG_64BIT=y

randconfig build error with next-20151215, in arch/x86/entry/vdso/vma.c

Building with the attached random configuration file, arch/x86/built-in.o: In function `map_vdso': vma.c:(.text+0x13fc): undefined reference to `pvclock_pvti_cpu0_va' -- Jim # # Automatically generated file; DO NOT EDIT. # Linux/x86 4.4.0-rc5 Kernel Configuration # CONFIG_64BIT=y

randconfig build error with next-20151209, in drivers/tty/serial/kgdboc.c

Building with the attached random configuration file, drivers/built-in.o: In function `kgdboc_pre_exp_handler': kgdboc.c:(.text+0x7b5aa): undefined reference to `fg_console' kgdboc.c:(.text+0x7b5ce): undefined reference to `vc_cons' kgdboc.c:(.text+0x7b5d5): undefined reference to `vc_cons' --

randconfig build error with next-20151209, in drivers/tty/serial/kgdboc.c

Building with the attached random configuration file, drivers/built-in.o: In function `kgdboc_pre_exp_handler': kgdboc.c:(.text+0x7b5aa): undefined reference to `fg_console' kgdboc.c:(.text+0x7b5ce): undefined reference to `vc_cons' kgdboc.c:(.text+0x7b5d5): undefined reference to `vc_cons' --

randconfig build error with next-20151203, in drivers/scsi/mpt3sas/mpt3sas_base.c

Building with the attached random configuration file, warning: (SCSI_MPT2SAS) selects SCSI_MPT3SAS which has unmet direct dependencies (SCSI_LOWLEVEL && PCI && SCSI) drivers/scsi/mpt3sas/mpt3sas_base.c: In function ‘mpt3sas_remove_dead_ioc_func’: drivers/scsi/mpt3sas/mpt3sas_base.c:140:2: error:

  1   2   3   4   5   >