linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Marton Balint <cus@fazekas.hu>,
	linux-media@vger.kernel.org
Subject: Re: linux-next: Tree for April 9
Date: Sat, 11 Apr 2009 08:09:53 -0300	[thread overview]
Message-ID: <20090411080953.0c22cf4e@pedra.chehab.org> (raw)
In-Reply-To: <20090410231158.33b85dc1.akpm@linux-foundation.org>

On Fri, 10 Apr 2009 23:11:58 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:

> On Thu, 9 Apr 2009 16:33:05 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> > I have created today's linux-next tree at
> > git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
> 
> It has a link failure with i386 allmodconfig due to missing __divdi3.
> 
> It's due to this statement in drivers/media/video/cx88/cx88-dsp.c's
> int_goertzel():
> 
>         return (u32)(((s64)s_prev2*s_prev2 + (s64)s_prev*s_prev -
>                       (s64)coeff*s_prev2*s_prev/32768)/N/N);
> 
> that gem will need to be converted to use div64() or similar, please.

Updated to use do_div().


Cheers,
Mauro

  reply	other threads:[~2009-04-11 11:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09  6:33 linux-next: Tree for April 9 Stephen Rothwell
2009-04-09 10:08 ` Next April 9 : x86 allmodconfig media/video/cx88 build break Sachin Sant
2009-04-09 10:28   ` Mauro Carvalho Chehab
2009-04-09 15:51 ` [CFQ/OOPS] rb_erase with April 9 next tree Sachin Sant
2009-04-09 17:29   ` Jens Axboe
2009-04-09 17:44     ` Jens Axboe
2009-04-10  6:40       ` Sachin Sant
2009-04-11  6:11 ` linux-next: Tree for April 9 Andrew Morton
2009-04-11 11:09   ` Mauro Carvalho Chehab [this message]
2009-04-11 12:05     ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2010-04-09  3:34 Stephen Rothwell

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=20090411080953.0c22cf4e@pedra.chehab.org \
    --to=mchehab@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=cus@fazekas.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).