From: David Miller <davem@davemloft.net>
To: Alexey.Brodkin@synopsys.com
Cc: netdev@vger.kernel.org, andy.shevchenko@gmail.com,
romieu@fr.zoreil.com, joe@perches.com,
Vineet.Gupta1@synopsys.com, Mischa.Jonker@synopsys.com,
arnd@arndb.de, grant.likely@linaro.org, rob.herring@calxeda.com,
paul.gortmaker@windriver.com, linux-kernel@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org, florian@openwrt.org,
david.laight@aculab.com
Subject: Re: [PATCH] arc_emac: fix compile-time errors & warnings on PPC64
Date: Wed, 26 Jun 2013 01:36:11 -0700 (PDT) [thread overview]
Message-ID: <20130626.013611.177497936507567378.davem@davemloft.net> (raw)
In-Reply-To: <1372232966-11507-1-git-send-email-abrodkin@synopsys.com>
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Date: Wed, 26 Jun 2013 11:49:26 +0400
> As reported by "kbuild test robot" there were some errors and warnings
> on attempt to build kernel with "make ARCH=powerpc allmodconfig".
>
> And this patch addresses both errors and warnings.
> Below is a list of introduced changes:
> 1. Fix compile-time errors (misspellings in "dma_unmap_single") on PPC.
> 2. Use DMA address instead of "skb->data" as a pointer to data buffer.
> This fixed warnings on pointer to int conversion on 64-bit systems.
> 3. Re-implemented initial allocation of Rx buffers in "arc_emac_open" in
> the same way they're re-allocated during operation (receiving packets).
> So once again DMA address could be used instead of "skb->data".
> 4. Explicitly use EMAC_BUFFER_SIZE for Rx buffers allocation.
>
> Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
Applied.
prev parent reply other threads:[~2013-06-26 8:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 7:49 [PATCH] arc_emac: fix compile-time errors & warnings on PPC64 Alexey Brodkin
2013-06-26 8:36 ` David Miller [this message]
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=20130626.013611.177497936507567378.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Alexey.Brodkin@synopsys.com \
--cc=Mischa.Jonker@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@arndb.de \
--cc=david.laight@aculab.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=florian@openwrt.org \
--cc=grant.likely@linaro.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=rob.herring@calxeda.com \
--cc=romieu@fr.zoreil.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).