From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: netdev@vger.kernel.org, David Miller <davem@davemloft.net>
Cc: linux-sh@vger.kernel.org
Subject: Re: [PATCH 2/2] sh_eth: fix WARNING in dma_free_coherent()
Date: Fri, 30 Oct 2015 23:47:18 +0300 [thread overview]
Message-ID: <5633D756.1030204@cogentembedded.com> (raw)
In-Reply-To: <5632A78C.4090807@cogentembedded.com>
Hello.
On 10/30/2015 02:11 AM, Sergei Shtylyov wrote:
>> Iff the first dma_alloc_coherent() call fails in sh_eth_ring_init(), the
>> following is printed to the kernel console:
>>
>> WARNING: CPU: 0 PID: 1 at drivers/base/dma-mapping.c:334
>> dma_common_free_remap+0x48/0x6c()
>
> Oops, I got the function name wrong in the subject. David, can you fix
> this while applying or should I repost?
I guess I'll repost (forgot to CC Dave anyway)...
MBR, Sergei
prev parent reply other threads:[~2015-10-30 20:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 21:50 [PATCH 0/2] sh_eth: fix bugs in sh_eth_ring_init() Sergei Shtylyov
2015-10-29 21:51 ` [PATCH 1/2] sh_eth: fix uninitialized arrays " Sergei Shtylyov
2015-10-29 21:52 ` [PATCH 2/2] sh_eth: fix WARNING in dma_free_coherent() Sergei Shtylyov
2015-10-29 23:11 ` Sergei Shtylyov
2015-10-30 20:47 ` Sergei Shtylyov [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=5633D756.1030204@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=davem@davemloft.net \
--cc=linux-sh@vger.kernel.org \
--cc=netdev@vger.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).