LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: Paul Mackerras <paulus@samba.org>,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v11] Fixup for "powerpc/vdso: Provide __kernel_clock_gettime64() on vdso32"
Date: Tue, 1 Sep 2020 09:24:32 +0200	[thread overview]
Message-ID: <f0152154-1edb-a51e-b24e-443b072b8ea0@csgroup.eu> (raw)
In-Reply-To: <20200901071908.GF29521@kitsune.suse.cz>


Le 01/09/2020 à 09:19, Michal Suchánek a écrit :
> Hello,
> 
> can you add Fixes: ?

That's a commit which is still in powerpc/next-test.
My intention was to provide something that Michael can squash/fixup into 
the culprit commit.

Christophe


> 
> Thanks
> 
> Michal
> 
> On Tue, Sep 01, 2020 at 05:28:57AM +0000, Christophe Leroy wrote:
>> Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
>> ---
>>   arch/powerpc/include/asm/vdso/gettimeofday.h | 2 ++
>>   1 file changed, 2 insertions(+)
>>
>> diff --git a/arch/powerpc/include/asm/vdso/gettimeofday.h b/arch/powerpc/include/asm/vdso/gettimeofday.h
>> index 59a609a48b63..8da84722729b 100644
>> --- a/arch/powerpc/include/asm/vdso/gettimeofday.h
>> +++ b/arch/powerpc/include/asm/vdso/gettimeofday.h
>> @@ -186,6 +186,8 @@ int __c_kernel_clock_getres(clockid_t clock_id, struct __kernel_timespec *res,
>>   #else
>>   int __c_kernel_clock_gettime(clockid_t clock, struct old_timespec32 *ts,
>>   			     const struct vdso_data *vd);
>> +int __c_kernel_clock_gettime64(clockid_t clock, struct __kernel_timespec *ts,
>> +			       const struct vdso_data *vd);
>>   int __c_kernel_clock_getres(clockid_t clock_id, struct old_timespec32 *res,
>>   			    const struct vdso_data *vd);
>>   #endif
>> -- 
>> 2.25.0
>>

      reply	other threads:[~2020-09-01  7:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-01  5:28 [PATCH v11] Fixup for "powerpc/vdso: Provide __kernel_clock_gettime64() on vdso32" Christophe Leroy
2020-09-01  7:19 ` Michal Suchánek
2020-09-01  7:24   ` Christophe Leroy [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=f0152154-1edb-a51e-b24e-443b072b8ea0@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=msuchanek@suse.de \
    --cc=paulus@samba.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