public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: Joseph Myers <joseph@codesourcery.com>,
	Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	Florian Weimer <fweimer@redhat.com>,
	GNU C Library <libc-alpha@sourceware.org>,
	Florian Weimer <fw@deneb.enyo.de>,
	Alistair Francis <alistair.francis@wdc.com>
Subject: Re: [PATCH v3] tst: Provide test for ppoll
Date: Mon, 8 Feb 2021 17:06:00 +0100	[thread overview]
Message-ID: <20210208170600.2361e9ac@jawa> (raw)
In-Reply-To: <e120e7f7-b62e-910a-12e3-b77a9e626b5c@gotplt.org>

[-- Attachment #1: Type: text/plain, Size: 1682 bytes --]

Hi Siddhesh,

> On 2/5/21 4:57 PM, Lukasz Majewski wrote:
> > This change adds new test to assess ppoll()'s timeout related
> > functionality (the struct pollfd does not provide valid fd to wait
> > for - just wait for timeout).
> > 
> > To be more specific - two use cases are checked:
> > - if ppoll() times out immediately when passed struct timespec has
> > zero values of tv_nsec and tv_sec.
> > - if ppoll() times out after timeout specified in passed argument
> > 
> > ---
> > Changes for v2:
> > - Remove _GNU_SOURCE definition if not already defined
> > - Replace clock_gettime with xclock_gettime
> > - Use FAIL_EXIT1 instead of plain ret value returning from the test
> > 
> > Changes for v3:
> > - Use smaller timeout - 0.5s (TIMEOUT* defines can be removed)
> > - Use TEST_TIMESPEC_NOW_OR_AFTER () to check if test has properly
> > timed out  
> 
> Lukasz, looks like this got pushed to master without a review.

With this particular version (v3) - I've followed detailed hints
provided by Adhemerval:
https://patchwork.sourceware.org/project/glibc/patch/20210114163239.16505-1-lukma@denx.de/

> Perhaps it happened by accident when pushing the timerfd patch?

I though that this patch is OK, after adding changes proposed by
Adhemerval (Adhemerval in detailed way - with working code - wrote what
he want's to see).

(Maybe I shouldn't post v3 to ML?)

> 
> Siddhesh


Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2021-02-08 16:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-05 11:27 Lukasz Majewski
2021-02-08 15:13 ` Siddhesh Poyarekar
2021-02-08 16:06   ` Lukasz Majewski [this message]
2021-02-08 16:18     ` Siddhesh Poyarekar
2021-02-08 16:38       ` Lukasz Majewski

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=20210208170600.2361e9ac@jawa \
    --to=lukma@denx.de \
    --cc=adhemerval.zanella@linaro.org \
    --cc=alistair.francis@wdc.com \
    --cc=fw@deneb.enyo.de \
    --cc=fweimer@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=siddhesh@gotplt.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).