All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: alsa-devel@alsa-project.org
Subject: Re: [PATCH][ASoC V2] Make Freescale MPC8610 drivers more dynamic
Date: Mon, 02 Jun 2008 09:18:11 -0500	[thread overview]
Message-ID: <48440123.5070508@freescale.com> (raw)
In-Reply-To: <20080602110101.GE9031@rakim.wolfsonmicro.main>

Mark Brown wrote:

> This change means that if someone builds another board with the same CPU
> on it then they'll have to add all the objects for the core CPU support
> to the Makefile entry for their board.

They'll need to update Kconfig and the Makefile anyway, so I decided to cut out
the "middle man" -- the SOC.

>  There should at least be a
> separate Kconfig thing, even if it's not user visible.  I've committed a
> patch backing this bit out for now.

Grrr...

>> +#define DEBUG
>> +
> 
> This probably shouldn't be on by default?

For now, I want it on.

> In general, it'd be a bit easier to review the changes you're making if
> you were able to submit individual changes in separate patches, 

Yes, that would be nice :-)

> though I
> appreciate that at the minute you're making a lot of changes that go
> over large portions of the code and can't be easily separated out so I
> wouldn't worry about it too much.

Normally, I would submit everything as one final patch, but I hate hanging on to
uncommitted code for too long.

-- 
Timur Tabi
Linux kernel developer at Freescale

  reply	other threads:[~2008-06-02 14:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-30 22:41 [PATCH][ASoC V2] Make Freescale MPC8610 drivers more dynamic Timur Tabi
2008-06-02 11:01 ` Mark Brown
2008-06-02 14:18   ` Timur Tabi [this message]
2008-06-02 14:42     ` Mark Brown

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=48440123.5070508@freescale.com \
    --to=timur@freescale.com \
    --cc=alsa-devel@alsa-project.org \
    /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.