All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Mark Brown <broonie@kernel.org>
Cc: Aishwarya TCV <aishwarya.tcv@arm.com>,
	adhemerval.zanella@linaro.org, linux-kernel@vger.kernel.org,
	Naresh Kamboju <naresh.kamboju@linaro.org>
Subject: Re: [PATCH] selftests: vDSO: don't include generated headers for chacha test
Date: Wed, 11 Sep 2024 14:47:02 +0200	[thread overview]
Message-ID: <ZuGRRp4j2qvUKxF7@zx2c4.com> (raw)
In-Reply-To: <974bdaba-6f99-4275-8b4e-f3e95d273ddd@sirena.org.uk>

On Wed, Sep 11, 2024 at 11:14:06AM +0100, Mark Brown wrote:
> On Wed, Sep 11, 2024 at 04:44:48AM +0200, Jason A. Donenfeld wrote:
> > On Tue, Sep 10, 2024 at 11:52:51PM +0100, Aishwarya TCV wrote:
> > > make[4]: *** [Makefile:299:
> > > /tmp/kci/linux/build/kselftest/kvm/aarch64/aarch32_id_regs.o] Error 1
> > > make[4]: Leaving directory '/tmp/kci/linux/tools/testing/selftests/kvm'
> 
> > You sure this bisected right? That directory isn't related to the
> > commit in question, I don't think...
> 
> I eyeballed it for Aishwarya and it looked related on first glance
> (messing around with the generated headers), though looking again it's
> only in the vDSO directory so shouldn't be messing up other
> directories...

Okay, so... I reproduced the problem on linux-next. Then I reverted the
commit and reproduced it again. Then just to be sure, I ran:

    $ git checkout v6.9 tools/testing/selftests/vDSO/

And then I reproduced the problem again.

So I think we can be somewhat certain the unrelated directory is indeed
unrelated.

  reply	other threads:[~2024-09-11 12:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-04 15:58 [PATCH] selftests: vDSO: don't include generated headers for chacha test Jason A. Donenfeld
2024-09-04 16:19 ` Adhemerval Zanella Netto
2024-09-10 22:52 ` Aishwarya TCV
2024-09-11  2:44   ` Jason A. Donenfeld
2024-09-11 10:14     ` Mark Brown
2024-09-11 12:47       ` Jason A. Donenfeld [this message]
2024-09-11 13:01         ` Jason A. Donenfeld
2024-09-11 13:33           ` Jason A. Donenfeld
2024-09-11 13:36             ` [PATCH v2] " Jason A. Donenfeld
2024-09-11 14:12               ` Mark Brown
2024-09-11 14:40                 ` Jason A. Donenfeld

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=ZuGRRp4j2qvUKxF7@zx2c4.com \
    --to=jason@zx2c4.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=aishwarya.tcv@arm.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=naresh.kamboju@linaro.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.