From: Angelo Dureghello <angelo@sysam.it>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Vinod Koul <vkoul@kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: linux-next: build warning after merge of the slave-dma tree
Date: Thu, 13 Sep 2018 09:17:38 +0200 [thread overview]
Message-ID: <20180913071738.GA11013@jerusalem> (raw)
In-Reply-To: <20180913122218.0fb31482@canb.auug.org.au>
Hi,
sorry, there was no build-test robot warning anymore about it.
Will fix it in a patch in short.
On Thu, Sep 13, 2018 at 12:22:18PM +1000, Stephen Rothwell wrote:
> Hi Vinod,
>
> After merging the slave-dma tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> drivers/dma/mcf-edma.c: In function 'mcf_edma_filter_fn':
> drivers/dma/mcf-edma.c:296:33: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
> return (mcf_chan->slave_id == (u32)param);
> ^
>
> Introduced by commit
>
> e7a3ff92eaf1 ("dmaengine: fsl-edma: add ColdFire mcf5441x edma support")
>
Regards,
Angelo
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2018-09-13 7:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 2:22 linux-next: build warning after merge of the slave-dma tree Stephen Rothwell
2018-09-13 7:17 ` Angelo Dureghello [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-14 0:00 Stephen Rothwell
2020-02-14 4:41 ` Vinod Koul
2019-08-12 7:14 Stephen Rothwell
2019-08-12 9:14 ` Arnd Bergmann
2019-08-12 9:21 ` Stephen Rothwell
2018-11-26 5:59 Stephen Rothwell
2018-11-26 8:09 ` Vinod Koul
2018-07-04 3:30 Stephen Rothwell
2018-07-04 4:20 ` Vinod
2018-07-05 2:47 ` Stephen Rothwell
2018-07-05 5:01 ` Vinod
2016-06-09 1:18 Stephen Rothwell
2016-06-09 6:04 ` Appana Durga Kedareswara Rao
2015-03-30 6:20 Stephen Rothwell
2015-03-30 6:26 ` Appana Durga Kedareswara Rao
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=20180913071738.GA11013@jerusalem \
--to=angelo@sysam.it \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=vkoul@kernel.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).