Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH] libbpf: Avoid allocating reg_name with sscanf in
 parse_usdt_arg()
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <166638783264.15541.17720155984505413324.git-patchwork-notify@kernel.org>
Date:   Fri, 21 Oct 2022 21:30:32 +0000
References: <20221018145538.2046842-1-xukuohai@huaweicloud.com>
In-Reply-To: <20221018145538.2046842-1-xukuohai@huaweicloud.com>
To:     Xu Kuohai <xukuohai@huaweicloud.com>
Cc:     bpf@vger.kernel.org, linux-kernel@vger.kernel.org, ast@kernel.org,
        daniel@iogearbox.net, john.fastabend@gmail.com, andrii@kernel.org,
        martin.lau@linux.dev, song@kernel.org, yhs@fb.com,
        kpsingh@kernel.org, sdf@google.com, haoluo@google.com,
        jolsa@kernel.org
Precedence: bulk

Hello:

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

On Tue, 18 Oct 2022 10:55:38 -0400 you wrote:
> From: Xu Kuohai <xukuohai@huawei.com>
> 
> The reg_name in parse_usdt_arg() is used to hold register name, which
> is short enough to be held in a 16-byte array, so we could define
> reg_name as char reg_name[16] to avoid dynamically allocating reg_name
> with sscanf.
> 
> [...]

Here is the summary with links:
  - libbpf: Avoid allocating reg_name with sscanf in parse_usdt_arg()
    https://git.kernel.org/bpf/bpf-next/c/d9740535b857

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