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] [thread-next>] [day] [month] [year] [list]
Message-ID: <87a7efgxw7.fsf@linux.intel.com>
Date:   Tue, 18 Jun 2019 10:23:20 +0300
From:   Felipe Balbi <balbi@...nel.org>
To:     Lee Jones <lee.jones@...aro.org>
Cc:     alokc@...eaurora.org, agross@...nel.org, david.brown@...aro.org,
        bjorn.andersson@...aro.org, gregkh@...uxfoundation.org,
        ard.biesheuvel@...aro.org, jlhugo@...il.com,
        linux-arm-msm@...r.kernel.org, linux-usb@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [RESEND v4 0/4] I2C: DWC3 USB: Add support for ACPI based AArch64 Laptops


Hi,

Lee Jones <lee.jones@...aro.org> writes:
> On Mon, 17 Jun 2019, Felipe Balbi wrote:
>
>> Lee Jones <lee.jones@...aro.org> writes:
>> 
>> > This patch-set ensures the kernel is bootable on the newly released
>> > AArch64 based Laptops using ACPI configuration tables.  The Pinctrl
>> > changes have been accepted, leaving only I2C (keyboard, touchpad,
>> > touchscreen, fingerprint, etc, HID device) and USB (root filesystem,
>> > camera, networking, etc) enablement.
>> >
>> > RESEND: Stripped I2C patches as they have also been merged into
>> >         their respective subsystem.
>> >
>> > v4:
>> >  * Collecting Acks
>> >  * Adding Andy Gross' new email
>> >  * Removing applied Pinctrl patches
>> >
>> > Lee Jones (4):
>> >   soc: qcom: geni: Add support for ACPI
>> >   usb: dwc3: qcom: Add support for booting with ACPI
>> >   usb: dwc3: qcom: Start USB in 'host mode' on the SDM845
>> >   usb: dwc3: qcom: Improve error handling
>> 
>> pushed to testing/next
>
> Sounds promising, thanks Felipe.
>
> OOI, what is your process?
>
> How does do the patches typically sit in there?

I'll probably merge to my 'next' branch today. I leave them in
testing/next for a couple days, usually, so 0-day can run its thing and
I get a chance of at least boot testing on our machines in the lab here.

Since this doesn't touch anything "generic", I don't _have_ to boot
test, so I'll probably merge to 'next' today.

-- 
balbi

Download attachment "signature.asc" of type "application/pgp-signature" (833 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ