linux-kernel - Re: [PATCH v4 0/6] Introduce PMIC based USB type C detection

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <159364222729.10880.15242810692121676047.b4-ty@kernel.org>
Date:   Wed, 01 Jul 2020 23:23:57 +0100
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com, Wesley Cheng <wcheng@...eaurora.org>,
        heikki.krogerus@...ux.intel.com, gregkh@...uxfoundation.org,
        mark.rutland@....com, robh+dt@...nel.org,
        bjorn.andersson@...aro.org, agross@...nel.org
Cc:     linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
        devicetree@...r.kernel.org, linux-usb@...r.kernel.org,
        jackp@...eaurora.org, rdunlap@...radead.org
Subject: Re: [PATCH v4 0/6] Introduce PMIC based USB type C detection

On Fri, 26 Jun 2020 11:55:10 -0700, Wesley Cheng wrote:
> Changes in v4:
>  - Modified qcom,pmic-typec binding to include the SS mux and the DRD remote
>    endpoint nodes underneath port@1, which is assigned to the SSUSB path
>    according to usb-connector
>  - Added usb-connector reference to the typec dt-binding
>  - Added tags to the usb type c and vbus nodes
>  - Removed "qcom" tags from type c and vbus nodes
>  - Modified Kconfig module name, and removed module alias from the typec driver
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/2] regulator: Add support for QCOM PMIC VBUS booster
      commit: 4fe66d5a62fbe1b050e783e7a01f986632c08c44
[2/2] regulator: Add dt-binding for QCOM PMIC VBUS output regulator
      commit: a824bab7c62d7ecd8ccfe9693da7ccb7e4683760

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark