On Mon, Aug 2, 2021 at 10:43 AM Jack Winch <sunt.un.morcov@xxxxxxxxx> wrote: > > Hello Bartosz, > > I am most certainly being *dense* here, but which libgpiod branch > should I be applying this patch series to? Also, what other patch > series is this particular set of patches dependent on? I tried to > apply against master and next/libgpiod-2.0 without much success this > weekend. Also, just for clarity, how is the next/libgpiod-2.0 branch > being used at current? Which and at what point are you applying > patches to this particular branch? > It's actually my fault. Let me explain: the development of the v2 API for the entire project (C, C++ and Python parts) happens in the next/libgpiod-2.0 branch of git://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git I squash the new changes into the big patch with the plan of resending it for a final review once we agree on the interface (more or less anyway). That will allow the repo to remain bisectable. Then we'll be able to fine-tune different elements. > Once I've got over this basic hurdle, I'd like to do a 'holistic' > review of this patch series. As I've not been following changes to > either the kernel subsystem or user library as of late, I feel this > approach to be more appropriate and thorough. > Maybe you could wait until I post v4? I'm addressing a lot of issues in this revision. Previous small patches have already been squashed and they concerned the core C library anyway. > Finally, what is the target deadline for completion of the v2 API? > There's no target, it'll be ready when it's done. Bart PS How did the move go?