From: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
To: Sudip Mukherjee
<sudipm.mukherjee-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Wim Van Sebroeck <wim-IQzOog9fTRqzQB+pC5nmwQ@public.gmane.org>,
Haavard Skinnemoen
<hskinnemoen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Hans-Christian Egtvedt
<egtvedt-BrfabpQBY5qlHtIdYg32fQ@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-watchdog-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] watchdog: dw_wdt: dont build for avr32
Date: Tue, 12 Apr 2016 06:07:03 -0700 [thread overview]
Message-ID: <570CF2F7.50206@roeck-us.net> (raw)
In-Reply-To: <1460440303-20640-1-git-send-email-sudipm.mukherjee-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On 04/11/2016 10:51 PM, Sudip Mukherjee wrote:
> The build of avr32 allmodconfig fails with the error:
> ERROR: "__avr32_udiv64" [drivers/watchdog/kempld_wdt.ko] undefined!
>
> Exclude this driver from the build of avr32.
Also, the subject line is wrong.
Guenter
>
> Signed-off-by: Sudip Mukherjee <sudip.mukherjee-4yDnlxn2s6sWdaTGBSpHTA@public.gmane.org>
> ---
>
> avr32 build log is at:
> https://travis-ci.org/sudipm-mukherjee/parport/jobs/122158665
>
> drivers/watchdog/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
> index fb94765..61041ba 100644
> --- a/drivers/watchdog/Kconfig
> +++ b/drivers/watchdog/Kconfig
> @@ -981,7 +981,7 @@ config HP_WATCHDOG
>
> config KEMPLD_WDT
> tristate "Kontron COM Watchdog Timer"
> - depends on MFD_KEMPLD
> + depends on MFD_KEMPLD && !AVR32
> select WATCHDOG_CORE
> help
> Support for the PLD watchdog on some Kontron ETX and COMexpress
>
WARNING: multiple messages have this Message-ID (diff)
From: Guenter Roeck <linux@roeck-us.net>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Wim Van Sebroeck <wim@iguana.be>,
Haavard Skinnemoen <hskinnemoen@gmail.com>,
Hans-Christian Egtvedt <egtvedt@samfundet.no>
Cc: linux-kernel@vger.kernel.org, kernel-testers@vger.kernel.org,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH] watchdog: dw_wdt: dont build for avr32
Date: Tue, 12 Apr 2016 06:07:03 -0700 [thread overview]
Message-ID: <570CF2F7.50206@roeck-us.net> (raw)
In-Reply-To: <1460440303-20640-1-git-send-email-sudipm.mukherjee@gmail.com>
On 04/11/2016 10:51 PM, Sudip Mukherjee wrote:
> The build of avr32 allmodconfig fails with the error:
> ERROR: "__avr32_udiv64" [drivers/watchdog/kempld_wdt.ko] undefined!
>
> Exclude this driver from the build of avr32.
Also, the subject line is wrong.
Guenter
>
> Signed-off-by: Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>
> ---
>
> avr32 build log is at:
> https://travis-ci.org/sudipm-mukherjee/parport/jobs/122158665
>
> drivers/watchdog/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
> index fb94765..61041ba 100644
> --- a/drivers/watchdog/Kconfig
> +++ b/drivers/watchdog/Kconfig
> @@ -981,7 +981,7 @@ config HP_WATCHDOG
>
> config KEMPLD_WDT
> tristate "Kontron COM Watchdog Timer"
> - depends on MFD_KEMPLD
> + depends on MFD_KEMPLD && !AVR32
> select WATCHDOG_CORE
> help
> Support for the PLD watchdog on some Kontron ETX and COMexpress
>
next prev parent reply other threads:[~2016-04-12 13:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 5:51 [PATCH] watchdog: dw_wdt: dont build for avr32 Sudip Mukherjee
2016-04-12 5:51 ` Sudip Mukherjee
[not found] ` <1460440303-20640-1-git-send-email-sudipm.mukherjee-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-04-12 13:06 ` Guenter Roeck
2016-04-12 13:06 ` Guenter Roeck
[not found] ` <570CF2CB.2050200-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2016-04-12 13:39 ` Sudip Mukherjee
2016-04-12 13:39 ` Sudip Mukherjee
[not found] ` <570CFA90.4060100-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-04-12 14:58 ` Andy Shevchenko
2016-04-12 14:58 ` Andy Shevchenko
2016-04-12 15:29 ` Sudip Mukherjee
[not found] ` <CAHp75VcrmiP0GWR-zCBmqc7zA6uiC4dD8-HDikmWZxyEwXkRLw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-04-12 18:01 ` Guenter Roeck
2016-04-12 18:01 ` Guenter Roeck
[not found] ` <20160412180128.GA6965-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2016-04-12 18:17 ` Andy Shevchenko
2016-04-12 18:17 ` Andy Shevchenko
2016-04-30 18:38 ` Sudip Mukherjee
2016-04-30 18:38 ` Sudip Mukherjee
2016-05-01 0:04 ` Guenter Roeck
2016-05-01 0:04 ` Guenter Roeck
2016-05-01 0:36 ` Guenter Roeck
2016-05-01 0:36 ` Guenter Roeck
[not found] ` <20160501003651.GA28804-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2016-05-01 1:13 ` Guenter Roeck
2016-05-01 1:13 ` Guenter Roeck
2016-05-01 9:04 ` Sudip Mukherjee
[not found] ` <5725C698.1090504-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-05-01 14:09 ` Guenter Roeck
2016-05-01 14:09 ` Guenter Roeck
[not found] ` <57260E10.5050601-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2016-05-01 16:30 ` Sudip Mukherjee
2016-05-01 16:30 ` Sudip Mukherjee
2016-04-12 13:07 ` Guenter Roeck [this message]
2016-04-12 13:07 ` 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=570CF2F7.50206@roeck-us.net \
--to=linux-0h96xk9xttrk1umjsbkqmq@public.gmane.org \
--cc=egtvedt-BrfabpQBY5qlHtIdYg32fQ@public.gmane.org \
--cc=hskinnemoen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-watchdog-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sudipm.mukherjee-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=wim-IQzOog9fTRqzQB+pC5nmwQ@public.gmane.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 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.