public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Lukasz Majewski <lukma@denx.de>, Alistair Francis <alistair23@gmail.com>
Cc: Joseph Myers <joseph@codesourcery.com>,
	Paul Eggert <eggert@cs.ucla.edu>,  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>,
	Andreas Schwab <schwab@suse.de>, Zack Weinberg <zackw@panix.com>,
	Jeff Law <law@redhat.com>
Subject: Re: [PATCH 1/2] nptl: Provide proper spelling for 32 bit version of futex_abstimed_wait
Date: Tue, 29 Sep 2020 15:11:31 -0300	[thread overview]
Message-ID: <210f2c04-6518-c385-c7b0-723770eba6f8@linaro.org> (raw)
In-Reply-To: <20200929185236.36dd8d68@jawa>



On 29/09/2020 13:52, Lukasz Majewski wrote:
> Hi Adhemerval,
> 
>> On Wed, Sep 16, 2020 at 4:07 AM Lukasz Majewski <lukma@denx.de> wrote:
>>>
>>> This change provides proper spelling of 32 bit
>>> __futex_abstimed_wait_cancelable32 function  
> 
> Adhemerval, do you have any comments regarding this patch? Or shall I
> pull it to -master?
> 

LGTM, thanks.

      reply	other threads:[~2020-09-29 18:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-16 11:07 Lukasz Majewski
2020-09-16 11:07 ` [PATCH 2/2] nptl: Provide NULL abstime pointer handling in __futex_abstimed_wait_cancelable32 Lukasz Majewski
2020-09-16 12:06   ` Andreas Schwab
2020-09-16 14:59   ` Alistair Francis
2020-09-16 12:04 ` [PATCH 1/2] nptl: Provide proper spelling for 32 bit version of futex_abstimed_wait Andreas Schwab
2020-09-16 14:56 ` Alistair Francis
2020-09-29 16:52   ` Lukasz Majewski
2020-09-29 18:11     ` Adhemerval Zanella [this message]

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=210f2c04-6518-c385-c7b0-723770eba6f8@linaro.org \
    --to=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=schwab@suse.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).