From: Mark Salter <msalter@redhat.com>
To: Chen Gang <xili_gchen_5257@hotmail.com>
Cc: a-jacquiot@ti.com, linux-c6x-dev@linux-c6x.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] c6x: kernel: setup: Export symbol memory_end
Date: Thu, 26 Mar 2015 10:58:16 -0400 [thread overview]
Message-ID: <1427381896.9430.49.camel@deneb.redhat.com> (raw)
In-Reply-To: <BLU436-SMTP257F4DBA53508E368896955B91E0@phx.gbl>
On Wed, 2015-03-04 at 14:44 +0800, Chen Gang wrote:
> It is needed by several modules, the related error with allmodconfig:
>
> MODPOST 3327 modules
> ERROR: "memory_end" [net/wireless/lib80211_crypt_tkip.ko] undefined!
> ERROR: "memory_end" [net/sunrpc/sunrpc.ko] undefined!
> ERROR: "memory_end" [net/sunrpc/auth_gss/rpcsec_gss_krb5.ko] undefined!
> ERROR: "memory_end" [net/rxrpc/rxkad.ko] undefined!
> ERROR: "memory_end" [net/mac802154/mac802154.ko] undefined!
> ERROR: "memory_end" [net/mac80211/mac80211.ko] undefined!
> ERROR: "memory_end" [net/ipv6/esp6.ko] undefined!
> ERROR: "memory_end" [net/ipv6/ah6.ko] undefined!
> ERROR: "memory_end" [net/ipv4/esp4.ko] undefined!
> ERROR: "memory_end" [net/ipv4/ah4.ko] undefined!
> ERROR: "memory_end" [net/ceph/libceph.ko] undefined!
> ERROR: "memory_end" [net/9p/9pnet_virtio.ko] undefined!
> ERROR: "memory_end" [drivers/usb/wusbcore/wusbcore.ko] undefined!
> ERROR: "memory_end" [drivers/usb/misc/usbtest.ko] undefined!
> ERROR: "memory_end" [drivers/usb/core/usbcore.ko] undefined!
> ERROR: "memory_end" [drivers/target/target_core_file.ko] undefined!
> ERROR: "memory_end" [drivers/net/wireless/brcm80211/brcmfmac/brcmfmac.ko] undefined!
> ERROR: "memory_end" [drivers/net/wireless/ath/ath6kl/ath6kl_sdio.ko] undefined!
> ERROR: "memory_end" [drivers/net/virtio_net.ko] undefined!
> ERROR: "memory_end" [drivers/net/usb/usbnet.ko] undefined!
> ERROR: "memory_end" [drivers/net/ppp/ppp_mppe.ko] undefined!
> ERROR: "memory_end" [drivers/mtd/nand/nand.ko] undefined!
> ERROR: "memory_end" [drivers/mmc/card/mmc_block.ko] undefined!
> ERROR: "memory_end" [drivers/crypto/qce/qcrypto.ko] undefined!
> ERROR: "memory_end" [drivers/block/drbd/drbd.ko] undefined!
> ERROR: "memory_end" [drivers/block/aoe/aoe.ko] undefined!
> ERROR: "memory_end" [crypto/tcrypt.ko] undefined!
> ERROR: "memory_end" [crypto/gcm.ko] undefined!
> ERROR: "memory_end" [crypto/cts.ko] undefined!
> ERROR: "memory_end" [crypto/ccm.ko] undefined!
> ERROR: "memory_end" [crypto/authencesn.ko] undefined!
> ERROR: "memory_end" [crypto/authenc.ko] undefined!
>
> Signed-off-by: Chen Gang <gang.chen.5i5j@gmail.com>
> ---
Thanks! I added this to the c6x tree for next merge window.
> arch/c6x/kernel/setup.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/c6x/kernel/setup.c b/arch/c6x/kernel/setup.c
> index 165bbd9..72e17f7 100644
> --- a/arch/c6x/kernel/setup.c
> +++ b/arch/c6x/kernel/setup.c
> @@ -63,6 +63,7 @@ unsigned char c6x_fuse_mac[6];
>
> unsigned long memory_start;
> unsigned long memory_end;
> +EXPORT_SYMBOL(memory_end);
>
> unsigned long ram_start;
> unsigned long ram_end;
prev parent reply other threads:[~2015-03-26 14:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 6:44 Chen Gang
2015-03-26 14:58 ` Mark Salter [this message]
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=1427381896.9430.49.camel@deneb.redhat.com \
--to=msalter@redhat.com \
--cc=a-jacquiot@ti.com \
--cc=linux-c6x-dev@linux-c6x.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xili_gchen_5257@hotmail.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
all inboxes | Powered by JetHome®