This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH v8 2/3] y2038: Provide conversion helpers for struct __timespec64
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Lukasz Majewski <lukma at denx dot de>
- Cc: Alistair Francis <alistair23 at gmail dot com>, Alistair Francis <alistair dot francis at wdc dot com>, Zack Weinberg <zackw at panix dot com>, Arnd Bergmann <arnd at arndb dot de>, GNU C Library <libc-alpha at sourceware dot org>, Adhemerval Zanella <adhemerval dot zanella at linaro dot org>, Florian Weimer <fweimer at redhat dot com>, Carlos O'Donell <carlos at redhat dot com>, Stepan Golosunov <stepan at golosunov dot pp dot ru>
- Date: Thu, 19 Sep 2019 22:17:47 +0000
- Subject: Re: [PATCH v8 2/3] y2038: Provide conversion helpers for struct __timespec64
- Ironport-sdr: mBu7yi3GXTb8MjJnzSr2rs+4hrwiX5CMVwWfG1THo059Xelf5zzFN0+2CkiTFmJv30Zn+hE0Gt mIbUHVc/689TLtA8T7hZ1QZx42Ne6kbvyzaAhKR0KHvshRcLvpqRMJSpaRpKM+PiWS3ChPb/4l QeIG6j/Nl2NtbYa9ZqACsZN3yDIzhV9pWEcNWcyyMO4TpbHLKPCtx87d6uBPBySh9+xce7ebTp ktVEtYryYA9FHt5f/u0Kod5bdC8Y9QndvqzDO0n6p5SIaNvxWZZ5hjqT9XzWuAOKN+SzliQh+i 12Y=
- Ironport-sdr: hbnp63iJOPD2HxqWeuwtMARc47uGv0yLPgRf2rZ98XNqpfZUs6C3CXmpfocaKdiT1hfxvY9Avo F885geL4LyKxet++SZ3H5yTq1Ubmwie2CqO6X1hwu/BD+bKKS75Qev7EXwIfZ2Vr2URb4t78od ALervfB6lqusLL0ISjp6/7LxTR4EQFkBlnd7EvoSSYkmAW2A3P8fAtPrHcGiWw/RpA+cHuxAvR RdC0BsskbuT9Wv/l+/0eoYWzlYztxToNGoUT5d+kpZP2yEiEp9Bd1mvA+KQOZSe+8qtCS7qtYW 2RE=
- References: <20190918211603.8444-1-lukma@denx.de> <20190918211603.8444-3-lukma@denx.de> <alpine.DEB.2.21.1909192016030.11875@digraph.polyomino.org.uk> <20190919232106.160135df@jawa> <alpine.DEB.2.21.1909192126500.11875@digraph.polyomino.org.uk> <20190920000338.70441394@jawa>
On Fri, 20 Sep 2019, Lukasz Majewski wrote:
> So if I understood your proposed workflow:
>
> First the patch 1/3 get applied to glibc -master branch. Then on top of
> it I shall send the corrected 2/3 (independently from review of 3/3).
>
> Am I correct?
Yes.
In general, if a patch is approved, and it doesn't depend on any other
unapproved patches, it should be committed (so making future revisions of
any containing patch series smaller and easier to review) - unless there's
some special reason to delay the commit until subsequent patches are ready
as well.
--
Joseph S. Myers
joseph@codesourcery.com