[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5862f649-8058-7e39-cb43-2a4b09303333@synopsys.com>
Date: Tue, 21 Jul 2020 10:09:50 +0000
From: Minas Harutyunyan <Minas.Harutyunyan@...opsys.com>
To: Felipe Balbi <balbi@...nel.org>,
Minas Harutyunyan <Minas.Harutyunyan@...opsys.com>,
Lee Jones <lee.jones@...aro.org>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
CC: "linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
Ben Dooks <ben@...tec.co.uk>
Subject: Re: [PATCH v2 1/8] usb: dwc2: gadget: Make use of GINTMSK2
Hi Felipe,
On 7/21/2020 1:43 PM, Felipe Balbi wrote:
> Minas Harutyunyan <Minas.Harutyunyan@...opsys.com> writes:
>
>> On 7/15/2020 1:32 PM, Lee Jones wrote:
>>> The value obtained from GINTSTS2 should be masked with the GINTMSK2
>>> value. Looks like this has been broken since
>>> dwc2_gadget_wkup_alert_handler() was added back in 2018.
>>>
>>> Also fixes the following W=1 warning:
>>>
>>> drivers/usb/dwc2/gadget.c: In function ‘dwc2_gadget_wkup_alert_handler’:
>>> drivers/usb/dwc2/gadget.c:259:6: warning: variable ‘gintmsk2’ set but not used [-Wunused-but-set-variable]
>>> 259 | u32 gintmsk2;
>>> | ^~~~~~~~
>>>
>>> Cc: Minas Harutyunyan <hminas@...opsys.com>
>>> Cc: Ben Dooks <ben@...tec.co.uk>
>>> Fixes: 187c5298a1229 ("usb: dwc2: gadget: Add handler for WkupAlert interrupt")
>>> Signed-off-by: Lee Jones <lee.jones@...aro.org>
>>
>> Acked-by: Minas Harutyunyan <hminas@...opsys.com>
>
> Should I apply the entire series or only 1/8?
>
In this series only 2 patches are related to dwc2, which I'm already Acked:
[PATCH v2 1/8] usb: dwc2: gadget: Make use of GINTMSK2
[PATCH v2 2/8] usb: dwc2: gadget: Avoid pointless read of EP control
register
I can't acked other patches from this series, because they are not
related to dwc2.
Thanks,
Minas
Powered by blists - more mailing lists