From: Guenter Roeck <linux@roeck-us.net>
To: "Bruno André Ferreira" <bruno.ferreira@efacec.com>
Cc: Wim Van Sebroeck <wim@iguana.be>,
Giel van Schijndel <me@mortis.eu>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>
Subject: Re: Fintek F81865 chip (Wdog support)
Date: Fri, 02 Aug 2013 14:01:35 -0700 [thread overview]
Message-ID: <51FC1E2F.6020308@roeck-us.net> (raw)
In-Reply-To: <D9EA4899424AAF4E89868AB4BB0DCD82879596A5@S103.efacec.pt>
On 08/02/2013 07:48 AM, Bruno André Ferreira wrote:
> Sorry.
>
> Wrong driver...
>
> Best regards,
> Bruno Ferreira
> ________________________________________
> From: BrunoFerreira [bruno.ferreira@efacec.com]
> Sent: Friday, August 02, 2013 3:17 PM
> To: Wim Van Sebroeck
> Cc: Giel van Schijndel; linux-watchdog@vger.kernel.org
> Subject: Re: Fintek F81865 chip (Wdog support)
>
> Hi All.
>
> Sorry about the delay.
> Please find in attach the driver source code with support for this chip.
>
Hi Bruno,
Just wondering ... why didn't you just add the new chip type to the existing f71808e driver ?
I don't see a significant enough difference to warrant a new driver. Your driver doesn't
support minutes mode, but I am quite sure that is not a chip limitation. Other than that,
everything seems to be identical.
Thanks,
Guenter
--
To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-08-02 21:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51409586.4030204@efacec.com>
2013-03-26 17:26 ` Fintek F81865 chip (Wdog support) Giel van Schijndel
2013-05-26 16:44 ` Wim Van Sebroeck
2013-08-02 14:17 ` BrunoFerreira
2013-08-02 14:48 ` Bruno André Ferreira
2013-08-02 21:01 ` Guenter Roeck [this message]
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=51FC1E2F.6020308@roeck-us.net \
--to=linux@roeck-us.net \
--cc=bruno.ferreira@efacec.com \
--cc=linux-watchdog@vger.kernel.org \
--cc=me@mortis.eu \
--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 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.