From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Timur Tabi <timur@freescale.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH][ASoC V2] Make Freescale MPC8610 drivers more dynamic
Date: Mon, 2 Jun 2008 15:42:37 +0100 [thread overview]
Message-ID: <20080602144235.GA29975@sirena.org.uk> (raw)
In-Reply-To: <48440123.5070508@freescale.com>
On Mon, Jun 02, 2008 at 09:18:11AM -0500, Timur Tabi wrote:
> 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.
[As discussed on IRC, summarising for the list archive.]
For the user-visible menu that's sensible enough - the issue is more
with the fact that you've now got the CPU side objects encoded into each
individual board entry rather than having the board build machinery say
"I need the SSI controller" or similar.
> > 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.
It's not the submitting individual patches that I was meaning, it's the
fact that individual patches cover multiple issues.
prev parent reply other threads:[~2008-06-02 14:42 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
2008-06-02 14:42 ` 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=20080602144235.GA29975@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=timur@freescale.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.