linux-kernel - Re: [PATCH v36 01/31] xhci: sideband: add initial api to register a secondary interrupter entity

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 for Android: free password hash cracker in your pocket

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

Message-ID: <87746e66-84c1-4ff3-8b69-fbee1664eff6@quicinc.com>
Date: Thu, 27 Mar 2025 09:12:12 -0700
From: Wesley Cheng <quic_wcheng@...cinc.com>
To: Puma Hsu <pumahsu@...gle.com>, Greg KH <gregkh@...uxfoundation.org>
CC: <srinivas.kandagatla@...aro.org>, <mathias.nyman@...el.com>,
        <perex@...ex.cz>, <conor+dt@...nel.org>, <dmitry.torokhov@...il.com>,
        <corbet@....net>, <broonie@...nel.org>, <lgirdwood@...il.com>,
        <krzk+dt@...nel.org>, <pierre-louis.bossart@...ux.intel.com>,
        <Thinh.Nguyen@...opsys.com>, <tiwai@...e.com>, <robh@...nel.org>,
        <linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>,
        <linux-sound@...r.kernel.org>, <linux-input@...r.kernel.org>,
        <linux-usb@...r.kernel.org>, <linux-arm-msm@...r.kernel.org>,
        <linux-doc@...r.kernel.org>,
        Mathias Nyman <mathias.nyman@...ux.intel.com>
Subject: Re: [PATCH v36 01/31] xhci: sideband: add initial api to register a
 secondary interrupter entity



On 3/27/2025 3:14 AM, Puma Hsu wrote:
> On Thu, Mar 27, 2025 at 3:02 PM Greg KH <gregkh@...uxfoundation.org> wrote:
>>
>> On Thu, Mar 27, 2025 at 02:27:00PM +0800, Puma Hsu wrote:
>>> Hi,
>>>
>>> We have implemented and verified the USB audio offloading feature with
>>> the xhci sideband driver on our Google Pixel products. We would
>>> appreciate it if this solution can be accepted. Thank you all for the
>>> work!
>>>
>>
>> Great, can you properly send a "Tested-by:" line for this against the
>> 00/XX email so that it will be properly saved?
>>
> 
> We(Google Pixel) only use the xhci sideband related changes and two
> changes in the sound card driver. For the details, what we actually
> tested are patch [01], [02], [03], [04], [05], [06], [08], and [12].
> Do I still send the "Tested-by:" line to 00/31 email? Or should I just
> send the "Tested-by:" line to the 8 changes above? (I added
> "Tested-by" line for this [01/31] first.)
> 
>> Also, I think a new version of the series is coming, can you test that
>> to verify it works properly?  We have to wait until after -rc1 is out
>> anyway.
>>
> 
> I think this v36 is the last version of the series as I discussed with
> QCOM Wesley. And for sure I will test it if they do have a new
> version.
> 

Hi Puma,

I'm discussing with Stephan on the QC specific stuff, so the common changes
won't change on v37.  Please provide your tested-by tags for each commit,
so I can carry them accordingly on the next submission.  If I do end up
making changes to any of the common patches, I will remove your tested by
tag, which means you might have to test it again.

Thanks
Wesley Cheng