linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Christoph Hellwig <hch@lst.de>
Cc: John Crispin <john@phrozen.org>, Vinod Koul <vkoul@kernel.org>,
	Dmitry Tarnyagin <dmitry.tarnyagin@lockless.no>,
	Nicolas Ferre <nicolas.ferre@microchip.com>,
	Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
	Felipe Balbi <balbi@kernel.org>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	dmaengine@vger.kernel.org, netdev@vger.kernel.org,
	linux-usb@vger.kernel.org, linux-fbdev@vger.kernel.org,
	alsa-devel@alsa-project.org, iommu@lists.linux-foundation.org
Subject: Re: [alsa-devel] don't pass a NULL struct device to DMA API functions
Date: Fri, 01 Feb 2019 17:18:21 +0100	[thread overview]
Message-ID: <s5hwomj7a9e.wl-tiwai@suse.de> (raw)
In-Reply-To: <20190201160957.GD6532@lst.de>

On Fri, 01 Feb 2019 17:09:57 +0100,
Christoph Hellwig wrote:
> 
> On Fri, Feb 01, 2019 at 02:16:08PM +0100, Takashi Iwai wrote:
> > Actually there are a bunch of ISA sound drivers that still call
> > allocators with NULL device.
> > 
> > The patch below should address it, although it's only compile-tested.
> 
> Oh, I missed these "indirect" calls.  This looks good to me:
> 
> Reviewed-by: Christoph Hellwig <hch@lst.de>

OK, merged this one to for-next branch now as well.


thanks,

Takashi


      reply	other threads:[~2019-02-01 16:18 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-01  8:47 don't pass a NULL struct device to DMA API functions Christoph Hellwig
2019-02-01  8:47 ` [PATCH 01/18] MIPS: lantiq: pass " Christoph Hellwig
2019-02-07 23:29   ` Paul Burton
2019-02-12  7:45     ` Christoph Hellwig
2019-02-12 17:41   ` Paul Burton
2019-02-01  8:47 ` [PATCH 02/18] dmaengine: imx-sdma: " Christoph Hellwig
2019-02-02 10:11   ` Vinod Koul
2019-02-02 17:21     ` Christoph Hellwig
2019-02-01  8:47 ` [PATCH 03/18] net: caif: " Christoph Hellwig
2019-02-01 13:53   ` Robin Murphy
2019-02-01 16:10     ` Christoph Hellwig
2019-02-01  8:47 ` [PATCH 04/18] au1000_eth: " Christoph Hellwig
2019-02-01  8:47 ` [PATCH 05/18] macb_main: " Christoph Hellwig
2019-02-01 13:34   ` Nicolas.Ferre
2019-02-01  8:47 ` [PATCH 06/18] lantiq_etop: " Christoph Hellwig
2019-02-01  8:47 ` [PATCH 07/18] pxa168_eth: " Christoph Hellwig
2019-02-01  8:47 ` [PATCH 08/18] moxart_ether: " Christoph Hellwig
2019-02-01  8:47 ` [PATCH 09/18] meth: " Christoph Hellwig
2019-02-01  8:47 ` [PATCH 10/18] smc911x: " Christoph Hellwig
2019-02-01 14:14   ` Robin Murphy
2019-02-01 16:11     ` Christoph Hellwig
2019-02-01  8:47 ` [PATCH 11/18] parport_ip32: " Christoph Hellwig
2019-02-01  8:47 ` [PATCH 12/18] fotg210-udc: remove a bogus dma_sync_single_for_device call Christoph Hellwig
2019-02-01 13:19   ` Felipe Balbi
2019-02-01 16:10     ` Christoph Hellwig
2019-02-11 13:12       ` Christoph Hellwig
2019-02-11 13:30         ` Felipe Balbi
2019-02-01  8:47 ` [PATCH 13/18] fotg210-udc: pass struct device to DMA API functions Christoph Hellwig
2019-02-01 13:20   ` Felipe Balbi
2019-02-01  8:47 ` [PATCH 14/18] da8xx-fb: " Christoph Hellwig
2019-02-01  8:47 ` [PATCH 15/18] gbefb: switch to managed version of the DMA allocator Christoph Hellwig
2019-02-01  8:47 ` [PATCH 16/18] pxa3xx-gcu: pass struct device to dma_mmap_coherent Christoph Hellwig
2019-02-01  8:48 ` [PATCH 17/18] ALSA: hal2: pass struct device to DMA API functions Christoph Hellwig
2019-02-01 13:12   ` [alsa-devel] " Takashi Iwai
2019-02-01 16:09     ` Christoph Hellwig
2019-02-01 16:17       ` Takashi Iwai
2019-02-01  8:48 ` [PATCH 18/18] ALSA: " Christoph Hellwig
2019-02-01 13:13   ` [alsa-devel] " Takashi Iwai
2019-02-01 13:16 ` [alsa-devel] don't pass a NULL " Takashi Iwai
2019-02-01 16:09   ` Christoph Hellwig
2019-02-01 16:18     ` Takashi Iwai [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=s5hwomj7a9e.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=balbi@kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=dmitry.tarnyagin@lockless.no \
    --cc=hch@lst.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=john@phrozen.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.ferre@microchip.com \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=vkoul@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).