From: Mark Brown <broonie@kernel.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/5] regulator: core: have regulator_dev_lookup() return ERR_PTR-encoded errors
Date: Mon, 6 Feb 2017 00:49:23 +0100 [thread overview]
Message-ID: <20170205234923.55wvhe7uo6l54hc2@sirena.org.uk> (raw)
In-Reply-To: <20170204181921.GC12980@dtor-ws>
[-- Attachment #1: Type: text/plain, Size: 525 bytes --]
On Sat, Feb 04, 2017 at 10:19:21AM -0800, Dmitry Torokhov wrote:
> Instead of returning both regulator_dev structure as return value and
> auxiliary error code in 'ret' argument, let's switch to using ERR_PTR
> encoded values. This makes it more obvious what is going on at call sites.
I did apply this but GNOME has decided to try to force gnome-keyring's
SSH agent on us with renewed force so until I fix that I can't use the
key on my smartcard to 2FA or push to kernel.org :/ It'll appear some
time tomorrow hopefully.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-02-05 23:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 21:56 [PATCH 1/5] regulator: core: remove dead code in _regulator_get() Dmitry Torokhov
2017-02-03 21:56 ` [PATCH 2/5] regulator: core: have regulator_dev_lookup() return ERR_PTR-encoded errors Dmitry Torokhov
2017-02-04 10:11 ` Mark Brown
2017-02-04 18:19 ` [PATCH v2 " Dmitry Torokhov
2017-02-05 14:49 ` Mark Brown
2017-02-05 23:49 ` Mark Brown [this message]
2017-02-06 13:37 ` Applied "regulator: core: have regulator_dev_lookup() return ERR_PTR-encoded errors" to the regulator tree Mark Brown
2017-02-03 21:56 ` [PATCH 3/5] regulator: core: have _regulator_get() accept get_type argument Dmitry Torokhov
2017-02-04 10:48 ` Applied "regulator: core: have _regulator_get() accept get_type argument" to the regulator tree Mark Brown
2017-02-03 21:56 ` [PATCH 4/5] regulator: core: simplify _regulator_get() Dmitry Torokhov
2017-02-04 10:34 ` Mark Brown
2017-02-04 18:27 ` Dmitry Torokhov
2017-02-05 16:08 ` Mark Brown
2017-02-08 18:34 ` Applied "regulator: core: simplify _regulator_get()" to the regulator tree Mark Brown
2017-02-03 21:56 ` [PATCH 5/5] regulator: core: lower severity level of message about using dummy supplies Dmitry Torokhov
2017-02-04 11:48 ` Mark Brown
2017-02-04 17:45 ` Dmitry Torokhov
2017-02-05 16:12 ` Mark Brown
2017-02-07 0:56 ` Dmitry Torokhov
2017-02-08 18:19 ` Mark Brown
2017-02-04 10:48 ` Applied "regulator: core: remove dead code in _regulator_get()" to the regulator tree Mark Brown
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=20170205234923.55wvhe7uo6l54hc2@sirena.org.uk \
--to=broonie@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@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).