From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Rajendra Nayak <rnayak@ti.com>
Cc: sfr@canb.auug.org.au, lrg@slimlogic.co.uk,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
heiko@sntech.de
Subject: Re: [PATCH] regulator: Fix compile break due to missing arguments to regulator_register
Date: Thu, 24 Nov 2011 10:51:54 +0000 [thread overview]
Message-ID: <20111124105153.GE8470@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1322119637-32634-1-git-send-email-rnayak@ti.com>
On Thu, Nov 24, 2011 at 12:57:17PM +0530, Rajendra Nayak wrote:
> The commit 2c043bcbf287 ("regulator: pass additional of_node to
> regulator_register()") caused a compile break because it missed
> updating the regulator_register() call in gpio-regulator.c with
> the additional parameter (NULL).
Applied, thanks. Please do submit patches against -next.
prev parent reply other threads:[~2011-11-24 10:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 7:27 [PATCH] regulator: Fix compile break due to missing arguments to regulator_register Rajendra Nayak
2011-11-24 7:27 ` Rajendra Nayak
2011-11-24 10:51 ` Mark Brown [this message]
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=20111124105153.GE8470@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=rnayak@ti.com \
--cc=sfr@canb.auug.org.au \
/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.