From: Li Wang <liwang@redhat.com>
To: Cyril Hrubis <chrubis@suse.cz>, Richard Palethorpe <rpalethorpe@suse.de>
Cc: Richard Palethorpe <rpalethorpe@suse.com>,
LTP List <ltp@lists.linux.it>,
Luke Nowakowski-Krijger <luke.nowakowskikrijger@canonical.com>
Subject: Re: [LTP] [PATCH 2/3] API/cgroup: Shorten cgroup to cg in most symbols
Date: Thu, 17 Feb 2022 11:13:40 +0800 [thread overview]
Message-ID: <CAEemH2fwb6ggm+aA4DmvbO4Ut0nDK46AyZ7efJSXqsLFPMcwPw@mail.gmail.com> (raw)
In-Reply-To: <Yg0XwAb1LOso6dtf@rei>
[-- Attachment #1.1: Type: text/plain, Size: 798 bytes --]
On Wed, Feb 16, 2022 at 11:27 PM Cyril Hrubis <chrubis@suse.cz> wrote:
> Hi!
> > To be honest, I only wanted that tst_cg_test pointer :).
> >
> > But I have no objection to renaming 'tst_cgroup_*' to 'tst_cg_*'
> > for the whole APIs. (Though I don't like it)
> >
> > Let's hear more voices from peers.
>
> Actually I like it, having the common prefix shortened to just tst_cg_
> makes it easier to read, at least for me.
>
Well, two to one, thanks for the comments :).
@Richard Palethorpe <rpalethorpe@suse.de> Hi Richard,
Feel free to push 1/3 and 2/3 patches, in case someone (I guess Luke)
waiting for the code rebase on it.
We can hold patch 3/3(memcontrol04) for a while for fail debugging.
(I am involved in another stuff these days, will look back on that soon)
--
Regards,
Li Wang
[-- Attachment #1.2: Type: text/html, Size: 1899 bytes --]
[-- Attachment #2: Type: text/plain, Size: 60 bytes --]
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-02-17 3:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 14:03 [LTP] [PATCH 0/3] memcontrol04 and s/cgroup/cg/ Richard Palethorpe via ltp
2022-02-08 14:03 ` [LTP] [PATCH 1/3] API/cgroup: Add memory.{events, low} Richard Palethorpe via ltp
2022-02-16 15:27 ` Cyril Hrubis
2022-02-17 3:14 ` Li Wang
2022-02-08 14:03 ` [LTP] [PATCH 2/3] API/cgroup: Shorten cgroup to cg in most symbols Richard Palethorpe via ltp
2022-02-09 4:51 ` Li Wang
2022-02-10 7:32 ` Richard Palethorpe
2022-02-16 15:26 ` Cyril Hrubis
2022-02-17 3:13 ` Li Wang [this message]
2022-02-17 5:37 ` Richard Palethorpe
2022-02-08 14:03 ` [LTP] [PATCH 3/3] memcontrol04: Copy from kselftest Richard Palethorpe via ltp
2022-02-09 10:47 ` Li Wang
2022-02-10 7:34 ` Richard Palethorpe
2022-02-09 11:05 ` Li Wang
2022-02-10 6:23 ` Li Wang
2022-02-10 7:12 ` Li Wang
2022-02-14 5:40 ` Richard Palethorpe
2022-02-16 10:13 ` Li Wang
2022-02-17 4:35 ` Richard Palethorpe
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=CAEemH2fwb6ggm+aA4DmvbO4Ut0nDK46AyZ7efJSXqsLFPMcwPw@mail.gmail.com \
--to=liwang@redhat.com \
--cc=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=luke.nowakowskikrijger@canonical.com \
--cc=rpalethorpe@suse.com \
--cc=rpalethorpe@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.