From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>, netdev@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 0/3] selftests: bpf: break up test_verifier
Date: Mon, 28 Jan 2019 08:45:34 -0800 [thread overview]
Message-ID: <20190128084534.183789e5@cakuba.hsd1.ca.comcast.net> (raw)
In-Reply-To: <20190128055719.kqvebv2ievpklydy@ast-mbp>
On Sun, 27 Jan 2019 21:57:20 -0800, Alexei Starovoitov wrote:
> My tripple check failed.
> Turned out that the eariler attempt to merge it created
> selftests/bpf/verifier/ directory with .gitignore file inside it
> and 'git am --abort' and 'git rebase --hard' kept it in place.
> (since .gitignore was there)
>
> 'git' wasn't very helpful with the following message either:
> ----
> Applying: selftests: bpf: prepare for break up of verifier tests
> error: sha1 information is lacking or useless (tools/testing/selftests/bpf/Makefile).
> error: could not build fake ancestor
> Patch failed at 0001 selftests: bpf: prepare for break up of verifier tests
Aw, weirdness.
> But the odds were in my favor tonight :)
>
> Applied to bpf-next. Thanks!
Awesome :)
prev parent reply other threads:[~2019-01-28 16:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 23:24 [PATCH bpf-next v2 0/3] selftests: bpf: break up test_verifier Jakub Kicinski
2019-01-25 23:24 ` [PATCH bpf-next v2 1/3] selftests: bpf: prepare for break up of verifier tests Jakub Kicinski
2019-01-25 23:24 ` [PATCH bpf-next v2 3/3] selftests: bpf: break up the rest of test_verifier Jakub Kicinski
2019-01-26 5:55 ` [PATCH bpf-next v2 0/3] selftests: bpf: break up test_verifier Alexei Starovoitov
2019-01-26 6:17 ` Jakub Kicinski
2019-01-26 6:21 ` Alexei Starovoitov
2019-01-27 18:33 ` Jakub Kicinski
2019-01-27 20:56 ` Alexei Starovoitov
[not found] ` <20190127205413.231fcc05@cakuba.hsd1.ca.comcast.net>
2019-01-28 5:57 ` Alexei Starovoitov
2019-01-28 16:45 ` Jakub Kicinski [this message]
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=20190128084534.183789e5@cakuba.hsd1.ca.comcast.net \
--to=jakub.kicinski@netronome.com \
--cc=alexei.starovoitov@gmail.com \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox