mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Sachin Kamat <sachin.kamat@linaro.org>
Cc: linux-kernel@vger.kernel.org, lgirdwood@gmail.com,
	Venu Byravarasu <vbyravarasu@nvidia.com>
Subject: Re: [PATCH 15/23] regulator: tps65090: Remove redundant error message
Date: Thu, 20 Feb 2014 20:54:10 +0900	[thread overview]
Message-ID: <20140220115410.GI2669@sirena.org.uk> (raw)
In-Reply-To: <1392886403-10640-15-git-send-email-sachin.kamat@linaro.org>

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

On Thu, Feb 20, 2014 at 02:23:15PM +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 --]

  reply	other threads:[~2014-02-20 11:54 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20  8:53 [PATCH 01/23] regulator: da9063: " Sachin Kamat
2014-02-20  8:53 ` [PATCH 02/23] regulator: da9210: " Sachin Kamat
2014-02-20 10:59   ` Mark Brown
2014-02-20  8:53 ` [PATCH 03/23] regulator: dbx500: " Sachin Kamat
2014-02-20 11:20   ` Mark Brown
2014-02-20  8:53 ` [PATCH 04/23] regulator: fan53555: " Sachin Kamat
2014-02-20 11:21   ` Mark Brown
2014-02-20  8:53 ` [PATCH 05/23] regulator: fixed: " Sachin Kamat
2014-02-20 11:23   ` Mark Brown
2014-02-20  8:53 ` [PATCH 06/23] regulator: max77686: " Sachin Kamat
2014-02-20 11:22   ` Mark Brown
2014-02-20  8:53 ` [PATCH 07/23] regulator: max8907: " Sachin Kamat
2014-02-20 11:23   ` Mark Brown
2014-02-20  8:53 ` [PATCH 08/23] regulator: max8952: " Sachin Kamat
2014-02-20 11:24   ` Mark Brown
2014-02-20  8:53 ` [PATCH 09/23] regulator: max8997: " Sachin Kamat
2014-02-20 11:25   ` Mark Brown
2014-02-20  8:53 ` [PATCH 10/23] regulator: rc5t583: " Sachin Kamat
2014-02-20 11:26   ` Mark Brown
2014-02-20  8:53 ` [PATCH 11/23] regulator: s5m8767: " Sachin Kamat
2014-02-20 11:49   ` Mark Brown
2014-02-20  8:53 ` [PATCH 12/23] regulator: tps51632: " Sachin Kamat
2014-02-20 11:50   ` Mark Brown
2014-02-20  8:53 ` [PATCH 13/23] regulator: tps62360: " Sachin Kamat
2014-02-20 11:51   ` Mark Brown
2014-02-20  8:53 ` [PATCH 14/23] regulator: tps6507x: " Sachin Kamat
2014-02-20 11:52   ` Mark Brown
2014-02-20  8:53 ` [PATCH 15/23] regulator: tps65090: " Sachin Kamat
2014-02-20 11:54   ` Mark Brown [this message]
2014-02-20  8:53 ` [PATCH 16/23] regulator: tps6524x: " Sachin Kamat
2014-02-20 11:55   ` Mark Brown
2014-02-20  8:53 ` [PATCH 17/23] regulator: tps6586x: " Sachin Kamat
2014-02-20 11:57   ` Mark Brown
2014-02-20  8:53 ` [PATCH 18/23] regulator: tps65910: " Sachin Kamat
2014-02-20 12:01   ` Mark Brown
2014-02-20  8:53 ` [PATCH 19/23] regulator: tps80031: " Sachin Kamat
2014-02-20 12:02   ` Mark Brown
2014-02-20  8:53 ` [PATCH 20/23] regulator: wm831x-dcdc: " Sachin Kamat
2014-02-20 12:03   ` Mark Brown
2014-02-20  8:53 ` [PATCH 21/23] regulator: wm831x-isink: " Sachin Kamat
2014-02-20 12:03   ` Mark Brown
2014-02-20  8:53 ` [PATCH 22/23] regulator: wm831x-ldo: " Sachin Kamat
2014-02-20 12:04   ` Mark Brown
2014-02-20  8:53 ` [PATCH 23/23] regulator: wm8994: " Sachin Kamat
2014-02-20 10:57 ` [PATCH 01/23] regulator: da9063: " 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=20140220115410.GI2669@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sachin.kamat@linaro.org \
    --cc=vbyravarasu@nvidia.com \
    /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

all inboxes | Powered by JetHome®