Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Petr Vorel <petr.vorel@gmail.com>
To: "Daniel Díaz" <daniel.diaz@linaro.org>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2 1/1] ltp: Update to 20180926
Date: Thu, 1 Nov 2018 18:58:15 +0100	[thread overview]
Message-ID: <20181101175803.GA22705@x230> (raw)
In-Reply-To: <CAEUSe78cdBVy2A2HVO6jEjaDk6-0h7kuKTH__7NUMthg_PUoow@mail.gmail.com>

Hello Daniel,

I've rebased patch for actual master and sent it as v2.
Please use this one.

> > New patches
> > * 0001-statx-fix-compile-errors.patch

> Oh, boy, thanks for finding that patch -- caused me lots of troubles.
:-)

About patches bellow. LTP is full of patches, if you want to have best LTP
use git master branch. That's why I'm for including only build fixes,
release is roughly each 4 months.

I kept patches bellow, let's keep them, but IMHO they're not that important.

> Since you sent v2 of this patch there's been a couple of patches added:
> * 0001-sigwaitinfo01-recent-glibc-calls-syscall-directly.patch
This one was accepted.

> * 0001-netns_helper.sh-use-ping-6-when-ping6-is-not-avaliab.patch
This one as well. There is more effective fix for ping6 for all networking tests
which use new shell API (IMHO the only relevant tests):
7f10a1910 tst_net.sh: Fix ping detection
d57ac0b7a net: Fix missing ping6

> * 0001-open_posix_testsuite-mmap24-2-Relax-condition-a-bit.patch
We're waiting for v2 of this patch.

> Do we want those in?

> > Rebased patches
> > * 0039-commands-ar01-Fix-for-test-in-deterministic-mode.patch

> > Removed removed (accepted in upstream)
> > * 0041-cve-2017-5669-shmat-for-0-or-PAGESIZE-with-RND-flag-.patch
> > * 0042-fs-ftest-ftest06.c-Fix-too-small-name-string-and-rel.patch
> > * 0043-open-creat-skip-S_ISGID-check-on-files-created-by-no.patch

> Patch 0040-read_all-Define-FNM_EXTMATCH-if-not-already-like-und.patch
> also made it upstream, albeit with a different implementation. See
> commit 822ad20433799193e2180862137c36f24e5d27d6.
Well, I haven't replaced this one with upgrade :(.
Shell I post v3? Or will you do it in separate commit?

> Thanks and greetings!

> Daniel Díaz
> daniel.diaz@linaro.org

Kind regards,
Petr


  reply	other threads:[~2018-11-01 17:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-07 19:42 [PATCH v2 1/1] ltp: Update to 20180926 Petr Vorel
2018-11-01 14:01 ` Daniel Díaz
2018-11-01 17:58   ` Petr Vorel [this message]
2018-11-01 18:57     ` Daniel Díaz
  -- strict thread matches above, loose matches on Subject: below --
2018-11-01 17:47 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=20181101175803.GA22705@x230 \
    --to=petr.vorel@gmail.com \
    --cc=daniel.diaz@linaro.org \
    --cc=openembedded-core@lists.openembedded.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