From: Dirk Behme <dirk.behme@googlemail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] ARM: OMAP: Fix broken N770 build
Date: Sat, 11 Nov 2006 07:07:17 +0100 [thread overview]
Message-ID: <45556895.8080008@gmail.com> (raw)
In-Reply-To: <20061111000316.GN26185@atomide.com>
Tony Lindgren wrote:
> Also left out the defconfig changes as they
> don't seem to do anything. Let me know if something is needed
> on the defconfig.
In -rc4 CONFIG_HWMON wasn't evaluated to y necessary to
build stuff cleanly. Seems that in -rc5 this is fixed. Now,
CONFIG_HWMON is default y and n770_defconfig builds fine
without the defconfig patch.
Thanks for updates,
Dirk
Btw: Last warning I see with n770_defconfig in our code is
arch/arm/plat-omap/sti/sti-console.c: In function
'sti_channel_puts':
arch/arm/plat-omap/sti/sti-console.c:48: warning: value
computed is not used
arch/arm/plat-omap/sti/sti-console.c:57: warning: value
computed is not used
Anybody with an idea here?
next prev parent reply other threads:[~2006-11-11 6:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 18:31 [PATCH] ARM: OMAP: Fix broken N770 build Dirk Behme
2006-11-11 0:03 ` Tony Lindgren
2006-11-11 6:07 ` Dirk Behme [this message]
2006-11-11 12:19 ` David Weinehall
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=45556895.8080008@gmail.com \
--to=dirk.behme@googlemail.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=tony@atomide.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.