From: Kalle Valo <kvalo@codeaurora.org>
To: Jared Bents <jared.bents@rockwellcollins.com>
Cc: ath10k@lists.infradead.org
Subject: Re: [PATCH v1 1/1] ath10k: convert kmemdup to dma_alloc_coherent
Date: Fri, 13 Apr 2018 14:35:08 +0300 [thread overview]
Message-ID: <8736zzs5jn.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1522077122-31134-1-git-send-email-jared.bents@rockwellcollins.com> (Jared Bents's message of "Mon, 26 Mar 2018 10:12:02 -0500")
Jared Bents <jared.bents@rockwellcollins.com> writes:
> Update to convert the use of kmemdup to dma_alloc_coherent as
> dma_alloc_coherent will consider DMA region limits such as
> those seen with CONFIG_FSL_PCI && CONFIG_ZONE_DMA32 whereas
> kmemdup does not take those limitations into account.
>
> Signed-off-by: Jared Bents <jared.bents@rockwellcollins.com>
Can you resend and CC linux-wireless, please? Otherwise patchwork won't
see it and hence I won't see it either as I mostly work via patchwork.
https://wireless.wiki.kernel.org/en/users/drivers/ath10k/submittingpatches
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2018-04-13 11:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 15:12 [PATCH v1 1/1] ath10k: convert kmemdup to dma_alloc_coherent Jared Bents
2018-04-13 11:35 ` Kalle Valo [this message]
2018-04-20 15:39 Jared Bents
2018-04-20 15:39 ` Jared Bents
2018-04-21 7:10 ` Kalle Valo
2018-04-21 7:10 ` Kalle Valo
2018-04-23 18:21 ` Jared Bents
2018-04-23 18:21 ` Jared Bents
2018-04-24 7:32 ` Kalle Valo
2018-04-24 7:32 ` Kalle Valo
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=8736zzs5jn.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=jared.bents@rockwellcollins.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.