public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: error: implicit declaration of function 'machine_is_ventana'
Date: Tue, 23 Aug 2011 01:01:35 +0100	[thread overview]
Message-ID: <20110823000135.GD3895@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF04B24A377F@HQMAIL01.nvidia.com>

On Mon, Aug 22, 2011 at 04:49:06PM -0700, Stephen Warren wrote:
> Russell King wrote at Monday, August 22, 2011 5:40 PM:
> > On Mon, Aug 22, 2011 at 04:11:50PM -0700, Stephen Warren wrote:
> > > Russell,
> > >
> > > Commit 46dcfc806a9f6834e6007449eac175f781058c49 "ARM: Update mach-types"
> > > removed the entry for Ventana (2927). In turn, this broke compilation of
> > > sound/soc/tegra/tegra_wm8903.c, since that calls machine_is_ventana().
> > > It looks like the machine is still registered at
> > > http://www.arm.linux.org.uk/developer/machines/. Can you explain what the
> > > removal policy is for arch/arm/tools/mach-types?
> > 
> > The policy has always been that the machine_is_xxx() matches the other
> > constants.  Rather than having to edit those out by hand, the script
> > now does this for me automatically.
> 
> I'm very sorry for being so dense, but what "other constants" must the
> entry match?
> 
> For reference, here's the entry I'm referring to:
> 
> -ventana                        MACH_VENTANA            VENTANA                 2927
> 
> ... which seems to use the name "ventana" consistently, if that's what
> you mean.
> 
> ...
> > Please submit a patch to fix your use in the kernel, including updating
> > the mach-types file to conform.  I'll then fix the machine registry by
> > hand.
> 
> I will happily submit the patch, once I understand exactly what needs to
> change. Thanks for any enlightenment!

Ah, sorry, I thought you were talking about a platform which was merged
into mainline.  This platform is not present in mainline, so accordingly
it isn't marked as such in the machine database.

Any entry not marked as being present in mainline will be removed after
12 months after it was last touched - which apparantly was 18th June
2010.

So, the questions are:
1. why do we have driver code merged for a platform which shows no sign
   of being merged.
2. why do we have drivers depending on their platform anyway.

  reply	other threads:[~2011-08-23  0:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-22 23:11 error: implicit declaration of function 'machine_is_ventana' Stephen Warren
2011-08-22 23:40 ` Russell King - ARM Linux
2011-08-22 23:49   ` Stephen Warren
2011-08-23  0:01     ` Russell King - ARM Linux [this message]
2011-08-23  0:11       ` Stephen Warren
2011-08-23 14:21         ` Russell King - ARM Linux

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=20110823000135.GD3895@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox