Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH] tools: bpftool: remove invalid \' json escape
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <167752621753.5062.4191667021667722418.git-patchwork-notify@kernel.org>
Date:   Mon, 27 Feb 2023 19:30:17 +0000
References: <20230227150853.16863-1-gerhorst@cs.fau.de>
In-Reply-To: <20230227150853.16863-1-gerhorst@cs.fau.de>
To:     Luis Gerhorst <gerhorst@cs.fau.de>
Cc:     quentin@isovalent.com, ast@kernel.org, daniel@iogearbox.net,
        andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
        yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
        sdf@google.com, haoluo@google.com, jolsa@kernel.org,
        bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Precedence: bulk

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Mon, 27 Feb 2023 16:08:54 +0100 you wrote:
> RFC8259 ("The JavaScript Object Notation (JSON) Data Interchange
> Format") only specifies \", \\, \/, \b, \f, \n, \r, and \r as valid
> two-character escape sequences. This does not include \', which is not
> required in JSON because it exclusively uses double quotes as string
> separators.
> 
> Solidus (/) may be escaped, but does not have to. Only reverse
> solidus (\), double quotes ("), and the control characters have to be
> escaped. Therefore, with this fix, bpftool correctly supports all valid
> two-character escape sequences (but still does not support characters
> that require multi-character escape sequences).
> 
> [...]

Here is the summary with links:
  - tools: bpftool: remove invalid \' json escape
    https://git.kernel.org/bpf/bpf-next/c/c679bbd611c0

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