From: Guenter Roeck <guenter.roeck@ericsson.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
Wim Van Sebroeck <wim@iguana.be>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
LM Sensors <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] [PATCH] hwmon/sch56xx: Depend on watchdog for watchdog core functions
Date: Fri, 1 Jun 2012 08:25:04 -0700 [thread overview]
Message-ID: <20120601152504.GA25384@ericsson.com> (raw)
In-Reply-To: <20120601160657.3b93393c@endymion.delvare>
On Fri, Jun 01, 2012 at 10:06:57AM -0400, Jean Delvare wrote:
> On Fri, 01 Jun 2012 15:37:55 +0200, Hans de Goede wrote:
> > Now that we've a common watchdog core, I would also like to convert the
> > fschmd watchdog code to it (one of these days). Which raises the question
> > through which tree should that conversion go in. fschmd is primarily a hwmon
> > driver, but the changes will only touch the watchdog part...
> >
> > I guess it would be best to get the conversion in to Wim's tree, even though
> > that slightly increases the chance of conflicts. The fschmd driver does not see
> > a lot of churn, and I think Wim is a better reviewer for watchdog related
> > patches :)
>
> Chances of conflicts are so thin, I vote for getting it through Wim's
> watchdog tree.
>
Ok with me.
Guenter
next prev parent reply other threads:[~2012-06-01 15:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 20:18 [PATCH] hwmon/sch56xx: Depend on watchdog for watchdog core functions Hans de Goede
2012-05-24 20:54 ` Wim Van Sebroeck
2012-05-29 16:11 ` [lm-sensors] " Guenter Roeck
2012-05-29 17:24 ` Wim Van Sebroeck
2012-06-01 13:37 ` [lm-sensors] " Hans de Goede
2012-06-01 14:06 ` Jean Delvare
2012-06-01 15:25 ` Guenter Roeck [this message]
2012-06-06 10:29 ` 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=20120601152504.GA25384@ericsson.com \
--to=guenter.roeck@ericsson.com \
--cc=hdegoede@redhat.com \
--cc=khali@linux-fr.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=lm-sensors@lm-sensors.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