All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: GERBER Patrick <Patrick.Gerber@heig-vd.ch>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [Patch] Error when compiling without CONFIG_PM_DEBUG
Date: Fri, 01 Oct 2010 08:15:18 -0700	[thread overview]
Message-ID: <871v8ac5bt.fsf@deeprootsystems.com> (raw)
In-Reply-To: <8959501C0BAF9F40956CEBAD13FB297F17F38C757C@EINTMBX.einet.ad.eivd.ch> (GERBER Patrick's message of "Fri, 1 Oct 2010 14:46:56 +0200")

GERBER Patrick <Patrick.Gerber@heig-vd.ch> writes:

> Hello all,
>
> I have compiled a fresh clone of the linux-omap-2.6 kernel for overo and I have linker error.
>
> The serial.c and pm34xx.c files used some variables declared as
> extern. The real declaration of those variables are on pm-debug.c and
> are compiled only with CONFIG_PM_DEBUG.  

Hi Patric, thanks for the patch.

A couple days ago, a similar patch was posted by Loïc Minier to fix the
same issue, and I'm waiting an updated version of his patch.

> So I have added some #ifdef to correct the error. I don't know if it's
> the best idea but anyway with the attached patch it's work.

Adding #ifdefs in this way is generally not done in the kernel.  For
another example of how to solve the same problem, see the patch from
Loïc.  Also see the '#ifdefs are ugly' section of
Documentation/SubmittingPatches in the kernel source.

Thanks again for contributing your fixes back,

Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2010-10-01 15:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-01 12:46 [Patch] Error when compiling without CONFIG_PM_DEBUG GERBER Patrick
2010-10-01 15:15 ` Kevin Hilman [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=871v8ac5bt.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=Patrick.Gerber@heig-vd.ch \
    --cc=linux-omap@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.