linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dma: mv_xor: Silence a bunch of LPAE-related warnings
Date: Wed, 12 Feb 2014 13:58:33 -0800	[thread overview]
Message-ID: <20140212215833.GA29365@quad.lixom.net> (raw)
In-Reply-To: <CAPcyv4gWJA7Cv39pxtuOqj0RyivODNuae7Q0Ku27RQO8=M3HbQ@mail.gmail.com>

On Tue, Feb 04, 2014 at 10:58:31AM -0800, Dan Williams wrote:
> On Tue, Feb 4, 2014 at 10:57 AM, Dan Williams <dan.j.williams@intel.com> wrote:
> > On Tue, Feb 4, 2014 at 10:30 AM, Olof Johansson <olof@lixom.net> wrote:
> >> On Tue, Feb 4, 2014 at 9:00 AM, Jason Cooper <jason@lakedaemon.net> wrote:
> >>> On Tue, Feb 04, 2014 at 10:53:29AM +0530, Vinod Koul wrote:
> >>>> On Mon, Feb 03, 2014 at 05:13:23PM -0800, Olof Johansson wrote:
> >>>> > Enabling some of the mvebu platforms in the multiplatform config for ARM
> >>>> > enabled these drivers, which also triggered a bunch of warnings when LPAE
> >>>> > is enabled (thus making phys_addr_t 64-bit).
> >>>> >
> >>>> > Most changes are switching printk formats, but also a bit of changes to what
> >>>> > used to be array-based pointer arithmetic that could just be done with the
> >>>> > address types instead.
> >>>> >
> >>>> > The warnings were:
> >>>> >
> >>>> > drivers/dma/mv_xor.c: In function 'mv_xor_tx_submit':
> >>>> > drivers/dma/mv_xor.c:500:3: warning: format '%x' expects argument of type
> >>>> >     'unsigned int', but argument 4 has type 'dma_addr_t' [-Wformat]
> >>>> > drivers/dma/mv_xor.c: In function 'mv_xor_alloc_chan_resources':
> >>>> > drivers/dma/mv_xor.c:553:13: warning: cast to pointer from integer of
> >>>> >     different size [-Wint-to-pointer-cast]
> >>>> > drivers/dma/mv_xor.c:555:4: warning: cast from pointer to integer of
> >>>> >     different size [-Wpointer-to-int-cast]
> >>>> > drivers/dma/mv_xor.c: In function 'mv_xor_prep_dma_memcpy':
> >>>> > drivers/dma/mv_xor.c:584:2: warning: format '%x' expects argument of type
> >>>> >     'unsigned int', but argument 5 has type 'dma_addr_t' [-Wformat]
> >>>> > drivers/dma/mv_xor.c:584:2: warning: format '%x' expects argument of type
> >>>> >     'unsigned int', but argument 6 has type 'dma_addr_t' [-Wformat]
> >>>> > drivers/dma/mv_xor.c: In function 'mv_xor_prep_dma_xor':
> >>>> > drivers/dma/mv_xor.c:628:2: warning: format '%u' expects argument of type
> >>>> >     'unsigned int', but argument 7 has type 'dma_addr_t' [-Wformat]
> >>>> >
> >>>> > Signed-off-by: Olof Johansson <olof@lixom.net>
> >>>> Acked-by: Vinod Koul <vinod.koul@intel.com>
> >>>
> >>> Olof, would you like me to queue it up?  Or do you want to take it
> >>> directly?
> >>>
> >>> Acked-by: Jason Cooper <jason@lakedaemon.net>
> >>
> >> I'm confused. I sent the patch to the drivers/dma maintainers and they
> >> just acked it without asking me to pick it up myself.
> >>
> >> Vinod, did you ack it for me to pick it up, or for some other reason?
> >> If you don't want to take it through your tree I'll be happy to take
> >> it through arm-soc, just looking to clarify.
> >>
> >> (Jason, I can apply it directly)
> >
> > Vinod will correct me if I am wrong, but I take his acks to mean "yup,
> > take it through your tree".  For this specific problem I thought we
> > had a comprehensive fix pending from Joe Perches to add a new %pX
> > format specifier for dma addresses?
> 
> Never mind... that's what you are using.  Sorry for the noise.

Yep. Applied now, btw.


-Olof

  reply	other threads:[~2014-02-12 21:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-04  1:13 [PATCH] dma: mv_xor: Silence a bunch of LPAE-related warnings Olof Johansson
2014-02-04  5:23 ` Vinod Koul
2014-02-04 17:00   ` Jason Cooper
2014-02-04 18:30     ` Olof Johansson
2014-02-04 18:57       ` Dan Williams
2014-02-04 18:58         ` Dan Williams
2014-02-12 21:58           ` Olof Johansson [this message]
2014-02-04 21:56         ` Olof Johansson

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=20140212215833.GA29365@quad.lixom.net \
    --to=olof@lixom.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).