linux-watchdog.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Radu Rendec <radu.rendec@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
	linux-watchdog@vger.kernel.org
Subject: [PATCH 0/1] xen_wdt: fix build failure
Date: Mon, 19 Feb 2018 14:38:50 +0000	[thread overview]
Message-ID: <20180219143851.13983-1-radu.rendec@gmail.com> (raw)

Hi Guenter,

I just saw Matteo Croce's email/patch on the i6300esb build failure and
I realized that xen_wdt has the exact same problem. I forgot to add a
dependency on CONFIG_WATCHDOG_CORE for both drivers when I ported them
to use the watchdog core.

This patch is the xen_wdt equivalent of Matteo Croce's patch for
i6300esb.

Thanks!

Radu Rendec (1):
  watchdog: xen_wdt: fix potential build failure

 drivers/watchdog/Kconfig | 1 +
 1 file changed, 1 insertion(+)

-- 
2.13.6

             reply	other threads:[~2018-02-19 14:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-19 14:38 Radu Rendec [this message]
2018-02-19 14:38 ` [PATCH 1/1] watchdog: xen_wdt: fix potential build failure Radu Rendec
2018-02-19 15:48   ` Guenter Roeck

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=20180219143851.13983-1-radu.rendec@gmail.com \
    --to=radu.rendec@gmail.com \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=wim@linux-watchdog.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;
as well as URLs for NNTP newsgroup(s).