From: Shuah Khan <skhan@linuxfoundation.org>
To: John Hubbard <jhubbard@nvidia.com>, Shuah Khan <shuah@kernel.org>
Cc: "Jason A . Donenfeld" <Jason@zx2c4.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andy Lutomirski <luto@kernel.org>,
Mark Brown <broonie@kernel.org>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Colin Ian King <colin.i.king@gmail.com>,
Valentin Obst <kernel@valentinobst.de>,
linux-kselftest@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
llvm@lists.linux.dev, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v4 2/3] selftests/mm: remove partially duplicated "all:" target in Makefile
Date: Fri, 5 Jul 2024 12:10:20 -0600 [thread overview]
Message-ID: <38852b52-7ea5-431a-b946-b0dc6bb54e7d@linuxfoundation.org> (raw)
In-Reply-To: <da35faba-b6c7-42bd-86a1-57328ebc9ad8@nvidia.com>
On 7/5/24 11:58, John Hubbard wrote:
> On 7/5/24 10:53, Shuah Khan wrote:
>> On 7/3/24 20:33, John Hubbard wrote:
>>> There were a couple of errors here:
>>>
>>> 1. TEST_GEN_PROGS was incorrectly prepending $(OUTPUT) to each program
>>> to be built. However, lib.mk already does that because it assumes "bare"
>>> program names are passed in, so this ended up creating
>>> $(OUTPUT)/$(OUTPUT)/file.c, which of course won't work as intended.
>>>
>>> 2. lib.mk was included before TEST_GEN_PROGS was set, which led to
>>> lib.mk's "all:" target not seeing anything to rebuild.
>>>
>>> So nothing worked, which caused the author to force things by creating
>>> an "all:" target locally--while still including ../lib.mk.
>>>
>>> Fix all of this by including ../lib.mk at the right place, and removing
>>> the $(OUTPUT) prefix to the programs to be built, and removing the
>>> duplicate "all:" target.
>>>
>>> Signed-off-by: John Hubbard <jhubbard@nvidia.com>
>>
>> Why does the summary say mm ?
>
> This is a mistake. I was also preparing some mm work at the time,
> and typed the wrong thing.
>
> Could you fix it up to s/mm/vDSO/ for me? Or if it's easier, I can send
> an updated patch, let me know.
>
>
Send me updated patch - it will be easier that way. I saw the note
about getting these into 6.10 - As soon as you send the patch I will
apply them and send them for 6.10
thanks,
-- Shuah
next prev parent reply other threads:[~2024-07-05 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 2:33 [PATCH v4 0/3] selftests/vDSO: fix clang build errors, and Makefile cleanup John Hubbard
2024-07-04 2:33 ` [PATCH v4 1/3] selftests/vDSO: fix clang build errors and warnings John Hubbard
2024-07-04 2:33 ` [PATCH v4 2/3] selftests/mm: remove partially duplicated "all:" target in Makefile John Hubbard
2024-07-05 8:13 ` Muhammad Usama Anjum
2024-07-05 17:53 ` Shuah Khan
2024-07-05 17:58 ` John Hubbard
2024-07-05 18:10 ` Shuah Khan [this message]
2024-07-04 2:33 ` [PATCH v4 3/3] selftests/vDSO: remove duplicate compiler invocations from Makefile John Hubbard
2024-07-05 16:54 ` [PATCH v4 0/3] selftests/vDSO: fix clang build errors, and Makefile cleanup Shuah Khan
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=38852b52-7ea5-431a-b946-b0dc6bb54e7d@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=Jason@zx2c4.com \
--cc=broonie@kernel.org \
--cc=colin.i.king@gmail.com \
--cc=jhubbard@nvidia.com \
--cc=kernel@valentinobst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=luto@kernel.org \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=vincenzo.frascino@arm.com \
/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