From: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Miaohe Lin <linmiaohe-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Cc: hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org,
lizefan.x-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] cgroup: remove unneeded return value of cgroup_rm_cftypes_locked()
Date: Tue, 11 Jul 2023 11:40:23 -1000 [thread overview]
Message-ID: <ZK3MR5liSMSrlKVm@slm.duckdns.org> (raw)
In-Reply-To: <27428e7d-e280-2f78-7856-056d4e174057-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
On Tue, Jul 11, 2023 at 11:00:58AM +0800, Miaohe Lin wrote:
> On 2023/7/11 3:40, Tejun Heo wrote:
> > On Sat, Jul 01, 2023 at 03:38:56PM +0800, Miaohe Lin wrote:
> >> The return value of cgroup_rm_cftypes_locked() is always 0. So remove
> >> it to simplify the code. No functional change intended.
> >>
> >> Signed-off-by: Miaohe Lin <linmiaohe-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
> >
> > Applied to cgroup/for-6.6. Please feel free to follow up with the comment
> > addition Michal suggested.
>
> Should I send a v2 patch or a separate patch? Both is fine to me.
Please send a separate patch.
Thanks.
--
tejun
next prev parent reply other threads:[~2023-07-11 21:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-01 7:38 [PATCH] cgroup: remove unneeded return value of cgroup_rm_cftypes_locked() Miaohe Lin
2023-07-10 15:46 ` Michal Koutný
2023-07-11 2:58 ` Miaohe Lin
[not found] ` <7d3323ab-f796-6846-ab08-5d48734595e1-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2023-07-11 11:21 ` Michal Koutný
[not found] ` <20230701073856.2095425-1-linmiaohe-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2023-07-10 19:40 ` Tejun Heo
[not found] ` <ZKxeke6SfBe37Jso-NiLfg/pYEd1N0TnZuCh8vA@public.gmane.org>
2023-07-11 3:00 ` Miaohe Lin
[not found] ` <27428e7d-e280-2f78-7856-056d4e174057-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2023-07-11 21:40 ` Tejun Heo [this message]
[not found] ` <ZK3MR5liSMSrlKVm-NiLfg/pYEd1N0TnZuCh8vA@public.gmane.org>
2023-07-12 2:02 ` Miaohe Lin
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=ZK3MR5liSMSrlKVm@slm.duckdns.org \
--to=tj-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org \
--cc=linmiaohe-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lizefan.x-EC8Uxl6Npydl57MIdRCFDg@public.gmane.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