mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Huang Weiyi <weiyi.huang@gmail.com>
Cc: mingo@redhat.com, hpa@zytor.com, x86@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/8] x86: remove dupilcated #include
Date: Wed, 8 Apr 2009 14:21:21 +0200	[thread overview]
Message-ID: <20090408122121.GB18581@elte.hu> (raw)
In-Reply-To: <1239009605-1796-1-git-send-email-weiyi.huang@gmail.com>


* Huang Weiyi <weiyi.huang@gmail.com> wrote:

> Remove dupilcated #include in arch/x86/kernel/dumpstack.c.
> 
> Signed-off-by: Huang Weiyi <weiyi.huang@gmail.com>
> ---
>  arch/x86/kernel/dumpstack.c |    1 -
>  1 files changed, 0 insertions(+), 1 deletions(-)
> 
> diff --git a/arch/x86/kernel/dumpstack.c b/arch/x86/kernel/dumpstack.c
> index 95ea5fa..6d7966d 100644
> --- a/arch/x86/kernel/dumpstack.c
> +++ b/arch/x86/kernel/dumpstack.c
> @@ -15,7 +15,6 @@
>  #include <linux/bug.h>
>  #include <linux/nmi.h>
>  #include <linux/sysfs.h>
> -#include <linux/ftrace.h>
>  
>  #include <asm/stacktrace.h>

Many of those include lines are probably unnecessary. Instead of 
these trivial patches causing churn, would you be interested in 
doing a comprehensive search to eliminate all the unused ones?
That would be a real step forward. (and this holds for your 
other patches in this series too.)

The include files section of fault.c might be a good template to 
use:

#include <linux/magic.h>		/* STACK_END_MAGIC		*/
#include <linux/sched.h>		/* test_thread_flag(), ...	*/
#include <linux/kdebug.h>		/* oops_begin/end, ...		*/
#include <linux/module.h>		/* search_exception_table	*/
#include <linux/bootmem.h>		/* max_low_pfn			*/
#include <linux/kprobes.h>		/* __kprobes, ...		*/
#include <linux/mmiotrace.h>		/* kmmio_handler, ...		*/
#include <linux/perf_counter.h>		/* perf_swcounter_*(), ...	*/

#include <asm/traps.h>			/* dotraplinkage, ...		*/
#include <asm/pgalloc.h>		/* pgd_*(), ...			*/
#include <asm/kmemcheck.h>		/* kmemcheck_*(), ...		*/

I was able to eliminate half of all include file lines there.

See latest -tip for that:

  http://people.redhat.com/mingo/tip.git/README

Thanks,

	Ingo

  reply	other threads:[~2009-04-08 12:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06  9:20 Huang Weiyi
2009-04-08 12:21 ` Ingo Molnar [this message]
2009-04-08 13:58   ` Sam Ravnborg
2009-04-08 14:12     ` Ingo Molnar
2009-04-08 18:43       ` Sam Ravnborg
2009-04-09  4:30         ` Ingo Molnar

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=20090408122121.GB18581@elte.hu \
    --to=mingo@elte.hu \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=weiyi.huang@gmail.com \
    --cc=x86@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

all inboxes | Powered by JetHome®