From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Joel A Fernandes <agnel.joel@gmail.com>
Cc: "Hebbar, Gururaja" <gururaja.hebbar@ti.com>,
"Porter, Matt" <mporter@ti.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>,
Tony Lindgren <tony@atomide.com>,
"Hiremath, Vaibhav" <hvaibhav@ti.com>,
Linux OMAP List <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] ARM: OMAP2+: AM33XX: clock data: fix mcasp entries
Date: Mon, 5 Nov 2012 09:13:18 +0100 [thread overview]
Message-ID: <20121105081317.GC28886@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAD=GYpYuyfGuEgAWJyE2nkKx4GEsm=eDYAhV966sWVLbEPaqYQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 360 bytes --]
On Sat, Nov 03, 2012 at 02:32:59PM -0500, Joel A Fernandes wrote:
> beaglebone_defconfig: Add dummy regulator to init tlv320aic3x
> https://github.com/joelagnel/linux-kernel/commit/db5672dfe548d82625cf40ed688d05ba7cee5c93
This should never be done in production, you should ensure that the
appropriate supplies are provided by the board file or device tree.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-11-05 8:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 14:30 [PATCH] ARM: OMAP2+: AM33XX: clock data: fix mcasp entries Matt Porter
2012-10-10 14:33 ` Hiremath, Vaibhav
2012-10-10 14:36 ` Matt Porter
2012-10-29 15:45 ` Hebbar, Gururaja
2012-10-30 0:33 ` Joel A Fernandes
2012-10-30 0:35 ` Joel A Fernandes
2012-10-30 20:28 ` Joel A Fernandes
2012-10-31 5:39 ` Hebbar, Gururaja
2012-11-03 19:32 ` Joel A Fernandes
2012-11-05 8:13 ` Mark Brown [this message]
2012-11-05 16:52 ` Joel A Fernandes
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=20121105081317.GC28886@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=agnel.joel@gmail.com \
--cc=gururaja.hebbar@ti.com \
--cc=hvaibhav@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mporter@ti.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).