From: Mark Brown <broonie@kernel.org>
To: Sachin Kamat <sachin.kamat@linaro.org>
Cc: linux-kernel@vger.kernel.org, lgirdwood@gmail.com
Subject: Re: [PATCH 14/15] regulator: arizona-micsupp: Remove redundant error message
Date: Thu, 20 Feb 2014 01:38:28 +0900 [thread overview]
Message-ID: <20140219163828.GX2669@sirena.org.uk> (raw)
In-Reply-To: <1392720071-13503-14-git-send-email-sachin.kamat@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 131 bytes --]
On Tue, Feb 18, 2014 at 04:11:10PM +0530, Sachin Kamat wrote:
> kzalloc prints its own OOM message upon failure.
Applied, thanks.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-02-19 16:38 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 10:40 [PATCH 01/15] regulator: wm8350: Do not hardcode return value Sachin Kamat
2014-02-18 10:40 ` [PATCH 02/15] regulator: ti-abb: " Sachin Kamat
2014-02-19 13:07 ` Mark Brown
2014-02-18 10:40 ` [PATCH 03/15] regulator: ti-abb: Remove redundant error message Sachin Kamat
2014-02-19 13:07 ` Mark Brown
2014-02-18 10:41 ` [PATCH 04/15] regulator: max8973: " Sachin Kamat
2014-02-19 13:08 ` Mark Brown
2014-02-18 10:41 ` [PATCH 05/15] regulator: max8925: Do not hardcode return value Sachin Kamat
2014-02-19 13:08 ` Mark Brown
2014-02-18 10:41 ` [PATCH 06/15] regulator: lp872x: Do not hardcode return values Sachin Kamat
2014-02-19 16:27 ` Mark Brown
2014-02-18 10:41 ` [PATCH 07/15] regulator: lp3971: Do not hardcode return value Sachin Kamat
2014-02-19 16:28 ` Mark Brown
2014-02-18 10:41 ` [PATCH 08/15] regulator: fan53555: Do not hardcode return values Sachin Kamat
2014-02-19 16:30 ` Mark Brown
2014-02-18 10:41 ` [PATCH 09/15] regulator: da9063: " Sachin Kamat
2014-02-19 16:31 ` Mark Brown
2014-02-18 10:41 ` [PATCH 10/15] regulator: da9055: Do not hardcode return value Sachin Kamat
2014-02-19 16:34 ` Mark Brown
2014-02-18 10:41 ` [PATCH 11/15] regulator: 88pm800: Remove redundant error message Sachin Kamat
2014-02-19 16:34 ` Mark Brown
2014-02-18 10:41 ` [PATCH 12/15] regulator: act8865: " Sachin Kamat
2014-02-19 16:35 ` Mark Brown
2014-02-18 10:41 ` [PATCH 13/15] regulator: arizona-ldo1: " Sachin Kamat
2014-02-19 16:38 ` Mark Brown
2014-02-18 10:41 ` [PATCH 14/15] regulator: arizona-micsupp: " Sachin Kamat
2014-02-19 16:38 ` Mark Brown [this message]
2014-02-18 10:41 ` [PATCH 15/15] regulator: as3711: " Sachin Kamat
2014-02-19 4:25 ` [PATCH 01/15] regulator: wm8350: Do not hardcode return value 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=20140219163828.GX2669@sirena.org.uk \
--to=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sachin.kamat@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.