From: Paul Bolle <pebolle@tiscali.nl>
To: Dan Williams <djbw@fb.com>
Cc: Vinod Koul <vinod.koul@intel.com>,
linux-kernel@vger.kernel.org, "dave.jiang" <dave.jiang@intel.com>
Subject: Re: [PATCH] ioatdma: silence GCC warnings
Date: Thu, 18 Jul 2013 13:42:37 +0200 [thread overview]
Message-ID: <1374147757.26384.49.camel@x61.thuisdomein> (raw)
In-Reply-To: <CAA9_cmc9XWCvU=d2qu6rMaV+_sxBeMgrreZWU5ofzAd3dANT9w@mail.gmail.com>
On Wed, 2013-07-17 at 15:39 -0700, Dan Williams wrote:
> On Mon, Jun 17, 2013 at 3:35 AM, Paul Bolle <pebolle@tiscali.nl> wrote:
> Seems this is fixed in gcc as of 4.7.2, but we can make things quieter
> for build testers on older compilers.
Well, I'm currently using
gcc (GCC) 4.7.2 20121109 (Red Hat 4.7.2-8)
as shipped for Fedora 18.
> > diff --git a/drivers/dma/ioat/dma_v3.c b/drivers/dma/ioat/dma_v3.c
> > index ca6ea9b..b5102da 100644
> > --- a/drivers/dma/ioat/dma_v3.c
> > +++ b/drivers/dma/ioat/dma_v3.c
> > @@ -251,7 +251,7 @@ static bool is_bwd_noraid(struct pci_dev *pdev)
> > }
> >
> > static void pq16_set_src(struct ioat_raw_descriptor *desc[3],
> > - dma_addr_t addr, u32 offset, u8 coef, int idx)
> > + dma_addr_t addr, u32 offset, u8 coef, unsigned int idx)
>
> "unsigned int" --> "unsigned"
Fine with me, but it does introduce a second form in this file (it
already uses "unsigned int" a few times).
> > {
> > struct ioat_pq_descriptor *pq = (struct ioat_pq_descriptor *)desc[0];
> > struct ioat_pq16a_descriptor *pq16 =
>
> Just do this hunk as the minimal one line change.
You're right. Just this hunk is enough. I'll try to send a v2 shortly.
Paul Bolle
next prev parent reply other threads:[~2013-07-18 11:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 10:35 Paul Bolle
2013-07-15 9:50 ` Paul Bolle
2013-07-15 9:40 ` Vinod Koul
2013-07-17 22:39 ` Dan Williams
2013-07-18 11:42 ` Paul Bolle [this message]
2013-07-20 18:05 ` [PATCH v2] " Paul Bolle
2013-07-22 15:46 ` Jiang, Dave
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=1374147757.26384.49.camel@x61.thuisdomein \
--to=pebolle@tiscali.nl \
--cc=dave.jiang@intel.com \
--cc=djbw@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vinod.koul@intel.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
all inboxes | Powered by JetHome®