public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.24-git7: section mismatches woes
Date: Sun, 3 Feb 2008 13:37:34 +0100	[thread overview]
Message-ID: <20080203123734.GH20810@uranus.ravnborg.org> (raw)
In-Reply-To: <200802031332.01827.rjw@sisk.pl>

> > > suspend to RAM working?
> > I dunno - never used it I'm afraid. And do not know how to do it either.
> 
> # echo mem > /sys/power/state
> 
> (better do it after a fresh boot for the first time in case it fails).

Will try later - thanks.

> > The way to approach it is straightforward but boring.
> > 
> > You can add:
> > ccflags-y += -fno-inline-functions-called-once
> > to the Makefiles where you think this can have caused troubles until
> > you find the problematic directory.
> > kbuild will pick up that gcc options changed and rebuild
> > all relevant files.
> > 
> > When the problematic directory is located then
> > remove the ccflags-y assignment and do it file-by-file
> > using the CFLAGS_xxx.o syntax:
> > 
> > CFLAGS_file.o := -fno-inline-functions-called-once
> 
> Do I have to pass any special options to "make"?

When you do it this way by tweaking the Makefiles - no.
And you do not have to delete .o files manually to get them
rebuild.

	Sam

      reply	other threads:[~2008-02-03 12:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-30 18:50 2.6.24-git7: section mismatches woes Rafael J. Wysocki
2008-01-30 19:08 ` Sam Ravnborg
2008-01-30 21:32   ` Rafael J. Wysocki
2008-02-02 18:08     ` Sam Ravnborg
2008-02-02 22:47       ` Rafael J. Wysocki
2008-02-03 10:12         ` Sam Ravnborg
2008-02-03 12:32           ` Rafael J. Wysocki
2008-02-03 12:37             ` Sam Ravnborg [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=20080203123734.GH20810@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.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