From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: linux-input@vger.kernel.org, alsa-devel@alsa-project.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: [PATCH 1/2] Add Palm support to Mainstone accelerated touch
Date: Fri, 17 Jul 2009 12:15:37 +0100 [thread overview]
Message-ID: <20090717111537.GA19871@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <200907171310.14935.marek.vasut@gmail.com>
On Fri, Jul 17, 2009 at 01:10:14PM +0200, Marek Vasut wrote:
> Ok, sending to linux-input, CC Mark, Dmitry, alsa-devel. Im sending the patch
> as an attachment to prevent breakage (sorry, I'll investigate what's wrong
> with KMail or my settings).
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
prev parent reply other threads:[~2009-07-17 11:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200907171000.24408.marek.vasut@gmail.com>
[not found] ` <20090717102217.GE3439@rakim.wolfsonmicro.main>
2009-07-17 11:10 ` [PATCH 1/2] Add Palm support to Mainstone accelerated touch Marek Vasut
2009-07-17 11:15 ` 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=20090717111537.GA19871@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=marek.vasut@gmail.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).