All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Wang <liwang@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v1 2/2] libs/libltpnewipc: Add libmsgctl.c into new ipc library
Date: Mon, 3 Aug 2020 16:47:50 +0800	[thread overview]
Message-ID: <CAEemH2dAGGFt6esH4srVec=6HCVt3j+Bn1UOdTACwg_5xj1htA@mail.gmail.com> (raw)
In-Reply-To: <320f25e9-f0e7-73a9-fe43-284befcce1e2@cn.fujitsu.com>

Hi Xu,

On Thu, Jul 30, 2020 at 3:00 PM Yang Xu <xuyang2018.jy@cn.fujitsu.com>
wrote:

> Hi Cyril
>
>
> > Hi!
> >> Signed-off-by: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
> >> ---
> >>   include/libnewipc.h           |  28 ++++------
> >>   libs/libltpnewipc/libnewipc.c | 101 ++++++++++++++++++++++++++++++++--
> >>   2 files changed, 109 insertions(+), 20 deletions(-)
> >
> > Just FYI we do not have to put all the code into a single *.c file, we
> > can have as many as we want in the library directory...
> I remember you have some comments on my previous patach as below:
> ------------------------------
> So unless we plan to use it from different tests it does not make much
> sense to export it to the top level include and libs.
>
> Or alternatively we do have libltpnewipc we can pust put the
> libnewmsgctl.c to that directory and with that we will have a single
> System V IPC helper library.
> ------------------------------
>
> So I merge libnewmsgctl.c into libnewipc.c.
>
> ps: IMO, libnewipc has only three functions(getipckey,get_used_queues,
> probe_free_addr) ,It's hard to call it a LIBS library. Can we put it
> into lib directory and named it as tst_ipc.c?
> @LI, What do you think about this?
>

I have no objection to this.

The reason to move it to LIBS is to support both new and old test cases in
same directory, so if you're going to move back into the general LTP lib,
we have to convert all the old-tests into new API. Then it will be fine.

-- 
Regards,
Li Wang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20200803/33a860d8/attachment.htm>

  reply	other threads:[~2020-08-03  8:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28  4:40 [LTP] [PATCH v1 1/2] libs/libltpnewipc: Use safe macros Yang Xu
2020-07-28  4:40 ` [LTP] [PATCH v1 2/2] libs/libltpnewipc: Add libmsgctl.c into new ipc library Yang Xu
2020-07-29  7:37   ` Li Wang
2020-07-29  7:51     ` Yang Xu
2020-07-29  8:16       ` Li Wang
2020-07-29  8:30         ` Yang Xu
2020-07-29 14:34   ` Cyril Hrubis
2020-07-30  7:00     ` Yang Xu
2020-08-03  8:47       ` Li Wang [this message]
2020-07-29 14:30 ` [LTP] [PATCH v1 1/2] libs/libltpnewipc: Use safe macros Cyril Hrubis

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='CAEemH2dAGGFt6esH4srVec=6HCVt3j+Bn1UOdTACwg_5xj1htA@mail.gmail.com' \
    --to=liwang@redhat.com \
    --cc=ltp@lists.linux.it \
    /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.