From: Jonathan Cameron <jic23@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
devel@linuxdriverproject.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
William Breathitt Gray <vilhelm.gray@gmail.com>
Subject: Re: [GIT PULL] Staging/IIO driver fixes for 5.11-rc5
Date: Thu, 28 Jan 2021 19:45:51 +0000 [thread overview]
Message-ID: <20210128194551.76c76cfe@archlinux> (raw)
In-Reply-To: <YA7Q0XZMIdudb6x9@kroah.com>
On Mon, 25 Jan 2021 15:08:17 +0100
Greg KH <gregkh@linuxfoundation.org> wrote:
> On Sun, Jan 24, 2021 at 11:31:59AM -0800, Linus Torvalds wrote:
> > On Sun, Jan 24, 2021 at 4:58 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> > >
> > > David Lechner (1):
> > > counter:ti-eqep: remove floor
> >
> > I'm not sure why that ti-eqep counter driver seems to be in your
> > "iio/staging" pile rather than "char/misc", but whatever..
>
> Jonathan said why that was needed, I think it was due to fixes in the
> counter core code, but he can verify this better than I can...
Hi Linus / Greg,
Bit of history involved here...
The counter drivers started out as just another sensor type
under IIO, but ended up pushing the boundaries of the ABI a lot -
ultimately making it clear that they really didn't fit in IIO.
William came up with a better abstraction / framework that
became drivers/counter/, but currently the patch flow for
drivers/counter/ is sufficiently low that I handle their
patches along side IIO rather than via a separate tree.
There is also a cross dependency because of legacy IIO ABI
though we are aiming to drop that either this cycle or next.
Hope that clears it up. If either of you would prefer
it a different way in future let me know.
This particular fix was local to the driver - it was pretending
it supported something that hardware couldn't actually do.
Thanks,
Jonathan
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2021-01-28 20:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 12:58 [GIT PULL] Staging/IIO driver fixes for 5.11-rc5 Greg KH
2021-01-24 19:31 ` Linus Torvalds
2021-01-25 14:08 ` Greg KH
2021-01-28 19:45 ` Jonathan Cameron [this message]
2021-01-24 19:33 ` pr-tracker-bot
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=20210128194551.76c76cfe@archlinux \
--to=jic23@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--cc=vilhelm.gray@gmail.com \
/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