From: Sasha Levin <sashal@kernel.org>
To: sashiko-reviews@lists.linux.dev
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH] tools/dma: fix building from the top level with O=
Date: Sun, 11 Oct 2026 19:58:33 -0400 [thread overview]
Message-ID: <aswiqUfbA9840hgo@laps> (raw)
In-Reply-To: <sashiko-outbox-167498@kernel.org>
On Sun, Oct 11, 2026 at 10:43:33PM +0000, sashiko-bot@kernel.org wrote:
>Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
>- [Low] tools/dma: incomplete fix for out-of-tree (O=) builds
>--
>
>commit f9ebfb989b6d469df7135b7ea719817656f0b606
>Author: Sasha Levin <sashal@kernel.org>
>
>tools/dma: fix building from the top level with O=
>
>This commit attempts to fix the out-of-tree build for tools/dma when using
>O=<dir> by correctly setting the srctree variable. It ensures that srctree
>is worked out even when it is empty or when building_out_of_srctree is set.
>
>> diff --git a/tools/dma/Makefile b/tools/dma/Makefile
>> index e4abf37bf020c..b5fe6e2625eef 100644
>> --- a/tools/dma/Makefile
>> +++ b/tools/dma/Makefile
>> @@ -7,7 +7,13 @@ bindir ?= /usr/bin
>> # isn't set and when invoked from selftests build, where srctree
>> # is set to ".". building_out_of_srctree is undefined for in srctree
>> # builds
>> +ifeq ($(srctree),)
>> +update_srctree := 1
>> +endif
>> ifndef building_out_of_srctree
>> +update_srctree := 1
>> +endif
>> +ifeq ($(update_srctree),1)
>> srctree := $(patsubst %/,%,$(dir $(CURDIR)))
>> srctree := $(patsubst %/,%,$(dir $(srctree)))
>> endif
>
>[Severity: Low]
>Does this commit completely fix the out-of-tree (O=) builds?
>
>While this resolves the srctree issue to successfully locate Makefile.include,
>an out-of-tree build via O=<dir> will still fail immediately afterwards.
This was fixed in a different patch here: https://lore.kernel.org/r/20261011223358.2327625-3-sashal@kernel.org
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-10-11 23:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20261011223410eucas1p1db84283e5fc98bfb7d0bdeff84fd1a7c@eucas1p1.samsung.com>
2026-10-11 22:33 ` [PATCH] tools/dma: fix building from the top level with O= Sasha Levin
2026-10-11 22:43 ` sashiko-bot
2026-10-11 23:58 ` Sasha Levin [this message]
2026-10-13 2:09 ` Qinxin Xia
2026-10-13 11:42 ` Marek Szyprowski
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=aswiqUfbA9840hgo@laps \
--to=sashal@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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