From: "Péter Ujfalusi" <peter.ujfalusi@ti.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Tony Lindgren <tony@atomide.com>,
Brown <broonie@opensource.wolfsonmicro.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mark@alsa-project.org,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"Lopez Cruz, Misael" <misael.lopez@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Girdwood, Liam" <lrg@ti.com>
Subject: Re: [PATCH v3 06/12] MFD: twl4030-codec -> twl4030-audio: Rename the driver
Date: Fri, 10 Jun 2011 07:52:51 +0300 [thread overview]
Message-ID: <201106100752.51718.peter.ujfalusi@ti.com> (raw)
In-Reply-To: <201106092137.28678.arnd@arndb.de>
On Thursday 09 June 2011 22:37:28 Arnd Bergmann wrote:
> Better use the -M flag to git-format-patch when moving files, to make it
> obvious what has or has not changed, and to reduce the size of the email.
I tend to forgot the -M flag, thanks.
> Also, shouldn't this file go into the sound/soc/ directory? It seems that
> this is really the device driver, not part of the multi-function layer.
This driver is the MFD core part for the audio block within the twl4030 series
pmic.
We have the slave drivers under sound/soc/codecs/twl4030.c and
drivers/input/misc/twl4030-vibra.c.
The audio block has codec, and vibra functionality, and we need to have this
driver to properly manage this block within twl.
--
Péter
next prev parent reply other threads:[~2011-06-10 4:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 13:30 [PATCH v3 00/12] MFD/ASoC/Input: TWL4030/TWL60X0 changes Peter Ujfalusi
2011-06-09 13:30 ` [PATCH v3 01/12] OMAP: New twl-common for common TWL configuration Peter Ujfalusi
2011-06-09 13:30 ` [PATCH v3 02/12] OMAP4: Move common twl6030 configuration to twl-common Peter Ujfalusi
2011-06-09 13:30 ` [PATCH v3 03/12] OMAP3: Move common twl " Peter Ujfalusi
2011-06-09 13:30 ` [PATCH v3 04/12] OMAP3: Move common regulator " Peter Ujfalusi
2011-06-09 13:30 ` [PATCH v3 05/12] MFD: twl4030-codec: Rename internals from codec to audio Peter Ujfalusi
2011-06-09 13:30 ` [PATCH v3 06/12] MFD: twl4030-codec -> twl4030-audio: Rename the driver Peter Ujfalusi
2011-06-09 19:37 ` Arnd Bergmann
2011-06-10 4:52 ` Péter Ujfalusi [this message]
2011-06-09 13:30 ` [PATCH v3 07/12] MFD: twl4030-audio: Rename platform data Peter Ujfalusi
2011-06-09 13:30 ` [PATCH v3 08/12] mfd: twl6040: Add initial support Peter Ujfalusi
2011-06-09 13:30 ` [PATCH v3 09/12] ASoC: twl6040: Convert into TWL6040 MFD child Peter Ujfalusi
2011-06-09 13:30 ` [PATCH v3 10/12] MFD: twl6040: Change platform data for soc codec driver Peter Ujfalusi
2011-06-09 13:30 ` [PATCH v3 11/12] input: Add initial support for TWL6040 vibrator Peter Ujfalusi
2011-06-09 13:30 ` [PATCH v3 12/12] OMAP4: SDP4430: Add twl6040 vibrator platform support Peter Ujfalusi
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=201106100752.51718.peter.ujfalusi@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=Mark@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
--cc=arnd@arndb.de \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=misael.lopez@ti.com \
--cc=sameo@linux.intel.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