public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Wim Van Sebroeck <wim@iguana•be>
To: Guenter Roeck <guenter.roeck@ericsson•com>
Cc: "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: [PATCH] hwmon/sch56xx: Depend on watchdog for watchdog core functions
Date: Tue, 29 May 2012 19:24:39 +0200	[thread overview]
Message-ID: <20120529172439.GY3074@spo001.leaseweb.com> (raw)
In-Reply-To: <1338307894.478.68.camel@groeck-laptop>

Hi Guenter,

> > > Since the watchdog code in sch56xx-common now uses the watchdog core, the
> > > Kconfig entires for the sch5627 and sch5636 should depend on WATCHDOG
> > > being set.
> > > 
> > > Signed-off-by: Hans de Goede <hdegoede@redhat•com>
> > 
> > I added also the "select WATCHDOG_CORE" lines for both drivers.
> > In linux-watchdog-next now.
> > 
> Hi Wim,
> 
> looks like Hans' patches are all in your tree, so I assume I don't have
> to take anything through my hwmon tree. Please let me know if I got that
> wrong.

All is in my tree indeed. So you don't need to do anything on your side.

Kind regards,
Wim.


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors•org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  reply	other threads:[~2012-05-29 17:24 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 [this message]
2012-06-01 13:37     ` Hans de Goede
2012-06-01 14:06       ` Jean Delvare
2012-06-01 15:25         ` Guenter Roeck
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=20120529172439.GY3074@spo001.leaseweb.com \
    --to=wim@iguana$(echo .)be \
    --cc=guenter.roeck@ericsson$(echo .)com \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux-watchdog@vger$(echo .)kernel.org \
    --cc=lm-sensors@lm-sensors$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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