public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Lukasz Majewski <lukma@denx.de>
Cc: Joseph Myers <joseph@codesourcery.com>,
	 Paul Eggert <eggert@cs.ucla.edu>,
	 Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	Alistair Francis <alistair23@gmail.com>,
	 Arnd Bergmann <arnd@arndb.de>,
	Alistair Francis <alistair.francis@wdc.com>,
	 GNU C Library <libc-alpha@sourceware.org>,
	 Florian Weimer <fweimer@redhat.com>,
	 Carlos O'Donell <carlos@redhat.com>,
	 Stepan Golosunov <stepan@golosunov.pp.ru>,
	Zack Weinberg <zackw@panix.com>,  Jeff Law <law@redhat.com>
Subject: Re: [RFC PATCH v1] y2038: nptl: Convert pthread_mutex_{clock|timed}lock to support 64 bit
Date: Mon, 05 Oct 2020 10:08:24 +0200	[thread overview]
Message-ID: <mvma6x1858n.fsf@suse.de> (raw)
In-Reply-To: <20200923122502.28172-1-lukma@denx.de> (Lukasz Majewski's message of "Wed, 23 Sep 2020 14:25:02 +0200")

On Sep 23 2020, Lukasz Majewski wrote:

> +  int err = INTERNAL_SYSCALL_CALL (futex_time64, futex, __lll_private_flag
> +                                   (FUTEX_WAIT, private), val, tsp);

Don't split function calls before the paren.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

  parent reply	other threads:[~2020-10-05  8:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-23 12:25 Lukasz Majewski
2020-10-04 15:21 ` Lukasz Majewski
2020-10-05  8:08 ` Andreas Schwab [this message]
2020-10-05 14:41 ` Adhemerval Zanella
2020-10-06  9:42   ` Lukasz Majewski
2020-10-06 13:54     ` Adhemerval Zanella

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=mvma6x1858n.fsf@suse.de \
    --to=schwab@suse.de \
    --cc=adhemerval.zanella@linaro.org \
    --cc=alistair.francis@wdc.com \
    --cc=alistair23@gmail.com \
    --cc=arnd@arndb.de \
    --cc=carlos@redhat.com \
    --cc=eggert@cs.ucla.edu \
    --cc=fweimer@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=law@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=lukma@denx.de \
    --cc=stepan@golosunov.pp.ru \
    --cc=zackw@panix.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).