From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Char/Misc driver updates 5.19-rc1
Date: Fri, 3 Jun 2022 12:46:45 +0200 [thread overview]
Message-ID: <YpnmlbveC6F1srSZ@kroah.com> (raw)
In-Reply-To: <YpnmYB8SN5dPweLV@kroah.com>
On Fri, Jun 03, 2022 at 12:45:52PM +0200, Greg KH wrote:
> The following changes since commit 672c0c5173427e6b3e2a9bbb7be51ceeec78093a:
>
> Linux 5.18-rc5 (2022-05-01 13:57:58 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git tags/char-misc-5.19-rc1
>
> for you to fetch changes up to 90de6805267f8c79cd2b1a36805071e257c39b5c:
>
> habanalabs: use separate structure info for each error collect data (2022-05-22 21:01:21 +0200)
>
> ----------------------------------------------------------------
> Char / Misc / Other smaller driver subsystem updates for 5.19-rc1
>
> Here is the large set of char, misc, and other driver subsystem updates
> for 5.19-rc1. The merge request for this has been delayed as I wanted
> to get lots of linux-next testing due to some late arrivals of changes
> for the habannalabs driver.
>
> Highlights of this merge are:
> - habanalabs driver updates for new hardware types and fixes and
> other updates
> - IIO driver tree merge which includes loads of new IIO drivers
> and cleanups and additions
> - PHY driver tree merge with new drivers and small updates to
> existing ones
> - interconnect driver tree merge with fixes and updates
> - soundwire driver tree merge with some small fixes
> - coresight driver tree merge with small fixes and updates
> - mhi bus driver tree merge with lots of updates and new device
> support
> - firmware driver updates
> - fpga driver updates
> - lkdtm driver updates (with a merge conflict, more on that
> below)
> - extcon driver tree merge with small updates
> - lots of other tiny driver updates and fixes and cleanups, full
> details in the shortlog.
>
> All of these have been in linux-next for almost 2 weeks with no reported
> problems.
>
> Note, there are 3 merge conflicts when merging this with your tree:
> - MAINTAINERS, should be easy to resolve
> - drivers/slimbus/qcom-ctrl.c, should be straightforward
> resolution
> - drivers/misc/lkdtm/stackleak.c, not an easy resolution. This
> has been noted in the linux-next tree for a while, and
> resolved there, here's a link to the resolution that Stephen
> came up with and that Kees says is correct:
> https://lore.kernel.org/r/20220509185344.3fe1a354@canb.auug.org.au
>
> I will be glad to provide a merge point that contains these resolutions
> if that makes things any easier for you.
I have now done so, and that can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git torvalds_merge
If there are any other issues here, please let me know.
thanks,
greg k-h
next prev parent reply other threads:[~2022-06-03 10:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 10:45 [GIT PULL] Char/Misc driver updates 5.19-rc1 Greg KH
2022-06-03 10:46 ` Greg KH [this message]
2022-06-03 18:44 ` Linus Torvalds
2022-06-03 18: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=YpnmlbveC6F1srSZ@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--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