From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: devel@linuxdriverproject.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Staging/IIO driver patches for 5.2-rc1
Date: Tue, 7 May 2019 20:01:08 +0200 [thread overview]
Message-ID: <20190507180108.GC11857@kroah.com> (raw)
In-Reply-To: <20190507175853.GA11568@kroah.com>
On Tue, May 07, 2019 at 07:58:53PM +0200, Greg KH wrote:
> The following changes since commit 085b7755808aa11f78ab9377257e1dad2e6fa4bb:
>
> Linux 5.1-rc6 (2019-04-21 10:45:57 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git tags/staging-5.2-rc1
>
> for you to fetch changes up to e2a5be107f52cefb9010ccae6f569c3ddaa954cc:
>
> staging: kpc2000: kpc_spi: Fix build error for {read,write}q (2019-05-03 08:23:20 +0200)
>
> ----------------------------------------------------------------
> Staging / IIO driver patches for 5.2-rc1
>
> Here is the big staging and iio driver update for 5.2-rc1.
>
> Lots of tiny fixes all over the staging and IIO driver trees here, along
> with some new IIO drivers.
>
> Also we ended up deleting two drivers, making this pull request remove a
> few hundred thousand lines of code, always a nice thing to see. Both of
> the drivers removed have been replaced with "real" drivers in their
> various subsystem directories, and they will be coming to you from those
> locations during this merge window.
>
> There are some core vt/selection changes in here, that was due to some
> cleanups needed for the speakup fixes. Those have all been acked by the
> various subsystem maintainers (i.e. me), so those are ok.
>
> We also added a few new drivers, for some odd hardware, giving new
> developers plenty to work on with basic coding style cleanups to come in
> the near future.
>
> Other than that, nothing unusual here.
>
> All of these have been in linux-next for a while with no reported
> issues, other than an odd gcc warning for one of the new drivers that
> should be fixed up soon.
>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
I forgot to mention that the "counter" subsystem was added in here as
well, as it is needed by the IIO drivers and subsystem. It's reflected
in the shortlog and diffstat, but I forgot to cover it in the text
above, sorry.
thanks,
greg k-h
next prev parent reply other threads:[~2019-05-07 18:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 17:58 [GIT PULL] Staging/IIO driver patches for 5.2-rc1 Greg KH
2019-05-07 18:01 ` Greg KH [this message]
2019-05-07 20:33 ` Linus Torvalds
2019-05-08 9:49 ` Greg KH
2019-05-07 20:50 ` 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=20190507180108.GC11857@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=devel@linuxdriverproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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