kernel-testers.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
	Wim Van Sebroeck <wim@iguana.be>,
	Haavard Skinnemoen <hskinnemoen@gmail.com>,
	Hans-Christian Egtvedt <egtvedt@samfundet.no>,
	"linux-kernel@vger.kernel.org" <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 20:59:23 +0530	[thread overview]
Message-ID: <570D1453.9020005@gmail.com> (raw)
In-Reply-To: <CAHp75VcrmiP0GWR-zCBmqc7zA6uiC4dD8-HDikmWZxyEwXkRLw@mail.gmail.com>

On Tuesday 12 April 2016 08:28 PM, Andy Shevchenko wrote:
> On Tue, Apr 12, 2016 at 4:39 PM, Sudip Mukherjee
> <sudipm.mukherjee@gmail.com> wrote:
>> On Tuesday 12 April 2016 06:36 PM, Guenter Roeck wrote:
>>>
>>> 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!
>>>>
>>> This means there is a direct 64 bit divide operation in the driver,
>>> which we should identify and fix.
>
> This driver will quite likely never be used on AVR32. Do we need to
> fix this due to some other architectures?

I have not seen failure in the architecture builds I monitor. And since 
no one reported anything so I guess its only avr32.

regards
sudip

  reply	other threads:[~2016-04-12 15:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-12  5:51 [PATCH] watchdog: dw_wdt: dont build for avr32 Sudip Mukherjee
     [not found] ` <1460440303-20640-1-git-send-email-sudipm.mukherjee-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-04-12 13:06   ` Guenter Roeck
     [not found]     ` <570CF2CB.2050200-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
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 15:29             ` Sudip Mukherjee [this message]
     [not found]             ` <CAHp75VcrmiP0GWR-zCBmqc7zA6uiC4dD8-HDikmWZxyEwXkRLw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-04-12 18:01               ` Guenter Roeck
     [not found]                 ` <20160412180128.GA6965-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2016-04-12 18:17                   ` Andy Shevchenko
2016-04-30 18:38                   ` Sudip Mukherjee
2016-05-01  0:04                     ` 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  9:04                           ` Sudip Mukherjee
     [not found]                             ` <5725C698.1090504-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-05-01 14:09                               ` Guenter Roeck
     [not found]                                 ` <57260E10.5050601-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2016-05-01 16:30                                   ` Sudip Mukherjee
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=570D1453.9020005@gmail.com \
    --to=sudipm.mukherjee@gmail.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=egtvedt@samfundet.no \
    --cc=hskinnemoen@gmail.com \
    --cc=kernel-testers@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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;
as well as URLs for NNTP newsgroup(s).