From: Mark Brown <broonie@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: [PATCH 5/8] sound: intel/sst: don't pass GFP_DMA32 to dma_alloc_coherent
Date: Wed, 17 Oct 2018 10:55:22 +0100 [thread overview]
Message-ID: <20181017095522.GB24097@sirena.org.uk> (raw)
In-Reply-To: <20181017071900.GA23407@lst.de>
[-- Attachment #1.1: Type: text/plain, Size: 1035 bytes --]
On Wed, Oct 17, 2018 at 09:19:00AM +0200, Christoph Hellwig wrote:
> On Mon, Oct 15, 2018 at 10:58:58AM +0100, Mark Brown wrote:
> > I don't have the patch... in fact, having found it in list archives I
> > see there's also a SPI patch I'll have to go hunting for so I guess I'll
> > apply this one when I find that :( Christoph, please CC maintainers.
> I tend to only add the list as there just are way too many maintainers
> for this sorts of series, and maintainers should read their list anyway.
For several of my subsystems that list is lkml, good luck reliably
getting anything noticed by a specific person by simply posting there!
Even with ASoC alsa-devel is also used by the general ALSA stuff so
there's a lot of noise, especially for things without the ASoC prefix.
I do trawl the lists but it's at best going to be delayed, especially
during busier periods.
The usual thing for things like this is to send individual patches to
specific maintainers (git send-email does the right thing with Cc: in
the commit body).
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2018-10-17 9:55 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-13 15:16 remove bogus GFP_DMA32 flags for dma allocations Christoph Hellwig
2018-10-13 15:16 ` Christoph Hellwig
2018-10-13 15:17 ` [PATCH 1/8] cpufreq: tegra186: don't pass GFP_DMA32 to dma_alloc_coherent Christoph Hellwig
2018-10-13 15:17 ` Christoph Hellwig
2018-10-13 15:17 ` Christoph Hellwig
2018-10-15 7:43 ` Rafael J. Wysocki
2018-10-15 7:43 ` Rafael J. Wysocki
2018-10-15 7:43 ` Rafael J. Wysocki
2018-10-17 7:19 ` Christoph Hellwig
2018-10-17 7:19 ` Christoph Hellwig
2018-10-17 7:19 ` Christoph Hellwig
2018-10-17 7:19 ` Christoph Hellwig
2018-10-17 7:22 ` Rafael J. Wysocki
2018-10-17 7:22 ` Rafael J. Wysocki
2018-10-17 7:22 ` Rafael J. Wysocki
2018-10-13 15:17 ` [PATCH 2/8] firmware: tegra: " Christoph Hellwig
2018-10-13 15:17 ` Christoph Hellwig
2018-10-13 15:17 ` Christoph Hellwig
2018-10-13 15:17 ` [PATCH 3/8] spi: pic32-sqi: " Christoph Hellwig
2018-10-13 15:17 ` Christoph Hellwig
2018-10-17 11:55 ` Applied "spi: pic32-sqi: don't pass GFP_DMA32 to dma_alloc_coherent" to the spi tree Mark Brown
2018-10-17 11:55 ` Mark Brown
2018-10-17 11:55 ` Mark Brown
2018-10-17 11:55 ` Mark Brown
2018-10-13 15:17 ` [PATCH 4/8] sound: hpios: don't pass GFP_DMA32 to dma_alloc_coherent Christoph Hellwig
2018-10-13 15:17 ` Christoph Hellwig
2018-10-13 16:18 ` [alsa-devel] " Takashi Iwai
2018-10-13 16:18 ` Takashi Iwai
2018-10-13 16:18 ` Takashi Iwai
2018-10-13 16:35 ` Christoph Hellwig
2018-10-13 16:35 ` [alsa-devel] " Christoph Hellwig
2018-10-13 16:35 ` Christoph Hellwig
2018-10-13 18:10 ` Takashi Iwai
2018-10-13 18:10 ` Takashi Iwai
2018-10-13 18:10 ` Takashi Iwai
2018-10-13 15:17 ` [PATCH 5/8] sound: intel/sst: " Christoph Hellwig
2018-10-13 15:17 ` Christoph Hellwig
2018-10-13 16:20 ` [alsa-devel] " Takashi Iwai
2018-10-13 16:20 ` Takashi Iwai
2018-10-13 16:20 ` Takashi Iwai
2018-10-14 7:46 ` Takashi Iwai
2018-10-15 9:58 ` Mark Brown
2018-10-17 7:19 ` Christoph Hellwig
2018-10-17 9:55 ` Mark Brown [this message]
2018-10-17 11:54 ` Applied "ASoC: intel: don't pass GFP_DMA32 to dma_alloc_coherent" to the asoc tree Mark Brown
2018-10-17 11:54 ` Mark Brown
2018-10-17 11:54 ` Mark Brown
2018-10-17 11:54 ` Mark Brown
2018-10-17 11:54 ` Mark Brown
2018-10-13 15:17 ` [PATCH 6/8] drm: sti: don't pass GFP_DMA32 to dma_alloc_wc Christoph Hellwig
2018-10-13 15:17 ` Christoph Hellwig
2018-10-15 9:12 ` Benjamin Gaignard
2018-10-15 9:12 ` Benjamin Gaignard
2018-10-16 12:41 ` Benjamin Gaignard
2018-10-16 12:41 ` Benjamin Gaignard
2018-10-16 12:41 ` Benjamin Gaignard
2018-10-17 7:19 ` Christoph Hellwig
2018-10-17 7:19 ` Christoph Hellwig
2018-10-17 7:19 ` Christoph Hellwig
2018-10-18 11:59 ` Benjamin Gaignard
2018-10-18 11:59 ` Benjamin Gaignard
2018-10-18 11:59 ` Benjamin Gaignard
2018-10-13 15:17 ` [PATCH 7/8] media: sti/bdisp: don't pass GFP_DMA32 to dma_alloc_attrs Christoph Hellwig
2018-10-13 15:17 ` Christoph Hellwig
2018-10-15 9:12 ` Benjamin Gaignard
2018-10-15 9:12 ` Benjamin Gaignard
2018-10-17 7:20 ` Christoph Hellwig
2018-10-17 7:20 ` Christoph Hellwig
2018-10-18 12:00 ` Benjamin Gaignard
2018-10-18 12:00 ` Benjamin Gaignard
2018-12-05 10:31 ` Mauro Carvalho Chehab
2018-12-05 10:31 ` Mauro Carvalho Chehab
2018-12-05 10:31 ` Mauro Carvalho Chehab
2018-10-13 15:17 ` [PATCH 8/8] fsl-diu-fb: don't pass GFP_DMA32 to dmam_alloc_coherent Christoph Hellwig
2018-10-13 15:17 ` Christoph Hellwig
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=20181017095522.GB24097@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=hch@lst.de \
--cc=tiwai@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 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.