From: Willy Tarreau <willy@w.ods.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Calin A. Culianu" <calin@ajvar.org>,
linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] Watchdog: Winsystems EPX-C3 SBC
Date: Sat, 14 Jan 2006 21:08:39 +0100 [thread overview]
Message-ID: <20060114200839.GA14036@w.ods.org> (raw)
In-Reply-To: <1137266649.23269.2.camel@localhost.localdomain>
On Sat, Jan 14, 2006 at 07:24:09PM +0000, Alan Cox wrote:
> Some quick comments:
>
> + if (len) {
> + epx_c3_pet();
> + }
>
> Doesn't need brackets (minor style)
>
> Otherwise it looks excellent but should use request_region and friends
> to claim the two ports it uses.
You just remind me that I had to comment out the request_region in another
watchdog driver I wrote, because the hardware was mapped on I/O port 0xF2
which is within the FPU I/O space :
00f0-00ff : fpu
I did not know how to correctly fix this problem, and I could live without
the check, but I found it dirty and never proposed it for inclusion.
It's not the first time I notice that write-only hardware share a reserved
I/O range with other components, and I don't know how to cope with this.
Perhaps it sounds logical not to request_region() as the hardware is meant
to be 100% transparent afterall ?
> The see the "Sign your work:" bit of Documentation/SubmittingPatches are
> it looks ready to go in.
>
> Alan
Willy
next prev parent reply other threads:[~2006-01-14 20:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-14 2:59 Calin A. Culianu
2006-01-14 19:24 ` Alan Cox
2006-01-14 20:08 ` Willy Tarreau [this message]
2006-01-29 23:47 ` Marcelo Tosatti
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=20060114200839.GA14036@w.ods.org \
--to=willy@w.ods.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=calin@ajvar.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome