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 bpf-next v3] bpf: btf: limit logging of ignored BTF mismatches
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <167340121559.21440.10650818438262209592.git-patchwork-notify@kernel.org>
Date:   Wed, 11 Jan 2023 01:40:15 +0000
References: <20230107025331.3240536-1-connoro@google.com>
In-Reply-To: <20230107025331.3240536-1-connoro@google.com>
To:     Connor O'Brien <connoro@google.com>
Cc:     bpf@vger.kernel.org, martin.lau@linux.dev, ast@kernel.org,
        daniel@iogearbox.net, andrii@kernel.org, song@kernel.org,
        yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
        sdf@google.com, haoluo@google.com, jolsa@kernel.org,
        linux-kernel@vger.kernel.org
Precedence: bulk

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:

On Sat,  7 Jan 2023 02:53:31 +0000 you wrote:
> Enabling CONFIG_MODULE_ALLOW_BTF_MISMATCH is an indication that BTF
> mismatches are expected and module loading should proceed
> anyway. Logging with pr_warn() on every one of these "benign"
> mismatches creates unnecessary noise when many such modules are
> loaded. Instead, handle this case with a single log warning that BTF
> info may be unavailable.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3] bpf: btf: limit logging of ignored BTF mismatches
    https://git.kernel.org/bpf/bpf-next/c/9cb61e50bf6b

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