From: "Moger, Babu" <bmoger@amd.com>
To: Ben Horgan <ben.horgan@arm.com>, linux-kernel@vger.kernel.org
Cc: tony.luck@intel.com, reinette.chatre@intel.com,
Dave.Martin@arm.com, james.morse@arm.com, babu.moger@amd.com,
tglx@kernel.org, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
fenghuay@nvidia.com, tan.shaopeng@fujitsu.com
Subject: Re: [PATCH v7 1/7] fs/resctrl: Tidy up the error path in resctrl_mkdir_event_configs()
Date: Wed, 6 May 2026 10:05:36 -0500 [thread overview]
Message-ID: <8b36ee47-3661-477b-94be-0d83b2273f26@amd.com> (raw)
In-Reply-To: <20260506082855.3694761-2-ben.horgan@arm.com>
Hi Ben,
On 5/6/2026 3:28 AM, Ben Horgan wrote:
> The error path in resctrl_mkdir_event_configs() is unnecessarily
> complicated. Simplify it to just return directly on error.
>
> Signed-off-by: Ben Horgan <ben.horgan@arm.com>
> Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>
> ---
> Changes since v5:
> Correct order of the tags
>
> Changes since v6:
> Add missing commit message separator,---
> ---
> fs/resctrl/rdtgroup.c | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/fs/resctrl/rdtgroup.c b/fs/resctrl/rdtgroup.c
> index 5dfdaa6f9d8f..fb6999178fe2 100644
> --- a/fs/resctrl/rdtgroup.c
> +++ b/fs/resctrl/rdtgroup.c
> @@ -2333,20 +2333,19 @@ static int resctrl_mkdir_event_configs(struct rdt_resource *r, struct kernfs_nod
> kn_subdir2 = kernfs_create_dir(kn_subdir, mevt->name, kn_subdir->mode, mevt);
> if (IS_ERR(kn_subdir2)) {
> ret = PTR_ERR(kn_subdir2);
> - goto out;
> + return ret;
Minor nit. You can directly return like below.
return PTR_ERR(kn_subdir2);
Optional, only if there is another version.
Thanks
Babu
next prev parent reply other threads:[~2026-05-06 15:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 8:28 [PATCH v7 0/7] x86,fs/resctrl: Pave the way for MPAM counter assignment Ben Horgan
2026-05-06 8:28 ` [PATCH v7 1/7] fs/resctrl: Tidy up the error path in resctrl_mkdir_event_configs() Ben Horgan
2026-05-06 15:05 ` Moger, Babu [this message]
2026-05-06 8:28 ` [PATCH v7 2/7] x86,fs/resctrl: Create 'event_filter' files read only if they're not configurable Ben Horgan
2026-05-06 8:28 ` [PATCH v7 3/7] fs/resctrl: Disallow the software controller when MBM counters are assignable Ben Horgan
2026-05-06 8:28 ` [PATCH v7 4/7] fs/resctrl: Add monitor property 'mbm_cntr_assign_fixed' Ben Horgan
2026-05-06 8:28 ` [PATCH v7 5/7] fs/resctrl: Continue counter allocation after failure Ben Horgan
2026-05-06 8:28 ` [PATCH v7 6/7] fs/resctrl: Document that automatic counter assignment is best effort Ben Horgan
2026-05-06 8:28 ` [PATCH v7 7/7] fs/resctrl: Document tasks file behaviour for task id 0 and idle tasks Ben Horgan
2026-05-06 15:01 ` [PATCH v7 0/7] x86,fs/resctrl: Pave the way for MPAM counter assignment Moger, Babu
2026-05-06 15:08 ` Ben Horgan
2026-05-06 15:28 ` Borislav Petkov
2026-05-06 15:58 ` Reinette Chatre
2026-05-06 16:56 ` Borislav Petkov
2026-05-06 17:06 ` Reinette Chatre
2026-05-06 18:33 ` Borislav Petkov
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=8b36ee47-3661-477b-94be-0d83b2273f26@amd.com \
--to=bmoger@amd.com \
--cc=Dave.Martin@arm.com \
--cc=babu.moger@amd.com \
--cc=ben.horgan@arm.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=fenghuay@nvidia.com \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=reinette.chatre@intel.com \
--cc=tan.shaopeng@fujitsu.com \
--cc=tglx@kernel.org \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
/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