public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: ltp@lists.linux.it,
	Stanislav Kholmanskikh <stanislav.kholmanskikh@oracle.com>
Subject: Re: [LTP] [PATCH 1/1] compat_16: Define USE_LEGACY_COMPAT_16_H for legacy tests
Date: Thu, 20 Jul 2023 11:43:43 +0200	[thread overview]
Message-ID: <20230720094343.GA1300426@pevik> (raw)
In-Reply-To: <CAEemH2esxksDg1NznrCW4QKO3NvEFUENWVcc4s-jf+Yk1-_RHw@mail.gmail.com>

> Hi Petr,

> On Wed, Jul 19, 2023 at 6:12 PM Petr Vorel <pvorel@suse.cz> wrote:

> > Hi Li,

> > ...
> > > I'm not sure here if we really need COMPAT_16_H for choosing two compat
> > > header file.
> > > As we already use hard code in C source file like #include "compat_16.h"
> > or
> > > "compat_tst_16.h",
> > > so compile with -I the header directory is enough I guess.

> > > Try this simple compat_16.mk, it at least works well on my side.
> > > Or, did I miss anything in the 16bit compilation?

> > I like this simplification.

> > Well, touch compat_16.h causes rebuilding tests which use compat_tst_16.h.
> > I don't mind that. But OTOH touch compat_tst_16.h does not trigger
> > rebuilding
> > tests which use compat_tst_16.h :( (tested on
> > testcases/kernel/syscalls/setregid). Could you please recheck that?


> Good point, I overlooked the prerequisite for the target build, so it needs
> adding back.

> But we don't have the necessary to keep INTERMEDIATE object syntax.

> Delete some lines based on your patch:

> --- a/testcases/kernel/syscalls/utils/compat_16.mk
> +++ b/testcases/kernel/syscalls/utils/compat_16.mk
> @@ -53,11 +53,8 @@ CPPFLAGS             += -I$(abs_srcdir)
> -I$(abs_srcdir)/../utils
>  SRCS                   ?= $(sort $(wildcard $(abs_srcdir)/*.c))

>  MAKE_TARGETS           := $(notdir $(patsubst %.c,%,$(SRCS)))
> -MAKE_TARGETS_OBJS_WO_COMPAT_16 := $(addsuffix .o,$(MAKE_TARGETS))
>  MAKE_TARGETS           += $(addsuffix _16,$(MAKE_TARGETS))

> -# XXX (garrcoop): This code should be put in question as it cannot be
> applied
> -# (no .h file, no TST_USE_NEWER64_SYSCALL def).
>  DEF_16                 := TST_USE_COMPAT16_SYSCALL

>  ifeq ($(USE_LEGACY_COMPAT_16_H),1)
> @@ -66,13 +63,7 @@ else
>  COMPAT_16_H     := $(abs_srcdir)/../utils/compat_tst_16.h
>  endif

> -ifneq ($(wildcard $(COMPAT_16_H)),)
> -$(MAKE_TARGETS_OBJS_WO_COMPAT_16): $(COMPAT_16_H)
> -.INTERMEDIATE: $(MAKE_TARGETS_OBJS_WO_COMPAT_16)
> -endif
> -
>  %_16: CPPFLAGS += -D$(DEF_16)=1
> -# XXX (garrcoop): End section of code in question..

>  %_16.o: %.c $(COMPAT_16_H)
>         $(COMPILE.c) $(OUTPUT_OPTION) $<

LGTM, would you mind to send it as a follow up to my patch, as an additional
cleanup?

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2023-07-20  9:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18 10:00 [LTP] [PATCH 1/1] compat_16: Define USE_LEGACY_COMPAT_16_H for legacy tests Petr Vorel
2023-07-18 14:53 ` Yang Xu (Fujitsu)
2023-07-19  7:15 ` Li Wang
2023-07-19 10:12   ` Petr Vorel
2023-07-20  3:13     ` Li Wang
2023-07-20  9:43       ` Petr Vorel [this message]
2023-07-20 10:03         ` Li Wang
2023-10-27 11:58           ` Cyril Hrubis
2023-10-27 17:38             ` Petr Vorel

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=20230720094343.GA1300426@pevik \
    --to=pvorel@suse.cz \
    --cc=liwang@redhat.com \
    --cc=ltp@lists.linux.it \
    --cc=stanislav.kholmanskikh@oracle.com \
    /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