From: David Miller <davem@davemloft.net>
To: tbogendoerfer@suse.de
Cc: ralf@linux-mips.org, linux-mips@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org, hch@lst.de
Subject: Re: [net v3 1/5] net: sgi: ioc3-eth: don't abuse dma_direct_* calls
Date: Mon, 04 Nov 2019 11:30:44 -0800 (PST) [thread overview]
Message-ID: <20191104.113044.1639305550623277715.davem@davemloft.net> (raw)
In-Reply-To: <20191104104515.7066-1-tbogendoerfer@suse.de>
From: Thomas Bogendoerfer <tbogendoerfer@suse.de>
Date: Mon, 4 Nov 2019 11:45:11 +0100
> From: Christoph Hellwig <hch@lst.de>
>
> dma_direct_ is a low-level API that must never be used by drivers
> directly. Switch to use the proper DMA API instead.
>
> Fixes: ed870f6a7aa2 ("net: sgi: ioc3-eth: use dma-direct for dma allocations")
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> Signed-off-by: Thomas Bogendoerfer <tbogendoerfer@suse.de>
Series applied to net-next.
Please provide a proper "[PATCH v3 0/5] ..." header posting next time when you
post a patch series.
Thank you.
prev parent reply other threads:[~2019-11-04 19:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 10:45 [net v3 1/5] net: sgi: ioc3-eth: don't abuse dma_direct_* calls Thomas Bogendoerfer
2019-11-04 10:45 ` [net v3 2/5] net: sgi: ioc3-eth: fix usage of GFP_* flags Thomas Bogendoerfer
2019-11-04 10:45 ` [net v3 3/5] net: sgi: ioc3-eth: simplify setting the DMA mask Thomas Bogendoerfer
2019-11-04 10:45 ` [net v3 4/5] net: sgi: ioc3-eth: fix setting NETIF_F_HIGHDMA Thomas Bogendoerfer
2019-11-04 10:45 ` [net v3 5/5] net: sgi: ioc3-eth: ensure tx ring is 16k aligned Thomas Bogendoerfer
2019-11-04 19:30 ` 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=20191104.113044.1639305550623277715.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=tbogendoerfer@suse.de \
/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).