From: Felipe Balbi <balbi@kernel.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: alokc@codeaurora.org, agross@kernel.org, david.brown@linaro.org,
bjorn.andersson@linaro.org, gregkh@linuxfoundation.org,
ard.biesheuvel@linaro.org, jlhugo@gmail.com,
linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND v4 0/4] I2C: DWC3 USB: Add support for ACPI based AArch64 Laptops
Date: Tue, 18 Jun 2019 10:23:20 +0300 [thread overview]
Message-ID: <87a7efgxw7.fsf@linux.intel.com> (raw)
In-Reply-To: <20190617132349.GI16364@dell>
[-- Attachment #1: Type: text/plain, Size: 1472 bytes --]
Hi,
Lee Jones <lee.jones@linaro.org> writes:
> On Mon, 17 Jun 2019, Felipe Balbi wrote:
>
>> Lee Jones <lee.jones@linaro.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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-06-18 7:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 12:51 [RESEND v4 0/4] I2C: DWC3 USB: Add support for ACPI based AArch64 Laptops Lee Jones
2019-06-17 12:51 ` [RESEND v4 1/4] soc: qcom: geni: Add support for ACPI Lee Jones
2019-06-19 5:52 ` Andy Gross
2019-06-19 6:05 ` Lee Jones
2019-06-17 12:51 ` [RESEND v4 2/4] usb: dwc3: qcom: Add support for booting with ACPI Lee Jones
2019-06-17 12:51 ` [RESEND v4 3/4] usb: dwc3: qcom: Start USB in 'host mode' on the SDM845 Lee Jones
2019-06-17 12:51 ` [RESEND v4 4/4] usb: dwc3: qcom: Improve error handling Lee Jones
2019-06-17 12:55 ` [RESEND v4 0/4] I2C: DWC3 USB: Add support for ACPI based AArch64 Laptops Felipe Balbi
2019-06-17 13:23 ` Lee Jones
2019-06-18 7:23 ` Felipe Balbi [this message]
2019-06-18 8:08 ` Lee Jones
2019-06-18 8:44 ` Felipe Balbi
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=87a7efgxw7.fsf@linux.intel.com \
--to=balbi@kernel.org \
--cc=agross@kernel.org \
--cc=alokc@codeaurora.org \
--cc=ard.biesheuvel@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=jlhugo@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).