From: Christoph Hellwig <hch@lst.de> To: Robin Murphy <robin.murphy@arm.com> Cc: hch@lst.de, iommu@lists.linux-foundation.org, m.szyprowski@samsung.com, catalin.marinas@arm.com, will.deacon@arm.com, linux-arm-kernel@lists.infradead.org, rjw@rjwysocki.net, lenb@kernel.org, gregkh@linuxfoundation.org, bhelgaas@google.com, linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/2] Refactor dummy DMA ops Date: Fri, 7 Dec 2018 18:05:19 +0100 [thread overview] Message-ID: <20181207170519.GA26857@lst.de> (raw) In-Reply-To: <cover.1544199754.git.robin.murphy@arm.com> So I'd really prefer if we had a separate dummy.c file, like in my take on your previous patch here: http://git.infradead.org/users/hch/misc.git/commitdiff/e01adddc1733fa414dc16cd22e8f58be9b64a025 http://git.infradead.org/users/hch/misc.git/commitdiff/596bde76e5944a3f4beb8c2769067ca88dda127a Otherwise this looks fine. If you don't minde I'll take your patches, apply the move to a separate file and merge it into the above tree.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de> To: Robin Murphy <robin.murphy@arm.com> Cc: rjw@rjwysocki.net, linux-pci@vger.kernel.org, catalin.marinas@arm.com, will.deacon@arm.com, linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, iommu@lists.linux-foundation.org, gregkh@linuxfoundation.org, bhelgaas@google.com, lenb@kernel.org, hch@lst.de, linux-arm-kernel@lists.infradead.org, m.szyprowski@samsung.com Subject: Re: [PATCH 0/2] Refactor dummy DMA ops Date: Fri, 7 Dec 2018 18:05:19 +0100 [thread overview] Message-ID: <20181207170519.GA26857@lst.de> (raw) In-Reply-To: <cover.1544199754.git.robin.murphy@arm.com> So I'd really prefer if we had a separate dummy.c file, like in my take on your previous patch here: http://git.infradead.org/users/hch/misc.git/commitdiff/e01adddc1733fa414dc16cd22e8f58be9b64a025 http://git.infradead.org/users/hch/misc.git/commitdiff/596bde76e5944a3f4beb8c2769067ca88dda127a Otherwise this looks fine. If you don't minde I'll take your patches, apply the move to a separate file and merge it into the above tree. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-12-07 17:05 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-12-07 16:31 [PATCH 0/2] Refactor dummy DMA ops Robin Murphy 2018-12-07 16:31 ` Robin Murphy [not found] ` <cover.1544199754.git.robin.murphy-5wv7dgnIgG8@public.gmane.org> 2018-12-07 16:31 ` [PATCH 1/2] dma-mapping: Factor out " Robin Murphy 2018-12-07 16:31 ` Robin Murphy 2018-12-07 16:31 ` Robin Murphy 2018-12-07 16:31 ` [PATCH 2/2] ACPI / scan: Refactor _CCA enforcement Robin Murphy 2018-12-07 16:31 ` Robin Murphy 2018-12-11 10:15 ` Rafael J. Wysocki 2018-12-11 10:15 ` Rafael J. Wysocki 2018-12-20 15:08 ` Bjorn Helgaas 2018-12-20 15:08 ` Bjorn Helgaas 2018-12-07 17:05 ` Christoph Hellwig [this message] 2018-12-07 17:05 ` [PATCH 0/2] Refactor dummy DMA ops Christoph Hellwig 2018-12-07 17:35 ` Robin Murphy 2018-12-07 17:35 ` Robin Murphy
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=20181207170519.GA26857@lst.de \ --to=hch@lst.de \ --cc=bhelgaas@google.com \ --cc=catalin.marinas@arm.com \ --cc=gregkh@linuxfoundation.org \ --cc=iommu@lists.linux-foundation.org \ --cc=lenb@kernel.org \ --cc=linux-acpi@vger.kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pci@vger.kernel.org \ --cc=m.szyprowski@samsung.com \ --cc=rjw@rjwysocki.net \ --cc=robin.murphy@arm.com \ --cc=will.deacon@arm.com \ /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: linkBe 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.