From: Dan Carpenter <dan.carpenter@oracle.com>
To: Minas Harutyunyan <minas.harutyunyan@synopsys.com>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
Maynard CABIENTE <maynard.cabiente@raritan.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Felipe Balbi <felipe.balbi@linux.intel.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: usb: dwc2: Revert "usb: dwc2: Disable all EP's on disconnect"
Date: Fri, 7 Dec 2018 17:40:45 +0300 [thread overview]
Message-ID: <20181207144045.GT3073@unbuntlaptop> (raw)
On Fri, Dec 07, 2018 at 02:13:18PM +0000, Minas Harutyunyan wrote:
>
> My patch doesn't pass sparse checking: "warning: context imbalance in
> 'dwc2_hsotg_core_init_disconnected' - unexpected unlock". Sparse persist!
> So, I need to re-work patch. Can I use your idea with
> dwc2_hsotg_ep_disable_lock() function to prepare new one?
>
Sparse lock checking is pretty crap, and I wouldn't go out of my way
normally to make it happy... But of course you can use my idea.
regards,
dan carpenter
next reply other threads:[~2018-12-07 14:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 14:40 Dan Carpenter [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-07 14:13 usb: dwc2: Revert "usb: dwc2: Disable all EP's on disconnect" Minas Harutyunyan
2018-12-07 11:20 Minas Harutyunyan
2018-12-07 10:15 Dan Carpenter
2018-12-07 10:11 Felipe Balbi
2018-12-07 9:58 Minas Harutyunyan
2018-12-07 9:50 Felipe Balbi
2018-12-07 9:06 Minas Harutyunyan
2018-12-07 9:06 Minas Harutyunyan
2018-12-06 23:09 Maynard CABIENTE
2018-12-06 15:07 Marek Szyprowski
2018-12-06 15:03 Marek Szyprowski
2018-12-06 14:52 Dan Carpenter
2018-12-05 12:52 Minas Harutyunyan
2018-12-04 13:29 Dan Carpenter
2018-12-04 12:34 Minas Harutyunyan
2018-11-23 14:43 Dan Carpenter
2018-11-23 9:49 Marek Szyprowski
2018-11-22 6:53 Minas Harutyunyan
2018-11-21 15:45 Marek Szyprowski
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=20181207144045.GT3073@unbuntlaptop \
--to=dan.carpenter@oracle.com \
--cc=b.zolnierkie@samsung.com \
--cc=felipe.balbi@linux.intel.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=maynard.cabiente@raritan.com \
--cc=minas.harutyunyan@synopsys.com \
/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).