From nobody Sat Feb 7 13:41:37 2026 Received: from out-184.mta0.migadu.com (out-184.mta0.migadu.com [91.218.175.184]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 10F673644AB for ; Thu, 29 Jan 2026 03:50:28 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.184 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769658631; cv=none; b=KDgYQqDRiVy6pwy4WVJv+vfO9CnJZOwOheK7BaxtFh9Z8ZAHQwAi+UUxGSKVJvPyDEFSB3QdEoKT3lsu43VDJICrrX9nYr8Aw2NzXK2Fsi94KzuX+bQA0s0V/Zzn7zU7oUp1GyN5Rd0FF+snXm4gMa0UPvhmDwnjNPr4dDmrA3Q= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769658631; c=relaxed/simple; bh=jtLB/czrRZ77D0/tt10ovpVdSgEst5eGeIq/HIdlg3o=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=BaceaQnTQVfhQEUMiNiLlJwRHidUDjHVRZ59h1M29TVz3uc+J8qTQOMmJ7nt+65ojybIfY8/wNEnGL7RvCnHEe0eWP8NmIHdaMSh/eNL4mQnHqw73ZS74gg42UzOZRc3h3bDCYYiVZFHKaP9bUjVZ+3uJnl6BXNlOyEa8TbEVtM= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=Lw9Keiwv; arc=none smtp.client-ip=91.218.175.184 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="Lw9Keiwv" X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1769658626; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=2/Qs/X84F7xqVULHI40NbrGxxf+fCcySI+HtrrKnXho=; b=Lw9KeiwvPevGSEmicxuywrMDbeZB6Yw++8Iw2z7hTXv4HRbKT++i7fd0qktNzEVrD+p4zE T8dLoJOHcK9Bsy7Fy1UvhXDOBhAWzFI4AVUixU9uC6J8l5nj4GC/VhPejGAfEFkDpNi/NT MzgzM3e9ipworgrbd49lOyKRFcQqneM= From: Hui Zhu To: Roman Gushchin , JP Kobryn , Shakeel Butt , Andrew Morton , bpf@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Cc: Hui Zhu Subject: [PATCH bpf-next] mm/bpf_memcontrol: Add missing newline in pr_warn message Date: Thu, 29 Jan 2026 11:50:14 +0800 Message-ID: <20260129035014.3283392-1-hui.zhu@linux.dev> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Migadu-Flow: FLOW_OUT Content-Type: text/plain; charset="utf-8" From: Hui Zhu Add missing newline character at the end of pr_warn error message in bpf_memcontrol_init() function. Kernel log messages should end with a newline character for proper formatting in kernel logs. This issue was pointed out in https://github.com/kernel-patches/bpf/pull/10864#discussion_r2735018210 Signed-off-by: Hui Zhu Acked-by: Roman Gushchin --- mm/bpf_memcontrol.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/mm/bpf_memcontrol.c b/mm/bpf_memcontrol.c index 716df49d7647..20999a29820b 100644 --- a/mm/bpf_memcontrol.c +++ b/mm/bpf_memcontrol.c @@ -186,7 +186,8 @@ static int __init bpf_memcontrol_init(void) err =3D register_btf_kfunc_id_set(BPF_PROG_TYPE_UNSPEC, &bpf_memcontrol_kfunc_set); if (err) - pr_warn("error while registering bpf memcontrol kfuncs: %d", err); + pr_warn("error while registering bpf memcontrol kfuncs: %d\n", + err); =20 return err; } --=20 2.43.0