From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Samuel Ortiz <sameo@linux.intel.com>, Liam Girdwood <lrg@ti.com>,
alsa-devel@alsa-project.org, linux-input@vger.kernel.org,
patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH 2/4] Input - arizona-haptics: Add driver haptics module on Arizona CODECs
Date: Tue, 27 Nov 2012 20:00:02 +0000 [thread overview]
Message-ID: <20121127200001.GJ4468@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20121127195644.GA29727@core.coreip.homeip.net>
[-- Attachment #1: Type: text/plain, Size: 369 bytes --]
On Tue, Nov 27, 2012 at 11:56:44AM -0800, Dmitry Torokhov wrote:
> How do you want to merge it? My tree or some other?
I'm not terribly fussed but I guess as it's a new driver for the input
tree merging via ASoC will minimise the potential for conflicts? But
we're near the merge window and I'm not sure that's likely anyway so if
you want to apply it to your tree.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-11-27 20:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 12:40 [PATCH 1/4] mfd: arizona: Allow the CODEC DAPM context to be accessed elsewhere Mark Brown
2012-11-27 12:40 ` [PATCH 2/4] Input - arizona-haptics: Add driver haptics module on Arizona CODECs Mark Brown
2012-11-27 19:56 ` Dmitry Torokhov
2012-11-27 20:00 ` Mark Brown [this message]
2012-11-28 7:11 ` Dmitry Torokhov
2012-11-28 13:49 ` Mark Brown
2012-11-27 12:40 ` [PATCH 3/4] ASoC: wm5102: Implement haptics support Mark Brown
2012-11-27 12:40 ` [PATCH 4/4] ASoC: wm5110: " Mark Brown
2012-11-30 10:09 ` [PATCH 1/4] mfd: arizona: Allow the CODEC DAPM context to be accessed elsewhere Samuel Ortiz
-- strict thread matches above, loose matches on Subject: below --
2012-11-27 10:33 Mark Brown
2012-11-27 10:33 ` [PATCH 2/4] Input - arizona-haptics: Add driver haptics module on Arizona CODECs Mark Brown
2012-11-27 7:08 [PATCH 1/4] mfd: arizona: Allow the CODEC DAPM context to be accessed elsewhere Mark Brown
2012-11-27 7:08 ` [PATCH 2/4] Input - arizona-haptics: Add driver haptics module on Arizona CODECs Mark Brown
2012-11-27 9:08 ` Dmitry Torokhov
2012-11-27 9:36 ` Mark Brown
2012-11-26 21:39 [PATCH 1/4] mfd: arizona: Allow the CODEC DAPM context to be accessed elsewhere Mark Brown
2012-11-26 21:39 ` [PATCH 2/4] Input - arizona-haptics: Add driver haptics module on Arizona CODECs Mark Brown
2012-11-26 23:11 ` Dmitry Torokhov
2012-11-27 6:32 ` Mark Brown
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=20121127200001.GJ4468@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=lrg@ti.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=sameo@linux.intel.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).