linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <kumar.gala@freescale.com>
To: "Takeharu KATO" <takeharu1219@ybb.ne.jp>
Cc: Glenn Burkhardt <glenn@aoi-industries.com>,
	"Gala Kumar K.-galak" <galak@freescale.com>,
	linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] BOOKE_WDT Part 1/2 (Re: PPC 44x Watchdog timer)
Date: Tue, 17 May 2005 12:00:04 -0500	[thread overview]
Message-ID: <fb7df67f9dda2794b4af2dfa9b4754ca@freescale.com> (raw)
In-Reply-To: <428A040D.40604@ybb.ne.jp>


On May 17, 2005, at 9:47 AM, Takeharu KATO wrote:

> Hi Kumar:
>
> >> No problem, can you replace all the cmd line parsing with
> >> early_param() code in arch/ppc/kernel/setup.c.=A0 Take a look at
> >> arch/ppc64/kernel/setup.c for an example.=A0 We still need to add a=20=

> call
> >> to parse_early_param() in setup_arch().
>  >>
>  > Sorry, I can not figure out what you want.
> > As far as I look the source tree,arch/ppc/kernel/setup.c does not=20
> have
>  > the function called early_param.
>  > Would you give me a more precise explanation?
>  >
> On second thought, I make sense what you said.
> You asked me that I make some kind of cleanups, didn't you?
>  If it is true, I'll try to clean up these setups, but it may be
>  take the time.

Yes, I think with these changes to us early_param() for command line=20
parsing in a single place will make the first patch look good.

I'm still not sure what suggestions I have for the second patch, I was=20=

more just letting you know my thinking about the fact that it concerned=20=

me that the exception handler code was not in arch/ppc/kernel.  Not to=20=

say this is wrong, it just doesn't feel write.

- kumar

  reply	other threads:[~2005-05-17 17:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19  1:37 PPC 44x Watchdog timer Glenn Burkhardt
2005-04-20 11:35 ` Takeharu KATO
2005-04-20 12:02   ` Glenn Burkhardt
2005-05-05  2:07     ` Takeharu KATO
2005-05-05 14:02       ` Kumar Gala
2005-05-05 21:43         ` Takeharu KATO
2005-05-06 21:04         ` [PATCH] BOOKE_WDT Part 1/2 (Re: PPC 44x Watchdog timer) Takeharu KATO
2005-05-12 15:37           ` Kumar Gala
2005-05-16  6:57             ` Takeharu KATO
2005-05-17  1:21               ` Kumar Gala
2005-05-17  5:59                 ` Takeharu KATO
2005-05-17 14:47                   ` Takeharu KATO
2005-05-17 17:00                     ` Kumar Gala [this message]
2005-05-17 17:41                       ` Takeharu KATO
2005-05-06 21:04         ` [PATCH] BOOKE_WDT Part 2/2 " Takeharu KATO

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=fb7df67f9dda2794b4af2dfa9b4754ca@freescale.com \
    --to=kumar.gala@freescale.com \
    --cc=galak@freescale.com \
    --cc=glenn@aoi-industries.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=takeharu1219@ybb.ne.jp \
    /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).