From: Tony Lindgren <tony@atomide.com>
To: Hiroshi DOYU <Hiroshi.DOYU@nokia.com>
Cc: premi@ti.com, linux-omap@vger.kernel.org
Subject: Re: [PATCH] OMAP3: iovmm: fix compiler warning
Date: Tue, 22 Sep 2009 14:36:17 -0700 [thread overview]
Message-ID: <20090922213617.GD4919@atomide.com> (raw)
In-Reply-To: <20090918.175434.229727484.Hiroshi.DOYU@nokia.com>
* Hiroshi DOYU <Hiroshi.DOYU@nokia.com> [090918 07:54]:
> Hi Premi,
>
> From: "ext Premi, Sanjeev" <premi@ti.com>
> Subject: RE: [PATCH] OMAP3: iovmm: fix compiler warning
> Date: Fri, 18 Sep 2009 16:40:29 +0200
>
> [...]
>
> > > > > @@ -390,7 +391,7 @@ static void sgtable_fill_vmalloc(struct
> > > > sg_table *sgt, void *_va)
> > > > > }
> > > > >
> > > > > va_end = _va + PAGE_SIZE * i;
> > > > > - flush_cache_vmap(_va, va_end);
> > > > > + flush_cache_vmap((unsigned long) _va, (unsigned long) va_end);
> > > > > }
> > > > >
> > > > > static inline void sgtable_drain_vmalloc(struct sg_table *sgt)
> > > >
> > > > If no need for pointer, what about below?
> > >
> > > I did not check for the usage of sgtable_drain_vmalloc().
> > > Yes. If the void* isn't MUST then, change below is fine.
> > >
> > > ~sanjeev
> >
> > On second look, the need for void* is driven backwards from:
> > pg = vmalloc_to_page(va);
> > In function sgtable_fill_vmalloc().
> >
> > Now we need a typecast from u32 to void*.
> >
> > Shouldn't we go with the original patch itself?
>
> Right, the original is better, then;)
Can you please specify which one (if any) should be queued?
Do you mean http://patchwork.kernel.org/patch/48467/
Tony
next prev parent reply other threads:[~2009-09-22 21:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 8:56 [PATCH] OMAP3: iovmm: fix compiler warning Sanjeev Premi
2009-09-18 9:54 ` Hiroshi DOYU
2009-09-18 10:23 ` Premi, Sanjeev
2009-09-18 14:40 ` Premi, Sanjeev
2009-09-18 14:54 ` Hiroshi DOYU
2009-09-22 21:36 ` Tony Lindgren [this message]
2009-09-23 4:06 ` Premi, Sanjeev
2009-09-23 5:45 ` Hiroshi DOYU
2009-09-23 8:29 ` Premi, Sanjeev
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=20090922213617.GD4919@atomide.com \
--to=tony@atomide.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=premi@ti.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