BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Quentin Monnet <quentin@isovalent.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next] bpf: use $(pound) instead of \# in Makefiles
Date: Wed, 06 Oct 2021 16:30:07 +0000	[thread overview]
Message-ID: <163353780748.7077.6059227334886059915.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211006111049.20708-1-quentin@isovalent.com>

Hello:

This patch was applied to bpf/bpf-next.git (refs/heads/master):

On Wed,  6 Oct 2021 12:10:49 +0100 you wrote:
> Recent-ish versions of make do no longer consider number signs ("#") as
> comment symbols when they are inserted inside of a macro reference or in
> a function invocation. In such cases, the symbols should not be escaped.
> 
> There are a few occurrences of "\#" in libbpf's and samples' Makefiles.
> In the former, the backslash is harmless, because grep associates no
> particular meaning to the escaped symbol and reads it as a regular "#".
> In samples' Makefile, recent versions of make will pass the backslash
> down to the compiler, making the probe fail all the time and resulting
> in the display of a warning about "make headers_install" being required,
> even after headers have been installed.
> 
> [...]

Here is the summary with links:
  - [bpf-next] bpf: use $(pound) instead of \# in Makefiles
    https://git.kernel.org/bpf/bpf-next/c/bf2819e0b10f

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2021-10-06 16:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-06 11:10 [PATCH bpf-next] bpf: use $(pound) instead of \# in Makefiles Quentin Monnet
2021-10-06 16:30 ` patchwork-bot+netdevbpf [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=163353780748.7077.6059227334886059915.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=netdev@vger.kernel.org \
    --cc=quentin@isovalent.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