[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75Vd28EChCHs0YTKrF_31OsEzJcgX8XFRwMmy9WGOeukTMg@mail.gmail.com>
Date: Tue, 12 Apr 2016 21:17:43 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Guenter Roeck <linux@...ck-us.net>
Cc: Sudip Mukherjee <sudipm.mukherjee@...il.com>,
Wim Van Sebroeck <wim@...ana.be>,
Haavard Skinnemoen <hskinnemoen@...il.com>,
Hans-Christian Egtvedt <egtvedt@...fundet.no>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
kernel-testers@...r.kernel.org, linux-watchdog@...r.kernel.org
Subject: Re: [PATCH] watchdog: dw_wdt: dont build for avr32
On Tue, Apr 12, 2016 at 9:01 PM, Guenter Roeck <linux@...ck-us.net> wrote:
> On Tue, Apr 12, 2016 at 05:58:20PM +0300, Andy Shevchenko wrote:
>> On Tue, Apr 12, 2016 at 4:39 PM, Sudip Mukherjee
>> <sudipm.mukherjee@...il.com> wrote:
>> > On Tuesday 12 April 2016 06:36 PM, Guenter Roeck wrote:
>> >>
> Sorry, I am missing something. do_div() should work fine with any 32 bit value
> as divisor, no matter what that value is. Why does it fail here ? And why does
> it work if I pass 0x1fffff as second parameter to do_div() directly ?
Perhaps compare assembly code in both cases?
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists