netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Navid Emamdoost <navid.emamdoost@gmail.com>
Cc: Kalle Valo <kvalo@codeaurora.org>,
	"David S. Miller" <davem@davemloft.net>,
	Johannes Berg <johannes.berg@intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Hari Nagalla <hnagalla@gmail.com>,
	"Jason A. Donenfeld" <Jason@zx2c4.com>,
	Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
	Maital Hahn <maitalm@ti.com>,
	Fuqian Huang <huangfq.daxian@gmail.com>,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, emamd001@umn.edu, wu000273@umn.edu,
	kjlu@umn.edu, smccaman@umn.edu
Subject: Re: [PATCH] wlcore: mesh: handle failure case of pm_runtime_get_sync
Date: Fri, 5 Jun 2020 09:49:38 -0700	[thread overview]
Message-ID: <20200605164938.GH37466@atomide.com> (raw)
In-Reply-To: <20200605032733.49846-1-navid.emamdoost@gmail.com>

* Navid Emamdoost <navid.emamdoost@gmail.com> [200605 03:28]:
> Calling pm_runtime_get_sync increments the counter even in case of
> failure, causing incorrect ref count. Call pm_runtime_put if
> pm_runtime_get_sync fails.

Looks like we have a similar patch already in Linux next,
care to check?

Regards,

Tony

  reply	other threads:[~2020-06-05 16:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-05  3:27 [PATCH] wlcore: mesh: handle failure case of pm_runtime_get_sync Navid Emamdoost
2020-06-05 16:49 ` Tony Lindgren [this message]
2020-07-15  8:35 ` Kalle Valo

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=20200605164938.GH37466@atomide.com \
    --to=tony@atomide.com \
    --cc=Jason@zx2c4.com \
    --cc=davem@davemloft.net \
    --cc=emamd001@umn.edu \
    --cc=emmanuel.grumbach@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hnagalla@gmail.com \
    --cc=huangfq.daxian@gmail.com \
    --cc=johannes.berg@intel.com \
    --cc=kjlu@umn.edu \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=maitalm@ti.com \
    --cc=navid.emamdoost@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=smccaman@umn.edu \
    --cc=tglx@linutronix.de \
    --cc=wu000273@umn.edu \
    /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).