netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: yuehaibing@huawei.com
Cc: Ariel.Elior@cavium.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, everest-linux-l2@cavium.com
Subject: Re: [PATCH net-next] qed: use dma_zalloc_coherent instead of allocator/memset
Date: Mon, 04 Jun 2018 17:28:58 -0400 (EDT)	[thread overview]
Message-ID: <20180604.172858.971130235733681824.davem@davemloft.net> (raw)
In-Reply-To: <20180604131031.24476-1-yuehaibing@huawei.com>

From: YueHaibing <yuehaibing@huawei.com>
Date: Mon, 4 Jun 2018 21:10:31 +0800

> Use dma_zalloc_coherent instead of dma_alloc_coherent
> followed by memset 0.
> 
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>

Applied.

      parent reply	other threads:[~2018-06-04 21:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-04 13:10 [PATCH net-next] qed: use dma_zalloc_coherent instead of allocator/memset YueHaibing
2018-06-04 14:53 ` Tayar, Tomer
2018-06-04 21:28 ` 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=20180604.172858.971130235733681824.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=Ariel.Elior@cavium.com \
    --cc=everest-linux-l2@cavium.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=yuehaibing@huawei.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).