linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Wanlong Gao <gaowanlong@cn.fujitsu.com>,
	linux-sh@vger.kernel.org, lethal@linux-sh.org
Cc: linux-kernel@vger.kernel.org, fengguang.wu@intel.com, kbuild-all@01.org
Subject: Re: [PATCH] sh: fix kernel build error
Date: Wed, 13 Nov 2013 17:14:50 +0000	[thread overview]
Message-ID: <5283C19D.4050601@cogentembedded.com> (raw)
In-Reply-To: <1384353504-21886-1-git-send-email-gaowanlong@cn.fujitsu.com>

Hello.

On 11/13/2013 05:38 PM, Wanlong Gao wrote:

>     arch/sh/kernel/kgdb.c: In function 'sleeping_thread_to_gdb_regs':
>>> arch/sh/kernel/kgdb.c:225:32: error: implicit declaration of function 'task_stack_page' [-Werror=implicit-function-declaration]
>>> arch/sh/kernel/kgdb.c:242:23: error: dereferencing pointer to incomplete type
>>> arch/sh/kernel/kgdb.c:243:22: error: dereferencing pointer to incomplete type
>     arch/sh/kernel/kgdb.c: In function 'singlestep_trap_handler':
>>> arch/sh/kernel/kgdb.c:310:27: error: 'SIGTRAP' undeclared (first use in this function)
>     arch/sh/kernel/kgdb.c:310:27: note: each undeclared identifier is reported only once for each function it appears in
>     cc1: all warnings being treated as errors

    Strange quoting...

> This is introduced by commit 16559ae.

    Please also specify that commit's summary line in parens.

> CC: kbuild-all@01.org
> Reported-by: Fengguang Wu <fengguang.wu@intel.com>
> Signed-off-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>

WBR, Sergei


  reply	other threads:[~2013-11-13 17:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-13 14:38 [PATCH] sh: fix kernel build error Wanlong Gao
2013-11-13 17:14 ` Sergei Shtylyov [this message]
2013-11-14  0:26   ` Wanlong Gao
2013-11-14 12:31     ` Sergei Shtylyov

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=5283C19D.4050601@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=fengguang.wu@intel.com \
    --cc=gaowanlong@cn.fujitsu.com \
    --cc=kbuild-all@01.org \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).