All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@sirena.org.uk>
To: chri <chripell@gmail.com>
Cc: zdevai@gmail.com, alsa-devel@alsa-project.org,
	linux-arm-kernel@lists.arm.linux.org.uk,
	Ben Dooks <ben-linux@fluff.org>
Subject: Re: [PATCH] ALSA SOC driver for s3c24xx with uda1341
Date: Tue, 11 Nov 2008 15:52:15 +0000	[thread overview]
Message-ID: <20081111155215.GF7019@sirena.org.uk> (raw)
In-Reply-To: <cabda6420811110614k73d97d4are33f5471044e86a4@mail.gmail.com>

On Tue, Nov 11, 2008 at 03:14:04PM +0100, chri wrote:
> On Mon, Nov 10, 2008 at 11:09 PM, Ben Dooks <ben-linux@fluff.org> wrote:

> > find somewhere for these to live that can be included without
> > resorting to knowing the directory layout.

> ack, I'll try include/sound

If they (you cut context so I'm not sure what exactly they are) are only
referenced within ASoC leave them in sound/soc/codecs which is idiomatic
for that.  Otherwise either include/sound or arch/arm depending on if
it's ARM/Samsung specific or not.

-- 
"You grabbed my hand and we fell into it, like a daydream - or a fever."

      reply	other threads:[~2008-11-11 15:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-08  7:43 [PATCH] ALSA SOC driver for s3c24xx with uda1341 Christian Pellegrin
2008-11-10 13:34 ` Mark Brown
2008-11-10 17:58   ` Kristoffer Ericson
2008-11-10 19:08     ` chri
2008-11-10 20:22       ` Kristoffer Ericson
2008-11-10 22:10         ` [alsa-devel] " Ben Dooks
2008-11-11 14:15           ` chri
2008-11-11 18:55             ` Kristoffer Ericson
2008-11-11 20:53             ` Kristoffer Ericson
2008-11-12  6:31               ` christian pellegrin
2008-11-10 19:04   ` chri
2008-11-11 10:39     ` Mark Brown
2008-11-11 14:16       ` chri
2008-11-10 19:22   ` [alsa-devel] " Russell King - ARM Linux
2008-11-11 14:00     ` chri
2008-11-10 22:09 ` Ben Dooks
2008-11-11 14:14   ` chri
2008-11-11 15:52     ` 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=20081111155215.GF7019@sirena.org.uk \
    --to=broonie@sirena.org.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=ben-linux@fluff.org \
    --cc=chripell@gmail.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=zdevai@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.