From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: dinghao.liu@zju.edu.cn
Cc: kjlu@umn.edu, Bin Liu <b-liu@ti.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH] [v2] usb: musb: Fix runtime PM imbalance on error
Date: Fri, 22 May 2020 07:32:49 +0200 [thread overview]
Message-ID: <20200522053249.GA616391@kroah.com> (raw)
In-Reply-To: <2ca9a5fc.be29f.1723ad51c1d.Coremail.dinghao.liu@zju.edu.cn>
On Fri, May 22, 2020 at 01:22:24PM +0800, dinghao.liu@zju.edu.cn wrote:
> Sorry, it's my carelessness. In v1 I added pm_runtime_put_autosuspend()
> after copy_from_user() to fix this problem. Since copy_from_user() is
> moved to the beginning now, we need not to add PM decrement.
THat's fine, please put that information in a v3 and resend it.
thanks,
greg k-h
prev parent reply other threads:[~2020-05-22 5:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 2:59 [PATCH] [v2] usb: musb: Fix runtime PM imbalance on error Dinghao Liu
2020-05-22 5:12 ` Greg Kroah-Hartman
2020-05-22 5:22 ` dinghao.liu
2020-05-22 5:32 ` Greg Kroah-Hartman [this message]
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=20200522053249.GA616391@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=b-liu@ti.com \
--cc=dinghao.liu@zju.edu.cn \
--cc=kjlu@umn.edu \
--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).