From: Geert Uytterhoeven <geert@linux-m68k.org>
To: gennarone@gmail.com
Cc: linux-media@vger.kernel.org, Antti Palosaari <crope@iki.fi>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
Linux-Next <linux-next@vger.kernel.org>
Subject: Re: rtl2830: __udivdi3 undefined
Date: Tue, 6 Mar 2012 19:02:02 +0100 [thread overview]
Message-ID: <CAMuHMdVE2m-Q+ikyEE5V9dd9cbqCbCC2+CtnkDhq=UTQg2detQ@mail.gmail.com> (raw)
In-Reply-To: <4F53EA7D.4090402@gmail.com>
On Sun, Mar 4, 2012 at 23:19, Gianluca Gennari <gennarone@gmail.com> wrote:
> Probably the best solution is to use div_u64.
> The following patch fixed the warning on my 32 bit system.
>
> Signed-off-by: Gianluca Gennari <gennarone@gmail.com>
Thanks, that fixes it (div_u64() is do_div() on 32-bit).
Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
> ---
> drivers/media/dvb/frontends/rtl2830.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/media/dvb/frontends/rtl2830.c
> b/drivers/media/dvb/frontends/rtl2830.c
> index f971d94..45196c5 100644
> --- a/drivers/media/dvb/frontends/rtl2830.c
> +++ b/drivers/media/dvb/frontends/rtl2830.c
> @@ -244,7 +244,7 @@ static int rtl2830_init(struct dvb_frontend *fe)
>
> num = priv->cfg.if_dvbt % priv->cfg.xtal;
> num *= 0x400000;
> - num /= priv->cfg.xtal;
> + num = div_u64(num, priv->cfg.xtal);
> num = -num;
> if_ctl = num & 0x3fffff;
> dbg("%s: if_ctl=%08x", __func__, if_ctl);
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2012-03-06 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 21:30 rtl2830: __udivdi3 undefined Geert Uytterhoeven
2012-03-04 22:19 ` Gianluca Gennari
2012-03-06 18:02 ` Geert Uytterhoeven [this message]
2012-03-12 19:58 ` Antti Palosaari
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='CAMuHMdVE2m-Q+ikyEE5V9dd9cbqCbCC2+CtnkDhq=UTQg2detQ@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=crope@iki.fi \
--cc=gennarone@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@redhat.com \
/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).