From: Vladimir Murzin <vladimir.murzin@arm.com>
To: Joerg Roedel <jroedel@suse.de>
Cc: "Szemző András" <sza@esh.hu>,
"Mark Rutland" <mark.rutland@arm.com>,
alexandre.torgue@st.com,
"Yoshinori Sato" <ysato@users.sourceforge.jp>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux@armlinux.org.uk, "Michal Nazarewicz" <mina86@mina86.com>,
linux-kernel@vger.kernel.org,
"Christian Borntraeger" <borntraeger@de.ibm.com>,
"Doug Ledford" <dledford@redhat.com>,
"Rich Felker" <dalias@libc.org>,
"Alan Stern" <stern@rowland.harvard.edu>,
kbuild-all@01.org, benjamin.gaignard@linaro.org,
"Rob Herring" <robh+dt@kernel.org>,
akpm@linux-foundation.org, "Roger Quadros" <rogerq@ti.com>,
robin.murphy@arm.com, linux-arm-kernel@lists.infradead.org,
"Marek Szyprowski" <m.szyprowski@samsung.com>
Subject: Re: [PATCH v3 0/7] ARM: Fix dma_alloc_coherent() and friends for NOMMU
Date: Wed, 19 Apr 2017 15:20:56 +0100 [thread overview]
Message-ID: <73e1eed0-9d21-6d36-d596-3ca40eb24075@arm.com> (raw)
In-Reply-To: <20170419115658.GD5077@suse.de>
On 19/04/17 12:56, Joerg Roedel wrote:
> On Tue, Apr 18, 2017 at 01:51:35PM +0100, Vladimir Murzin wrote:
>> FYI, nothing has changed since last "ping" - András and Alexandre are still
>> dependant on this series to safely enable DMA on their platforms. It is really
>> scary that these patches do not move forward even though they are supposed to
>> fix the real issue :(
>
> That's probably because you didn't include all relevant people in this
> post. I think patches the patches for dma-noop.c should go through
> Andrew Morton.
>
Thanks for suggestion, Joerg! Andrew is already in the loop.
I'm wondering if there is better way/tool to get relevant people except
get_maintainer.pl?
./scripts/get_maintainer.pl -f lib/dma-noop.c
Bart Van Assche <bart.vanassche@sandisk.com> (commit_signer:3/3=100%,authored:2/3=67%,added_lines:2/7=29%,removed_lines:2/6=33%)
Vineet Gupta <vgupta@synopsys.com> (commit_signer:2/3=67%)
Robin Murphy <robin.murphy@arm.com> (commit_signer:2/3=67%)
Doug Ledford <dledford@redhat.com> (commit_signer:2/3=67%)
Joerg Roedel <jroedel@suse.de> (commit_signer:2/3=67%)
Krzysztof Kozlowski <krzk@kernel.org> (authored:1/3=33%,added_lines:5/7=71%,removed_lines:4/6=67%)
linux-kernel@vger.kernel.org (open list)
./scripts/get_maintainer.pl -f drivers/base/dma-coherent.c
Greg Kroah-Hartman <gregkh@linuxfoundation.org> (supporter:DRIVER CORE, KOBJECTS, DEBUGFS AND SYSFS)
linux-kernel@vger.kernel.org (open list)
Cheers
Vladimir
>
>
> Joerg
>
>
next prev parent reply other threads:[~2017-04-19 14:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 9:23 Vladimir Murzin
2017-03-10 9:23 ` [PATCH v3 1/7] dma: Take into account dma_pfn_offset Vladimir Murzin
2017-03-10 9:23 ` [PATCH v3 2/7] dma: Add simple dma_noop_mmap Vladimir Murzin
2017-03-10 9:23 ` [PATCH v3 3/7] drivers: dma-coherent: Account dma_pfn_offset when used with device tree Vladimir Murzin
2017-03-10 9:23 ` [PATCH v3 4/7] drivers: dma-coherent: Introduce default DMA pool Vladimir Murzin
2017-03-10 9:23 ` [PATCH v3 5/7] ARM: NOMMU: Introduce dma operations for noMMU Vladimir Murzin
2017-04-19 10:10 ` Arnd Bergmann
2017-04-19 14:12 ` Vladimir Murzin
2017-03-10 9:23 ` [PATCH v3 6/7] ARM: NOMMU: Set ARM_DMA_MEM_BUFFERABLE for M-class cpus Vladimir Murzin
2017-04-19 10:02 ` Arnd Bergmann
2017-04-19 14:10 ` Vladimir Murzin
2017-04-21 22:12 ` Arnd Bergmann
2017-03-10 9:23 ` [PATCH v3 7/7] ARM: dma-mapping: Remove traces of NOMMU code Vladimir Murzin
2017-04-19 9:56 ` Arnd Bergmann
2017-04-19 14:11 ` Vladimir Murzin
2017-03-16 9:03 ` [PATCH v3 0/7] ARM: Fix dma_alloc_coherent() and friends for NOMMU Vladimir Murzin
2017-03-22 12:23 ` Szemző András
2017-03-23 9:26 ` Vladimir Murzin
2017-03-29 8:17 ` Vladimir Murzin
2017-04-18 12:51 ` Vladimir Murzin
2017-04-19 11:56 ` Joerg Roedel
2017-04-19 14:20 ` Vladimir Murzin [this message]
2017-05-11 14:44 ` Benjamin Gaignard
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=73e1eed0-9d21-6d36-d596-3ca40eb24075@arm.com \
--to=vladimir.murzin@arm.com \
--cc=akpm@linux-foundation.org \
--cc=alexandre.torgue@st.com \
--cc=benjamin.gaignard@linaro.org \
--cc=borntraeger@de.ibm.com \
--cc=dalias@libc.org \
--cc=dledford@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jroedel@suse.de \
--cc=kbuild-all@01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=mark.rutland@arm.com \
--cc=mina86@mina86.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=rogerq@ti.com \
--cc=stern@rowland.harvard.edu \
--cc=sza@esh.hu \
--cc=ysato@users.sourceforge.jp \
/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
all inboxes | Powered by JetHome®