linux-kernel - Re: [PATCH 1/1] scripts: allow docproc invocation from external

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4A240993.8030409@gmail.com>
Date:	Mon, 01 Jun 2009 19:02:11 +0200
From:	Jiri Slaby <jirislaby@...il.com>
To:	Randy Dunlap <randy.dunlap@...cle.com>
CC:	sam@...nborg.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] scripts: allow docproc invocation from external

On 06/01/2009 06:05 PM, Randy Dunlap wrote:
> Jiri Slaby wrote:
>> - getcwd returns path without a slash at the end, add the slash
> 
> Hi Jiri,
> 
> This part (above) fixes a bug, right?

Yes, but the bug is not triggered when building from a kernel tree.

>> - add KBUILD_SRC env support, so that we can specify path for
>>   kernel (to know where scripts/kernel-doc resides) and SRCTREE
>>   (for searching files referenced in .tmpl) separately
> 
> Can you explain your usage a bit more so that I can understand some
> justification for this change?  (not that I'm objecting to it)

Sure, I have out-of-kernel drivers (which I plan to merge, but keep
out-of-tree development anyway) and have this in a makefile:
%.xml: %.tmpl
        KBUILD_SRC=$(KSRC) $(KDIR)/scripts/basic/docproc doc $^ > $@
so that I can build documentation from a .tmpl file for those drivers.
SRCTREE defaults to cwd, so it finds sources referenced from the .tmpl
file in current location. What didn't work is execution of
scripts/kernel-doc. This is now executed with KBUILD_SRC prepended,
which is what it should be.
--
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/