linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	Linux PM <linux-pm@vger.kernel.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-i2c <linux-i2c@vger.kernel.org>
Subject: Re: RFC: a failing pm_runtime_get increases the refcnt?
Date: Tue, 30 Jun 2020 21:48:58 +0200	[thread overview]
Message-ID: <20200630194858.GC999@ninjato> (raw)
In-Reply-To: <20200614140717.heceqlwq75w5if5s@katana>

[-- Attachment #1: Type: text/plain, Size: 389 bytes --]


> However, that probably means that for most patches I am getting, the
> better fix would be to remove the error checking? (I assume most people
> put the error check in there to be on the "safe side" without having a
> real argument to really do it.)

Kindly asking for more input here: A better answer to all these patches
is to ask if the error checking could not be removed instead?


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-06-30 19:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-14  9:07 RFC: a failing pm_runtime_get increases the refcnt? Wolfram Sang
2020-06-14  9:34 ` Andy Shevchenko
2020-06-14  9:42   ` Andy Shevchenko
2020-06-14 10:00     ` Geert Uytterhoeven
2020-06-14 10:04       ` Geert Uytterhoeven
2020-06-14 10:44         ` Andy Shevchenko
2020-06-14 12:42       ` Andy Shevchenko
2020-06-14 13:59       ` Rafael J. Wysocki
2020-06-14 14:07         ` Wolfram Sang
2020-06-30 19:48           ` Wolfram Sang [this message]
2020-06-14 13:50 ` Rafael J. Wysocki

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=20200630194858.GC999@ninjato \
    --to=wsa@kernel.org \
    --cc=andy.shevchenko@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=rafael@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).