All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>,
	cw00.choi@samsung.com, linux-kernel@vger.kernel.org,
	alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com,
	myungjoo.ham@samsung.com, linux-input@vger.kernel.org
Subject: Re: [PATCH V2 5/5] Input: arizona-haptics - Use SoC component pin control functions
Date: Wed, 30 Nov 2016 10:30:06 -0800	[thread overview]
Message-ID: <20161130183006.GC31934@dtor-ws> (raw)
In-Reply-To: <20161130172823.ihmk6jaw2khtyzek@sirena.org.uk>

On Wed, Nov 30, 2016 at 05:28:23PM +0000, Mark Brown wrote:
> On Tue, Nov 29, 2016 at 05:41:35PM -0800, Dmitry Torokhov wrote:
> > On Tue, Nov 29, 2016 at 03:44:42PM +0000, Richard Fitzgerald wrote:
> 
> > > Switch to using the snd_soc_component_x_pin equivalent functions that
> > > take a specified SoC component and automatically add the name prefix to
> > > the provided pin name.
> 
> > Acked-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> 
> Do you want me to apply this or do you want to apply it in your tree?

Please apply though your tree, I should not have anything conflicting in
mine, and grouped on the same branch the changes make more sense.

Thanks!

-- 
Dmitry

      reply	other threads:[~2016-11-30 18:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-29 15:44 [PATCH V2 0/5] ASoC/arizona: Ensure pin searches use widget name prefix Richard Fitzgerald
2016-11-29 15:44 ` Richard Fitzgerald
2016-11-29 15:44 ` [PATCH V2 1/5] ASoC: core: Add component pin control functions Richard Fitzgerald
2016-11-29 15:44   ` Richard Fitzgerald
2016-11-30 17:16   ` Applied "ASoC: core: Add component pin control functions" to the asoc tree Mark Brown
2016-11-30 17:16     ` Mark Brown
2016-11-29 15:44 ` [PATCH V2 2/5] ASoC: arizona: Use component pin control functions Richard Fitzgerald
2016-11-29 15:44   ` Richard Fitzgerald
2016-11-30 18:07   ` Applied "ASoC: arizona: Use component pin control functions" to the asoc tree Mark Brown
2016-11-30 18:07     ` Mark Brown
2016-11-29 15:44 ` [PATCH V2 3/5] regulator: arizona-micsupp: Use SoC component pin control functions Richard Fitzgerald
2016-11-29 15:44   ` Richard Fitzgerald
2016-11-29 15:44 ` [PATCH V2 4/5] extcon: arizona: " Richard Fitzgerald
2016-11-29 15:44   ` Richard Fitzgerald
2016-11-30  0:19   ` Chanwoo Choi
2016-11-30 17:27     ` Mark Brown
2016-12-01  1:56       ` Chanwoo Choi
2016-11-29 15:44 ` [PATCH V2 5/5] Input: arizona-haptics - " Richard Fitzgerald
2016-11-29 15:44   ` Richard Fitzgerald
2016-11-30  1:41   ` Dmitry Torokhov
2016-11-30 17:28     ` Mark Brown
2016-11-30 18:30       ` Dmitry Torokhov [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=20161130183006.GC31934@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=cw00.choi@samsung.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    --cc=patches@opensource.wolfsonmicro.com \
    --cc=rf@opensource.wolfsonmicro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.