linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: "Albrecht Dreß" <albrecht.dress@arcor.de>
Cc: linuxppc-dev@ozlabs.org, devicetree-discuss@lists.ozlabs.org,
	wim@iguana.be
Subject: Re: Re: [PATCH 3/3] mpc52xx/wdt: WDT uses GPT api
Date: Wed, 11 Nov 2009 13:18:36 -0700	[thread overview]
Message-ID: <fa686aa40911111218g62bf8f50k99c786ec6f5421b4@mail.gmail.com> (raw)
In-Reply-To: <16246194.1257928342802.JavaMail.ngmail@webmail19.ha2.local>

On Wed, Nov 11, 2009 at 1:32 AM, Albrecht Dre=DF <albrecht.dress@arcor.de> =
wrote:
> Hi Grant:
>
> O.k., thanks for your comments. =A0If Wim doesn't have any objections to =
it, I will provide a merged patch. =A0One consequence I forgot to mention i=
s that we loose the ability to build the wdt support as module, but I don't=
 think it's a real problem.

I'm not too worried about this.  It is also potentially possible to
rework the entire GPT driver as a module.  But there are non-trivial
architecture fiddly bits needed to make it safe to load IRQ
controllers in a module.

> I think we still should keep the kernel config option enable/disable the =
wdt support, which would mask out the wdt code if disabled. =A0Is that ok f=
or you?

Yup.

g.

--=20
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  reply	other threads:[~2009-11-11 20:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10 19:43 [PATCH 3/3] mpc52xx/wdt: WDT uses GPT api Albrecht Dreß
2009-11-10 19:59 ` Grant Likely
2009-11-10 20:26   ` Albrecht Dreß
2009-11-10 21:07     ` Grant Likely
2009-11-11  8:32     ` Aw: " Albrecht Dreß
2009-11-11 20:18       ` Grant Likely [this message]
2009-11-12 21:36     ` Wim Van Sebroeck
2009-11-13  6:21       ` Grant Likely
2009-12-08 20:48         ` Wim Van Sebroeck
2009-12-08 21:21           ` Grant Likely

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=fa686aa40911111218g62bf8f50k99c786ec6f5421b4@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=albrecht.dress@arcor.de \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=linuxppc-dev@ozlabs.org \
    --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).