From: James Hogan <jhogan@kernel.org>
To: Felix Fietkau <nbd@nbd.name>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH 1/2] MIPS: mm: remove mips_dma_mapping_error
Date: Thu, 1 Feb 2018 11:56:22 +0000 [thread overview]
Message-ID: <20180201115621.GE7637@saruman> (raw)
In-Reply-To: <20171205115034.15078-1-nbd@nbd.name>
[-- Attachment #1: Type: text/plain, Size: 1286 bytes --]
On Tue, Dec 05, 2017 at 12:50:33PM +0100, Felix Fietkau wrote:
> dma_mapping_error() already checks if ops->mapping_error is a null
> pointer
>
> Signed-off-by: Felix Fietkau <nbd@nbd.name>
Thanks, I've already applied this to my 4.16 branch.
Cheers
James
> ---
> arch/mips/mm/dma-default.c | 6 ------
> 1 file changed, 6 deletions(-)
>
> diff --git a/arch/mips/mm/dma-default.c b/arch/mips/mm/dma-default.c
> index e3e94d05f0fd..1af0cd90cc34 100644
> --- a/arch/mips/mm/dma-default.c
> +++ b/arch/mips/mm/dma-default.c
> @@ -373,11 +373,6 @@ static void mips_dma_sync_sg_for_device(struct device *dev,
> }
> }
>
> -static int mips_dma_mapping_error(struct device *dev, dma_addr_t dma_addr)
> -{
> - return 0;
> -}
> -
> static int mips_dma_supported(struct device *dev, u64 mask)
> {
> return plat_dma_supported(dev, mask);
> @@ -404,7 +399,6 @@ static const struct dma_map_ops mips_default_dma_map_ops = {
> .sync_single_for_device = mips_dma_sync_single_for_device,
> .sync_sg_for_cpu = mips_dma_sync_sg_for_cpu,
> .sync_sg_for_device = mips_dma_sync_sg_for_device,
> - .mapping_error = mips_dma_mapping_error,
> .dma_supported = mips_dma_supported,
> .cache_sync = mips_dma_cache_sync,
> };
> --
> 2.14.2
>
>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-02-01 11:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 11:50 [PATCH 1/2] MIPS: mm: remove mips_dma_mapping_error Felix Fietkau
2017-12-05 11:50 ` [PATCH 2/2] MIPS: mm: remove no-op dma_map_ops where possible Felix Fietkau
2018-02-01 11:56 ` James Hogan [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=20180201115621.GE7637@saruman \
--to=jhogan@kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=nbd@nbd.name \
/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