All of lore.kernel.org
 help / color / mirror / Atom feed
From: Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"lee.jones@linaro.org" <lee.jones@linaro.org>,
	"ben@simtec.co.uk" <ben@simtec.co.uk>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: patch "usb: dwc2: gadget: Do not read GINTMSK2" added to usb-testing
Date: Fri, 3 Jul 2020 08:11:50 +0000	[thread overview]
Message-ID: <952b3264-41f6-3ffd-fe41-e4e3afe5bba2@synopsys.com> (raw)
In-Reply-To: <6eb59328-78c3-f925-45bb-fdfcf032814c@synopsys.com>

Added linux-usb@vger.kernel.org to recipient list.

On 7/3/2020 11:43 AM, Minas Harutyunyan wrote:
> Hi,
> 
> On 7/3/2020 11:34 AM, gregkh@linuxfoundation.org wrote:
>>
>> This is a note to let you know that I've just added the patch titled
>>
>>       usb: dwc2: gadget: Do not read GINTMSK2
>>
>> to my usb git tree which can be found at
>>       git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
>> in the usb-testing branch.
>>
>> The patch will show up in the next release of the linux-next tree
>> (usually sometime within the next 24 hours during the week.)
>>
>> The patch will be merged to the usb-next branch sometime soon,
>> after it passes testing, and the merge window is open.
>>
>> If you have any questions about this process, please let me know.
>>
> 

This patch is not correct. Please read below.

>>
>>   From 4f1ae9d60adb3d4f9b8ea94f02bfc883f954bed6 Mon Sep 17 00:00:00 2001
>> From: Lee Jones <lee.jones@linaro.org>
>> Date: Thu, 2 Jul 2020 15:46:04 +0100
>> Subject: usb: dwc2: gadget: Do not read GINTMSK2
>> MIME-Version: 1.0
>> Content-Type: text/plain; charset=UTF-8
>> Content-Transfer-Encoding: 8bit
>>
>> The value of GINTMSK2 hasn't been checked since the inception of
>> dwc2_gadget_wkup_alert_handler() in 2018.
>>
>> 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@synopsys.com>
>> Cc: Ben Dooks <ben@simtec.co.uk>
>> Signed-off-by: Lee Jones <lee.jones@linaro.org>
>> Link: https://urldefense.com/v3/__https://lore.kernel.org/r/20200702144625.2533530-10-lee.jones@linaro.org__;!!A4F2R9G_pg!MlXvn0tSkTvsGZZoWD5zq_1Owq-U-DIHNaHoyU1OfG8TwGGQBEfo9g0n9r2TxvQ$
>> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> ---
>>    drivers/usb/dwc2/gadget.c | 2 --
>>    1 file changed, 2 deletions(-)
>>
>> diff --git a/drivers/usb/dwc2/gadget.c b/drivers/usb/dwc2/gadget.c
>> index 1def9000f936..ea7c9c73b4ff 100644
>> --- a/drivers/usb/dwc2/gadget.c
>> +++ b/drivers/usb/dwc2/gadget.c
>> @@ -256,10 +256,8 @@ int dwc2_hsotg_tx_fifo_total_depth(struct dwc2_hsotg *hsotg)
>>    static void dwc2_gadget_wkup_alert_handler(struct dwc2_hsotg *hsotg)
>>    {
>>    	u32 gintsts2;
>> -	u32 gintmsk2;
>>    
>>    	gintsts2 = dwc2_readl(hsotg, GINTSTS2);
>> -	gintmsk2 = dwc2_readl(hsotg, GINTMSK2);
>>    
>>    	if (gintsts2 & GINTSTS2_WKUP_ALERT_INT) {
>>    		dev_dbg(hsotg->dev, "%s: Wkup_Alert_Int\n", __func__);


Lee, 'gintsts2' can't be removed. Just, please add follow line after
reading gintmsk2:

  	gintsts2 &= gintmsk2;


Please add also "Fixes:" tag and submit v2.

Thanks,
Minas

>>

       reply	other threads:[~2020-07-03  8:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <15937616791863@kroah.com>
     [not found] ` <6eb59328-78c3-f925-45bb-fdfcf032814c@synopsys.com>
2020-07-03  8:11   ` Minas Harutyunyan [this message]
     [not found]   ` <20200703081937.GA2396807@kroah.com>
2020-07-03  8:27     ` patch "usb: dwc2: gadget: Do not read GINTMSK2" added to usb-testing Minas Harutyunyan

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=952b3264-41f6-3ffd-fe41-e4e3afe5bba2@synopsys.com \
    --to=minas.harutyunyan@synopsys.com \
    --cc=ben@simtec.co.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=lee.jones@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.