From: Linus Walleij <linus.walleij@linaro.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Jonathan Cameron <jic23@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Alexandru Ardelean <aardelean@deviqon.com>,
linux-iio <linux-iio@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Paul Cercueil <paul@crapouillou.net>,
Nuno Sa <nuno.sa@analog.com>
Subject: Re: [PATCH] iio: core: return ENODEV if ioctl is unknown
Date: Tue, 18 May 2021 02:31:32 +0200 [thread overview]
Message-ID: <CACRpkdaNuGB+qpW-hjsGs5rC0k3nKwKDT0jUU6Jpon1JRf3MoQ@mail.gmail.com> (raw)
In-Reply-To: <YJjXU/mBKnmknItg@kroah.com>
On Mon, May 10, 2021 at 8:48 AM Greg KH <gregkh@linuxfoundation.org> 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.
Yours,
Linus Walleij
prev parent reply other threads:[~2021-05-18 0:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 14:43 [PATCH] iio: core: return ENODEV if ioctl is unknown Alexandru Ardelean
2021-05-04 7:10 ` Sa, Nuno
2021-05-04 9:04 ` Paul Cercueil
2021-05-05 12:52 ` Linus Walleij
2021-05-08 15:16 ` Jonathan Cameron
2021-05-08 18:21 ` Linus Walleij
2021-05-09 10:19 ` Jonathan Cameron
2021-05-09 15:29 ` Linus Walleij
2021-05-10 6:48 ` Greg KH
2021-05-18 0:31 ` Linus Walleij [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=CACRpkdaNuGB+qpW-hjsGs5rC0k3nKwKDT0jUU6Jpon1JRf3MoQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=aardelean@deviqon.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=paul@crapouillou.net \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).