All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takeharu KATO <takeharu1219@ybb.ne.jp>
To: Kumar Gala <kumar.gala@freescale.com>
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: Wed, 18 May 2005 02:41:33 +0900	[thread overview]
Message-ID: <428A2CCD.5070704@ybb.ne.jp> (raw)
In-Reply-To: <fb7df67f9dda2794b4af2dfa9b4754ca@freescale.com>

Hi Kumar:

> 
> Yes, I think with these changes to us early_param() for command line 
> parsing in a single place will make the first patch look good.
>
OK, I'll perform this fix in this week.

> I'm still not sure what suggestions I have for the second patch, I was 
> more just letting you know my thinking about the fact that it concerned 
> me that the exception handler code was not in arch/ppc/kernel.  Not to 
> say this is wrong, it just doesn't feel write.
> 
Hum, I agree this thing, I'll move the WDT exception handler to 
arch/ppc/kernel for the moment.
If someone disagree with this decision in the future, I'll move this 
into driver code again.

  reply	other threads:[~2005-05-17 17:36 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
2005-05-17 17:41                       ` Takeharu KATO [this message]
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=428A2CCD.5070704@ybb.ne.jp \
    --to=takeharu1219@ybb.ne.jp \
    --cc=galak@freescale.com \
    --cc=glenn@aoi-industries.com \
    --cc=kumar.gala@freescale.com \
    --cc=linuxppc-embedded@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.