public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: 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: Thu, 14 Nov 2013 16:31:53 +0400	[thread overview]
Message-ID: <5284C2B9.2020805@cogentembedded.com> (raw)
In-Reply-To: <528418B1.6090507@cn.fujitsu.com>

Hello.

On 14-11-2013 4:26, 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...

> Strange? It's the build error log.

    I've never seen the leading > characters in gcc's error output.

>>> This is introduced by commit 16559ae.

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

> commit 16559ae48c76f1ceb970b9719dea62b77eb5d06b
> Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Date:   Mon Feb 4 15:35:26 2013 -0800

>      kgdb: remove #include <linux/serial_8250.h> from kgdb.h
>
>      There's no reason kgdb.h itself needs to include the 8250 serial port
>      header file.  So push it down to the _very_ limited number of individual
>      drivers that need the values in that file, and fix up the places where
>      people really wanted serial_core.h and platform_device.h.

>      Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>


> And the line caused this build error is:

> diff --git a/include/linux/kgdb.h b/include/linux/kgdb.h
> index 4dff0c6..c6e091b 100644
> --- a/include/linux/kgdb.h
> +++ b/include/linux/kgdb.h
> @@ -13,7 +13,6 @@
>   #ifndef _KGDB_H_
>   #define _KGDB_H_
>
> -#include <linux/serial_8250.h>
>   #include <linux/linkage.h>
>   #include <linux/init.h>
>   #include <linux/atomic.h>

    That's all interesting but what I asked you to do is add the summary line 
("kgdb: remove #include <linux/serial_8250.h> from kgdb.h" in this case) 
enclosed into parentheses to your commit log. There was no need to tell me all 
the gory details of your fix. :-)

> Thanks,
> Wanlong Gao

WBR, Sergei


      reply	other threads:[~2013-11-14 12:31 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 18:14 ` Sergei Shtylyov
2013-11-14  0:26   ` Wanlong Gao
2013-11-14 12:31     ` Sergei Shtylyov [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=5284C2B9.2020805@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