From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: Error for machine_is_m28evk
Date: Wed, 16 Nov 2011 19:48:39 +0100 [thread overview]
Message-ID: <20111116184839.GS30612@pengutronix.de> (raw)
In-Reply-To: <20111116135857.GA14656@S2100-06.ap.freescale.net>
Hello,
On Wed, Nov 16, 2011 at 09:58:58PM +0800, Shawn Guo wrote:
> On Wed, Nov 16, 2011 at 08:42:58AM +0000, Russell King - ARM Linux wrote:
> > On Wed, Nov 16, 2011 at 01:59:41PM +0800, Shawn Guo wrote:
> > > Hi Russell,
> > >
> > > On Tue, Nov 08, 2011 at 08:53:47PM +0800, Shawn Guo wrote:
> > > > On Tue, Nov 08, 2011 at 08:53:50AM +0000, Russell King - ARM Linux wrote:
> > > > [...]
> > > > >
> > > > > Maybe the answer is to just update the file anyway, and ignore peoples
> > > > > complaints that their entries aren't present until they come to their
> > > > > senses and start COMMUNICATING properly about issues they have with
> > > > > their fscked up entry in the database.
> > > > >
> > > > So I assume that you will update mach-types for -rc2. Otherwise,
> > > > please let me know, and I will send a patch to disable m28evk build
> > > > from mxs_defconfig for -rc2.
> > > >
> > > May I know your plan of mach-types updating? The -rc2 is out with no
> > > update on mach-types.
> >
> > There is *NO* bloody way I'm updating this *known* *build* *breaking*
> > thing in an -rc series. I've already stated my reasons, and I _know_
> > it will break stuff. I've pointed out what the changes are. It's in
> > linux-next. No one has responded to that.
> >
> Then, can I send the following patch for -rc3 to fix the mxs build
> (I noticed the statement '# Please do not send patches to this file;
> it is automatically generated!' in the file)? Or do I have to disable
> the m28evk from mxs build?
it would not be the first patch to mach-types. And the next update
doesn't harm as it should include the entry for m28evk.
>
> Regards,
> Shawn
>
> ---8<----
> commit acbff8107c90a4d2a436cca53535f2fd35d109e7
> Author: Shawn Guo <shawn.guo@linaro.org>
> Date: Wed Nov 16 21:44:33 2011 +0800
>
> ARM: Update mach-types to fix mxs build breakage
>
> Add entry m28evk to fix the following mxs build breakage.
>
> CHK include/generated/compile.h
> CC arch/arm/mach-mxs/clock-mx28.o
> arch/arm/mach-mxs/clock-mx28.c: In function 'clk_misc_init':
> arch/arm/mach-mxs/clock-mx28.c:748: error: implicit declaration of
> function 'machine_is_m28evk'
> make[1]: *** [arch/arm/mach-mxs/clock-mx28.o] Error 1
> make: *** [arch/arm/mach-mxs] Error 2
>
> Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
Acked-by: Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>
Alternatively do
#ifndef machine_is_m28evk
#define machine_is_m28evk() 0
#endif
before it's use in arch/arm/mach-mxs/include/mach/mxs.h to fix the build
failure.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2011-11-16 18:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 1:49 Error for machine_is_m28evk Fabio Estevam
2011-11-08 5:16 ` Shawn Guo
2011-11-08 6:30 ` Stefano Babic
2011-11-08 7:53 ` Uwe Kleine-König
2011-11-08 8:09 ` Jason Liu
2011-11-08 8:53 ` Russell King - ARM Linux
2011-11-08 12:53 ` Shawn Guo
2011-11-08 13:37 ` Russell King - ARM Linux
2011-11-08 14:05 ` Will Deacon
2011-11-08 14:36 ` Arnaud Patard (Rtp)
2011-11-08 14:45 ` Russell King - ARM Linux
2011-11-08 14:53 ` Vincent Sanders
2011-11-16 5:59 ` Shawn Guo
2011-11-16 8:42 ` Russell King - ARM Linux
2011-11-16 13:58 ` Shawn Guo
2011-11-16 18:48 ` Uwe Kleine-König [this message]
2011-11-16 22:28 ` Shawn Guo
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=20111116184839.GS30612@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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