public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: guenter.roeck@ericsson.com
Cc: 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, 01 Jun 2012 15:37:55 +0200	[thread overview]
Message-ID: <4FC8C5B3.2060108@redhat.com> (raw)
In-Reply-To: <1338307894.478.68.camel@groeck-laptop>

Hi,

On 05/29/2012 06:11 PM, Guenter Roeck wrote:
> On Thu, 2012-05-24 at 16:54 -0400, Wim Van Sebroeck wrote:
>> Hi Hans,
>>
>>> 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.

Right, the sch56xx watchdog code conversion to the watchcore depended on
some pending watchdag core changes, so it seemed sensible to get them all
in though Wim's tree. Sorry if that caused any confusion.

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 :)

Thanks & Regards,

Hans

  parent reply	other threads:[~2012-06-01 13:38 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     ` Hans de Goede [this message]
2012-06-01 14:06       ` [lm-sensors] " 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=4FC8C5B3.2060108@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=guenter.roeck@ericsson.com \
    --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