All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Florian Bezdeka <florian.bezdeka@siemens.com>, xenomai@xenomai.org
Subject: Re: [PATCH v5 0/5] y2038: Add mutex_timedlock64() support
Date: Tue, 10 Aug 2021 12:38:18 +0200	[thread overview]
Message-ID: <046bb3ac-3e5c-f8b2-c1d7-5225329d3814@siemens.com> (raw)
In-Reply-To: <262f8a56-2afb-b486-dcf5-a5032e137f7d@siemens.com>

On 10.08.21 12:33, Jan Kiszka via Xenomai wrote:
> On 10.08.21 12:23, Florian Bezdeka wrote:
>> Hi!
>>
>> This series is based on the series posted by Song some time ago. The
>> testing part has been heavily reworked. Details are mentioned in the 
>> description of the last patch.
>>
>> @Jan: Patch 1 and 2 are re-sends. They are not directly related to the 
>> y2038 stuff but the testsuite might fail if they are not applied.
>>
>> Testing was done on x86 only so far, internal CI is still running but no
>> problems expected.
>>
>> Best regards,   
>> Florian
>>
>> Changes in v5:
>>   - Patch 5: Integrated fixes already made by Jan on next 
>>   - Patch 5: Fix typo
>>
> 
> Is this series equivalent with bb64c8c66aeec3b5ead55fcfa9c79efda8064f7f
> in next? Or do I have to replace next with it? Or do I only have to
> replace bb64c8c66a (patch 5)?
> 

Anyway, just pulled them all and put this as well as the mq series on
top of new next.

Thanks,
Jan

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux


      reply	other threads:[~2021-08-10 10:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-10 10:23 [PATCH v5 0/5] y2038: Add mutex_timedlock64() support Florian Bezdeka
2021-08-10 10:23 ` [PATCH v5 1/5] smokey: posix_mutex: Fix mutex/smokey_barrier leak Florian Bezdeka
2021-08-10 10:23 ` [PATCH v5 2/5] cobalt/posix/mutex: Harmonize pthread_mutex_timedlock() and sem_timedwait() Florian Bezdeka
2021-08-10 10:23 ` [PATCH v5 3/5] y2038: cobalt/posix/mutex: Adding mutex_timedlock64 Florian Bezdeka
2021-08-10 10:23 ` [PATCH v5 4/5] y2038: lib/cobalt/mutex: dispatch mutex_timedlock Florian Bezdeka
2021-08-10 10:23 ` [PATCH v5 5/5] y2038: testsuite/smokey/y2038: Adding test cases for mutex_timedlock64() Florian Bezdeka
2021-08-10 10:33 ` [PATCH v5 0/5] y2038: Add mutex_timedlock64() support Jan Kiszka
2021-08-10 10:38   ` Jan Kiszka [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=046bb3ac-3e5c-f8b2-c1d7-5225329d3814@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=florian.bezdeka@siemens.com \
    --cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.