From: Linus Walleij <linus.walleij@linaro.org>
To: Jonathan Cameron <jic23@kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: 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: Sun, 9 May 2021 17:29:10 +0200 [thread overview]
Message-ID: <CACRpkdZ2mC5V6PdphmtmtQKHZwPfc7mVgZ-FH3io2ihB8foA4g@mail.gmail.com> (raw)
In-Reply-To: <20210509111925.52f3f4e3@jic23-huawei>
On Sun, May 9, 2021 at 12:18 PM Jonathan Cameron <jic23@kernel.org> wrote:
> On Sat, 8 May 2021 20:21:08 +0200
> Linus Walleij <linus.walleij@linaro.org> wrote:
> > Unless you really like to base your work on Gregs tree for
> > some reason or other, that is.
>
> Definitely appreciate Greg's help (and patience), but no
> particularly strong reason to waste his time dealing with my
> mess ups. Hopefully they'll reduce now IIO trees are going directly
> into linux-next though.
I'd suggest to move to sending pulls to Torvalds directly
for IIO to cut the intermediary staging tree step, since
now the subsystem is pretty large and see a bunch of
frequent fixes that need an express path to Torvalds.
Pushing through Greg per se isn't really the problem,
I think the problem is that IIO is going through the
staging tree which (I guess) isn't a high priority activity
and not expected to carry any serious critical fixes and
I guess this can cause lags.
Maybe Greg has some other branch to take in IIO
fixes and for-next but I don't really see the point.
The IIO left in the staging tree is just regular staging
business at this point, the main IIO is much more
important.
Linus 2: would pulling the IIO tree directly work for
you if Jonathan makes up his mind in favor for that?
Yours,
Linus Walleij
next prev parent reply other threads:[~2021-05-09 15:29 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 [this message]
2021-05-10 6:48 ` Greg KH
2021-05-18 0:31 ` Linus Walleij
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=CACRpkdZ2mC5V6PdphmtmtQKHZwPfc7mVgZ-FH3io2ihB8foA4g@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).