From: Timur Tabi <timur@freescale.com>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: Josh Boyer <jwboyer@gmail.com>,
kumar.gala@freescale.com, linux-watchdog@vger.kernel.org,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 2/2] powerpc/watchdog: allow the e500 watchdog driver to be compiled as a module
Date: Mon, 20 Sep 2010 14:53:08 -0500 [thread overview]
Message-ID: <4C97BBA4.9090401@freescale.com> (raw)
In-Reply-To: <20100920193016.GA3845@zod.rchland.ibm.com>
Josh Boyer wrote:
> I guess I don't see what you mean. It talks about e500 but it doesn't
> say "Book-E" anywhere in that comment. (Though I'm pretty sure that
> comment does apply to 4xx.)
That was my point. The comment says e500, but the code is also intended for
4xx.
--
Timur Tabi
Linux kernel developer at Freescale
WARNING: multiple messages have this Message-ID (diff)
From: Timur Tabi <timur@freescale.com>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, kumar.gala@freescale.com,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH 2/2] powerpc/watchdog: allow the e500 watchdog driver to be compiled as a module
Date: Mon, 20 Sep 2010 14:53:08 -0500 [thread overview]
Message-ID: <4C97BBA4.9090401@freescale.com> (raw)
In-Reply-To: <20100920193016.GA3845@zod.rchland.ibm.com>
Josh Boyer wrote:
> I guess I don't see what you mean. It talks about e500 but it doesn't
> say "Book-E" anywhere in that comment. (Though I'm pretty sure that
> comment does apply to 4xx.)
That was my point. The comment says e500, but the code is also intended for
4xx.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2010-09-20 19:53 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 22:53 [PATCH 1/2] powerpc: export ppc_tb_freq so that modules can reference it Timur Tabi
2010-09-17 22:53 ` [PATCH 2/2] powerpc/watchdog: allow the e500 watchdog driver to be compiled as a module Timur Tabi
2010-09-18 0:37 ` Josh Boyer
2010-09-18 0:37 ` Josh Boyer
2010-09-20 15:51 ` Timur Tabi
2010-09-20 15:51 ` Timur Tabi
2010-09-20 19:30 ` Josh Boyer
2010-09-20 19:30 ` Josh Boyer
2010-09-20 19:53 ` Timur Tabi [this message]
2010-09-20 19:53 ` Timur Tabi
2010-09-18 0:38 ` [PATCH 1/2] powerpc: export ppc_tb_freq so that modules can reference it Josh Boyer
2010-09-18 0:38 ` Josh Boyer
2010-09-18 1:20 ` Timur Tabi
2010-09-18 1:20 ` Timur Tabi
2010-09-18 3:14 ` Benjamin Herrenschmidt
2010-09-18 3:14 ` Benjamin Herrenschmidt
2010-09-18 14:36 ` Tabi Timur-B04825
2010-09-18 14:36 ` Tabi Timur-B04825
2010-09-18 15:34 ` Kumar Gala
2010-09-18 15:34 ` Kumar Gala
2010-09-18 15:52 ` Vitaly Wool
2010-09-18 15:52 ` Vitaly Wool
2010-09-18 16:56 ` Josh Boyer
2010-09-18 16:56 ` Josh Boyer
2010-09-18 17:36 ` Tabi Timur-B04825
2010-09-18 17:46 ` Josh Boyer
2010-09-18 17:46 ` Josh Boyer
2010-09-18 17:55 ` Tabi Timur-B04825
2010-09-18 18:22 ` Josh Boyer
2010-09-18 18:22 ` Josh Boyer
2010-09-20 18:51 ` Scott Wood
2010-09-20 18:51 ` Scott Wood
[not found] ` <20100920135136.04ceb772__36164.799918379$1285008751$gmane$org@udp111988uds.am.freescale.net>
2010-09-21 12:34 ` Detlev Zundel
2010-09-18 18:36 ` Kumar Gala
2010-09-18 18:36 ` Kumar Gala
2010-09-19 2:42 ` Benjamin Herrenschmidt
2010-09-19 2:42 ` Benjamin Herrenschmidt
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=4C97BBA4.9090401@freescale.com \
--to=timur@freescale.com \
--cc=jwboyer@gmail.com \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=kumar.gala@freescale.com \
--cc=linux-watchdog@vger.kernel.org \
--cc=linuxppc-dev@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.