From: Russell King <rmk+alsa@arm.linux.org.uk>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Axel Lin <axel.lin@gmail.com>, Harald Welte <laforge@openezx.org>,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
Liam Girdwood <lrg@ti.com>
Subject: Re: [linux-next] ASoC: sound/soc/samsung/neo1973_wm8753.c build failure
Date: Thu, 15 Sep 2011 13:06:27 +0100 [thread overview]
Message-ID: <20110915120627.GB32615@flint.arm.linux.org.uk> (raw)
In-Reply-To: <4E71E720.7040008@metafoo.de>
On Thu, Sep 15, 2011 at 01:53:04PM +0200, Lars-Peter Clausen wrote:
> On 09/15/2011 01:00 PM, Russell King wrote:
> > [...]
> > We now have a sane policy: entries which aren't fully up to date are
> > automatically dropped. Entries for which there is no platform support
> > file merged within 12 months of the entries last edit are dropped also
> > automatically dropped.
>
> Partly unrelated, but what about these platforms which can be fully described
> with DT and don't need a platform file?
The theory is with DT is that machine_is_xxx() is no longer required,
because they're fully described by DT. Such a kernel should not care
whether it's running on board XYZ or ABC because the differences are
wrapped up in the DT description of it.
Moreover, DT boards do not have machine IDs - their machine ID is "~0"
which will be universal for all DT using platforms. So machine_is_xxx()
really has no meaning at all when using DT. Basically, DT makes machine
IDs obsolete.
> The code for GTA01 is out there and could be merged into mainline, but
> I think it would be dead code since there doesn't seem to be really
> any interest in the device anymore.
>
> So just get rid of the gta01 portions of the neo1973_wm8753 driver.
> If GTA01 support ever gets merged we can still revert the removal.
Agreed.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2011-09-15 12:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 9:18 Axel Lin
2011-09-14 19:19 ` Russell King
2011-09-14 23:28 ` Mark Brown
2011-09-14 23:38 ` Russell King
2011-09-15 9:46 ` Mark Brown
2011-09-15 11:00 ` Russell King
2011-09-15 11:53 ` Lars-Peter Clausen
2011-09-15 12:06 ` Russell King [this message]
2011-09-16 17:02 ` Valdis.Kletnieks
2011-09-16 20:03 ` Russell King
2011-09-15 13:31 ` Mark Brown
2011-09-15 19:16 ` Russell King
2011-09-15 22:39 ` Mark Brown
2011-09-15 7:20 ` Harald Welte
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=20110915120627.GB32615@flint.arm.linux.org.uk \
--to=rmk+alsa@arm.linux.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=axel.lin@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=laforge@openezx.org \
--cc=lars@metafoo.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
Powered by JetHome