From: Andrew Morton <akpm@linux-foundation.org>
To: Sasha Levin <sashal@kernel.org>
Cc: Mark Brown <broonie@kernel.org>,
Christian Brauner <brauner@kernel.org>,
Yongxin Yang <yangyongxin@kylinos.cn>,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: [PATCH linux-next] profiling: keep the error message in the mm-nonmm-unstable merge
Date: Mon, 16 Nov 2026 13:51:39 -0800 [thread overview]
Message-ID: <20261116135139.ffa354b526687dd39f62b58a@linux-foundation.org> (raw)
In-Reply-To: <20261116214219.470791-1-sashal@kernel.org>
On Mon, 16 Nov 2026 16:42:19 -0500 Sasha Levin <sashal@kernel.org> wrote:
> Commit 944b8062bc6f ("profiling: report it when /proc/profile can't be
> created") in the vfs-brauner-fixes tree and commit 091be6dce28a
> ("perf/profile: report failure to create /proc/profile") in the
> mm-nonmm-unstable tree both make create_proc_profile() return -ENOMEM
> when proc_create() fails.
Yeah, two near-identical patches were in flight at the same time. I've
dropped 091be6dce28a.
> The second one also prints an error, as the
> return value of an initcall is not shown to anyone.
Unless they use initcall_debug.
> The merge resolution
> took the first version, so the message is gone.
>
> Keep the pr_err().
OK, this turns 944b8062bc6f into 091be6dce28a, ack.
prev parent reply other threads:[~2026-11-16 21:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 15:53 linux-next: manual merge of the mm-nonmm-unstable tree with the vfs-brauner-fixes tree Mark Brown
2026-11-16 21:42 ` [PATCH linux-next] profiling: keep the error message in the mm-nonmm-unstable merge Sasha Levin
2026-11-16 21:51 ` Andrew Morton [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=20261116135139.ffa354b526687dd39f62b58a@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=yangyongxin@kylinos.cn \
/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