mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King <rmk+alsa@arm.linux.org.uk>
To: Valdis.Kletnieks@vt.edu
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	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: Fri, 16 Sep 2011 21:03:53 +0100	[thread overview]
Message-ID: <20110916200353.GB18566@flint.arm.linux.org.uk> (raw)
In-Reply-To: <56969.1316192529@turing-police.cc.vt.edu>

On Fri, Sep 16, 2011 at 01:02:09PM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Thu, 15 Sep 2011 13:53:04 +0200, Lars-Peter Clausen said:
> > 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?
> 
> Then those platforms won't notice if their now-unused entries evaporate out of
> the platform file, right?

Just to be clear: DT SoCs should be described with DT_MACHINE_START()
rather than MACHINE_START().  DT_MACHINE_START() sets the machine ID
to ~0, so using machine_is_xxx() is _intentionally_ useless in that
case - the point of DT is that DT itself is used to describe the
platform differences, not code based on machine type numbers.

Essentially, as DT progresses, the machine IDs should eventually
disappear and become completely redundant.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:

  reply	other threads:[~2011-09-16 20:04 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
2011-09-16 17:02             ` Valdis.Kletnieks
2011-09-16 20:03               ` Russell King [this message]
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=20110916200353.GB18566@flint.arm.linux.org.uk \
    --to=rmk+alsa@arm.linux.org.uk \
    --cc=Valdis.Kletnieks@vt.edu \
    --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