From: Mark Brown <broonie@kernel.org>
To: Saurabh Singh <saurabh1.s@samsung.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"grant.likely@linaro.org" <grant.likely@linaro.org>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"celinux-dev@tree.celinuxforum.org"
<celinux-dev@tree.celinuxforum.org>,
SREEVATSA D B <srevatsa@samsung.com>,
Praveen BP <bp.praveen@samsung.com>
Subject: Re: [PATCH] Parse missing regulator constraints from device tree blob
Date: Thu, 16 Jan 2014 14:07:12 +0000 [thread overview]
Message-ID: <20140116140712.GE17314@sirena.org.uk> (raw)
In-Reply-To: <27224826.584141389879802275.JavaMail.weblogic@epml20>
[-- Attachment #1: Type: text/plain, Size: 614 bytes --]
On Thu, Jan 16, 2014 at 01:43:23PM +0000, Saurabh Singh wrote:
> Hi Mark,
>
> New patch incorporating your suggestions is given below.
>
> > * None of these properties are documented. Documentation is required so
> > that the contract is defined. That allows people to learn how to use
> > the properties, and makes clear what we can and cannot change
> > kernel-side.
> Done. The documentation is in the patch below.
Please send patches using the process in SubmittingPatches, the
formatting of the submission is very important for tools like git am
which people use to work with patches.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-01-16 14:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 13:43 Saurabh Singh
2014-01-16 14:07 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-17 15:11 Saurabh Singh
2014-01-17 15:04 Saurabh Singh
2014-01-16 6:34 Saurabh Singh
2014-01-16 10:28 ` Mark Rutland
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=20140116140712.GE17314@sirena.org.uk \
--to=broonie@kernel.org \
--cc=bp.praveen@samsung.com \
--cc=celinux-dev@tree.celinuxforum.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rob.herring@calxeda.com \
--cc=saurabh1.s@samsung.com \
--cc=srevatsa@samsung.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®