From: Timur Tabi <timur@freescale.com>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org, Wim Van Sebroeck <wim@iguana.be>
Subject: Re: [PATCH 1/3] [WATCHDOG] mpc83xx_wdt: add support for MPC86xx CPUs
Date: Mon, 12 May 2008 16:01:06 -0500 [thread overview]
Message-ID: <4828B012.9090805@freescale.com> (raw)
In-Reply-To: <4828AFBD.1040501@freescale.com>
Scott Wood wrote:
> It avoids confusion. I vote for renaming.
Me too. How about fsl_wdt.c?
Or we could come up with a name for that particular WDT device, like we
did with the 85xx DMA controller.
next prev parent reply other threads:[~2008-05-12 21:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 18:52 [PATCH 1/3] [WATCHDOG] mpc83xx_wdt: add support for MPC86xx CPUs Anton Vorontsov
2008-05-12 18:58 ` Scott Wood
2008-05-12 19:24 ` Kumar Gala
2008-05-12 19:44 ` Jochen Friedrich
2008-05-12 20:53 ` Anton Vorontsov
2008-05-12 20:59 ` Scott Wood
2008-05-12 21:01 ` Timur Tabi [this message]
2008-05-12 21:18 ` Anton Vorontsov
2008-05-12 21:20 ` Timur Tabi
2008-05-12 21:35 ` Anton Vorontsov
2008-05-12 21:42 ` Timur Tabi
2008-05-12 21:48 ` Anton Vorontsov
2008-05-12 21:55 ` Timur Tabi
2008-05-12 22:12 ` Anton Vorontsov
2008-05-13 1:06 ` Kumar Gala
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=4828B012.9090805@freescale.com \
--to=timur@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
--cc=wim@iguana.be \
/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).