All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: kernel update (relative to 2.6.0-test4)
Date: Wed, 27 Aug 2003 16:34:42 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106200240214008@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106192276030286@msgid-missing>

>   Tony> Any clues on what the warning from OBJCOPY really means?
> 
> Nope.  I don't get that (building for zx1):


Ok, I found it.  I somehow ended up with CONFIG_PM=y, so "kernel/power"
got built, and inside kernel/power/main.c there is:

  static int in_suspend __nosavedata = 0;

where __nosavedata is defined in include/linux/init.h as:

#define __nosavedata __attribute__ ((__section__ (".data.nosave")))

We don't have an entry in vmlinux.lds.S to handle this section.

-Tony

  parent reply	other threads:[~2003-08-27 16:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-26 18:29 kernel update (relative to 2.6.0-test4) David Mosberger
2003-08-26 21:16 ` Alex Williamson
2003-08-27 16:01 ` Luck, Tony
2003-08-27 16:22 ` David Mosberger
2003-08-27 16:34 ` Luck, Tony [this message]
2003-08-27 16:52 ` Luck, Tony
2003-08-27 16:54 ` Matthew Wilcox

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=marc-linux-ia64-106200240214008@msgid-missing \
    --to=tony.luck@intel.com \
    --cc=linux-ia64@vger.kernel.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 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.