public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Greg KH <gregkh@suse.de>
Cc: Felipe Balbi <balbi@ti.com>,
	linux-kernel@vger.kernel.org, Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] ASoC: Update cx20442 for TTY API change
Date: Wed, 11 May 2011 18:11:31 +0200	[thread overview]
Message-ID: <20110511161131.GB31593@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110511155535.GB20920@suse.de>

On Wed, May 11, 2011 at 08:55:35AM -0700, Greg KH wrote:

> Do you want me to take this through the tty tree, or do you want to take
> it through the SOC sound tree?  If you want to do it, that's fine with
> me, whatever is easier for you.

Please apply it to your tree - the problem that this fixes was
introduced by a patch in your tree in -next so it'd introduce breakage
in my tree if I'd applied it anyway.

  reply	other threads:[~2011-05-11 16:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-11 14:05 [PATCH] ASoC: Update cx20442 for TTY API change Mark Brown
2011-05-11 15:55 ` Greg KH
2011-05-11 16:11   ` Mark Brown [this message]
2011-05-11 16:27     ` Greg KH

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=20110511161131.GB31593@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=balbi@ti.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@ti.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