From: Mark Brown <broonie@kernel.org>
To: Axel Lin <axel.lin@ingics.com>
Cc: Bjorn Andersson <bjorn.andersson@sonymobile.com>,
Liam Girdwood <lgirdwood@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] regulator: qcom_rpm: Don't explicitly initialise the first field of config
Date: Fri, 26 Sep 2014 09:28:46 +0100 [thread overview]
Message-ID: <20140926082846.GC27755@sirena.org.uk> (raw)
In-Reply-To: <1411551925.24415.0.camel@phoenix>
[-- Attachment #1: Type: text/plain, Size: 172 bytes --]
On Wed, Sep 24, 2014 at 05:45:25PM +0800, Axel Lin wrote:
> Doing so generates a warning as the first field is a pointer but we use
> 0 to initialize it.
Applied, thanks.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2014-09-26 8:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 9:45 [PATCH] regulator: qcom_rpm: Don't explicitly initialise the first field of config Axel Lin
2014-09-26 8:28 ` 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=20140926082846.GC27755@sirena.org.uk \
--to=broonie@kernel.org \
--cc=axel.lin@ingics.com \
--cc=bjorn.andersson@sonymobile.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