bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: Andrii Nakryiko <andriin@fb.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, ast@fb.com,
	yhs@fb.com, andrii.nakryiko@gmail.com, kernel-team@fb.com
Subject: Re: [PATCH bpf-next] selftests/bpf: fix .gitignore to ignore no_alu32/
Date: Fri, 25 Oct 2019 23:42:46 +0200	[thread overview]
Message-ID: <20191025214246.GC14547@pc-63.home> (raw)
In-Reply-To: <20191025045503.3043427-1-andriin@fb.com>

On Thu, Oct 24, 2019 at 09:55:03PM -0700, Andrii Nakryiko wrote:
> When switching to alu32 by default, no_alu32/ subdirectory wasn't added
> to .gitignore. Fix it.
> 
> Fixes: e13a2fe642bd ("tools/bpf: Turn on llvm alu32 attribute by default")
> Signed-off-by: Andrii Nakryiko <andriin@fb.com>

Applied, thanks!

      parent reply	other threads:[~2019-10-25 21:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-25  4:55 [PATCH bpf-next] selftests/bpf: fix .gitignore to ignore no_alu32/ Andrii Nakryiko
2019-10-25  5:36 ` Yonghong Song
2019-10-25 21:42 ` Daniel Borkmann [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=20191025214246.GC14547@pc-63.home \
    --to=daniel@iogearbox.net \
    --cc=andrii.nakryiko@gmail.com \
    --cc=andriin@fb.com \
    --cc=ast@fb.com \
    --cc=bpf@vger.kernel.org \
    --cc=kernel-team@fb.com \
    --cc=netdev@vger.kernel.org \
    --cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).