mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bryan Wu" <cooloney.lkml@gmail.com>
To: "Adrian Bunk" <bunk@kernel.org>
Cc: bryan.wu@analog.com, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] blackfin: remove dump_thread()
Date: Wed, 7 Nov 2007 11:39:12 +0800	[thread overview]
Message-ID: <386072610711061939j66e89f95s59e4e4ab4cbdbee9@mail.gmail.com> (raw)
In-Reply-To: <20071107032831.GW26163@stusta.de>

On Nov 7, 2007 11:28 AM, Adrian Bunk <bunk@kernel.org> wrote:
> On Wed, Nov 07, 2007 at 11:07:06AM +0800, Bryan Wu wrote:
> > On 11/6/07, Adrian Bunk <bunk@kernel.org> wrote:
> > > This patch removes the unused dump_thread().
> > >
> >
> > Why only remove it from Blackfin? any more reason?
>
> The only user is the a.out support.
>
> It was therefore removed prior to the blackfin merge from all
> architectures not supporting a.out.
>

OK, make sense. Currently, Blackfin doesn't suppport a.out.

Acked-by: Bryan Wu <bryan.wu@analog.com>



> > I found this in latest 2.6.24-rc2:
> >
> > --
> > Cscope tag: dump_thread
> >    #   line  filename / context / line
> >    1    324  arch/alpha/kernel/process.c <<dump_thread>>
> >              dump_thread(struct pt_regs * pt, struct user * dump)
> >    2    373  arch/arm/kernel/process.c <<dump_thread>>
> >              void dump_thread(struct pt_regs * regs, struct user * dump)
> >    3    244  arch/blackfin/kernel/process.c <<dump_thread>>
> >              void dump_thread(struct pt_regs *regs, struct user *dump)
> >    4    321  arch/m68k/kernel/process.c <<dump_thread>>
> >              void dump_thread(struct pt_regs * regs, struct user * dump)
> >    5    572  arch/sparc/kernel/process.c <<dump_thread>>
> >              void dump_thread(struct pt_regs * regs, struct user * dump)
> >    6    731  arch/sparc64/kernel/process.c <<dump_thread>>
> >              void dump_thread(struct pt_regs * regs, struct user * dump)
> >    7    306  arch/um/kernel/process.c <<dump_thread>>
> >              void dump_thread(struct pt_regs *regs, struct user *u)
> >    8    519  arch/x86/kernel/process_32.c <<dump_thread>>
> >              void dump_thread(struct pt_regs * regs, struct user * dump)
> > --
> >
> > Regards,
> > -Bryan
>
> cu
> Adrian
>
> --
>
>        "Is there not promise of rain?" Ling Tan asked suddenly out
>         of the darkness. There had been need of rain for many days.
>        "Only a promise," Lao Er said.
>                                        Pearl S. Buck - Dragon Seed
>
>

Thanks a lot.
-Bryan Wu

  reply	other threads:[~2007-11-07  3:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-05 17:07 Adrian Bunk
2007-11-07  3:07 ` Bryan Wu
2007-11-07  3:28   ` Adrian Bunk
2007-11-07  3:39     ` Bryan Wu [this message]
2007-11-07  3:41       ` Mike Frysinger

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=386072610711061939j66e89f95s59e4e4ab4cbdbee9@mail.gmail.com \
    --to=cooloney.lkml@gmail.com \
    --cc=bryan.wu@analog.com \
    --cc=bunk@kernel.org \
    --cc=linux-kernel@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

Powered by JetHome