All of lore.kernel.org
 help / color / mirror / Atom feed
From: Micka <mickamusset@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, lgirdwood@gmail.com,
	anish kumar <yesanishhere@gmail.com>
Subject: Re: [PATCH] ASoC: Add max98371 codec driver
Date: Thu, 24 Mar 2016 11:19:13 +0000	[thread overview]
Message-ID: <CAF+MRtnV0FhmVjuvRua-jWjJQn1Q_Ynn=7x+VpGhPPuXp5=cFQ@mail.gmail.com> (raw)
In-Reply-To: <20160324110512.GV2566@sirena.org.uk>

Mark, the subject of this mail is asoc: add max98371 codex driver.

My questions concerns this patch/codec :

Where I can find your patch ? Will it work under the kernel 4.1 ? And how
do you make it work with the dts file ?

Micka,

Le jeu. 24 mars 2016 à 12:05, Mark Brown <broonie@kernel.org> a écrit :

> On Thu, Mar 24, 2016 at 10:49:59AM +0000, Micka wrote:
> > Hi Mark,
>
> Please don't top post, reply in line with needed context.  This allows
> readers to readily follow the flow of conversation and understand what
> you are talking about and also helps ensure that everything in the
> discussion is being addressed.
>
> > Where I can find your patch ? Will it work under the kernel 4.1 ? And how
> > do you make it work with the dts file ?
>
> I have no idea what you're talking about here, sorry.
>
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2016-03-24 11:19 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-21  1:59 [PATCH] ASoC: Add max98371 codec driver anish kumar
2016-03-21 14:56 ` Mark Brown
2016-03-21 15:29   ` Micka
2016-03-21 15:56     ` Mark Brown
2016-03-21 16:41       ` Micka
2016-03-21 17:05         ` Mark Brown
2016-03-23 12:45           ` Micka
2016-03-23 16:23             ` Amish Kumar
2016-03-24 10:49   ` Micka
2016-03-24 11:05     ` Mark Brown
2016-03-24 11:19       ` Micka [this message]
2016-03-24 11:21         ` Mark Brown
2016-03-22  6:53 anish kumar
2016-03-28 19:13 ` Mark Brown
2016-04-07 19:34   ` anish kumar
2016-04-08  3:09 ` Lars-Peter Clausen
2016-04-08 20:04   ` anish kumar
2016-04-10 18:04   ` Mark Brown
2016-04-13 20:20 anish kumar
2016-04-18 16:47 ` Mark Brown
2016-04-18 20:20   ` anish kumar
2016-04-19  9:46     ` Mark Brown
2016-04-20 18:14       ` anish kumar
2016-04-22 15:31         ` Mark Brown
2016-04-26 18:16           ` anish kumar
2016-04-27 16:42             ` Mark Brown
2016-04-27 22:39 anish kumar

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='CAF+MRtnV0FhmVjuvRua-jWjJQn1Q_Ynn=7x+VpGhPPuXp5=cFQ@mail.gmail.com' \
    --to=mickamusset@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=yesanishhere@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 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.