Re: [PATCH] iio: core: return ENODEV if ioctl is unknown
From: Linus Walleij
Date: Mon May 17 2021 - 20:31:48 EST
On Mon, May 10, 2021 at 8:48 AM Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
> I can take IIO changes in my char/misc tree like many other driver
> subsystems go, if the staging portions are not involved. Otherwise, I
> really don't see the problem with it as-is, what problems is this
> causing at the moment?
It's in the thread: pipeline stalls, haha :)
It has happened more than once that Jonathan needs to wait for
things to percolate upstream before he can base new stuff on it.
Personally I've encountered fixes that are waiting in your tree
so that new fixes on fixes, or next development cannot be applied
because the fixes need to land in a tag upstream so that can be
merged in first as base for the new development. Essentially
any time patches with dependencies end up on two branches.
Also it takes a while after the merge window for you to move
branches to -rc1 or similar (whether through merge or rebase),
as is natural. Which will delay everything using those. It's just
a natural side-effect of hierarchy.
Nothing disastrous but it makes things congest. Maybe it can
be processed around, I don't exactly know the routine around
your trees and branches.