mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dan Williams" <dan.j.williams@gmail.com>
To: "Wim Van Sebroeck" <wim@iguana.be>
Cc: "Curt E. Bruns" <curt.e.bruns@intel.com>,
	"Peter Milne" <peter.milne@d-tacq.com>,
	"Russell King" <rmk@arm.linux.org.uk>,
	linux-kernel@vger.kernel.org,
	"Lennert Buytenhek" <buytenh@wantstofly.org>
Subject: Re: [2.6.22 patch] iop: combined watchdog timer driver for iop3xx and iop13xx
Date: Sun, 6 May 2007 15:47:32 -0700	[thread overview]
Message-ID: <e9c3a7c20705061547u7de21fas6ccad4258da57a9e@mail.gmail.com> (raw)
In-Reply-To: <20070506205320.GA6486@infomag.infomag.iguana.be>

On 5/6/07, Wim Van Sebroeck <wim@iguana.be> wrote:
> Hi Dan,
>
> > >Could you split this patch into 2 patches: one that deals with the moving
> > >of
> > >the architecture dependant code (and explaining why) and one with the new
> > >watchdog drivers? I will continue my review today.
> > >
> >
> > I am one of the maintainers of this architecture, (Lennert Buytenhek
> > is the other).  I will go ahead and split this up so you can sign-off
> > on the watchdog specific bits.  The intent is to move all hardware
> > definitions under #include <asm/hardware.h>.  You are right this
> > should have been a separate patch.
>
> I reviewed the rest of the code. Looks OK to me. One small remark though:
> Can we change the ifdef's in the code as described in section 2 point 2 of
> the Documentation/SubmittingPatches document?
>
Ok, I can add this cleanup.

Barring any objections I'll go ahead and submit the revised patch with
an "Acked-by: Wim Van Sebroeck <wim at iguana dot be>" to Russell's
ARM patch tracker.

> Thanks,
> Wim.
>

Dan

  reply	other threads:[~2007-05-06 22:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-30 16:57 Dan Williams
2007-05-06  9:52 ` Wim Van Sebroeck
2007-05-06 20:13   ` Dan Williams
2007-05-06 20:18     ` Lennert Buytenhek
2007-05-06 20:53     ` Wim Van Sebroeck
2007-05-06 22:47       ` Dan Williams [this message]
2007-05-07 19:03         ` Wim Van Sebroeck

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=e9c3a7c20705061547u7de21fas6ccad4258da57a9e@mail.gmail.com \
    --to=dan.j.williams@gmail.com \
    --cc=buytenh@wantstofly.org \
    --cc=curt.e.bruns@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.milne@d-tacq.com \
    --cc=rmk@arm.linux.org.uk \
    --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

all inboxes | Powered by JetHome®