From: Will Deacon <will@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: iommu@lists.linux-foundation.org, Will Deacon <will@kernel.org>,
Claire Chang <tientzu@chromium.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Christoph Hellwig <hch@lst.de>, Rob Herring <robh+dt@kernel.org>,
Robin Murphy <robin.murphy@arm.com>
Subject: [PATCH v2 0/2] Don't fail device probing due to of_dma_set_restricted_buffer()
Date: Mon, 16 Aug 2021 14:26:15 +0100 [thread overview]
Message-ID: <20210816132618.11707-1-will@kernel.org> (raw)
Hi all,
This is v2 of the patch I previously posted here:
https://lore.kernel.org/r/20210805094736.902-1-will@kernel.org
Changes since v1 are:
* Move of_dma_set_restricted_buffer() into of/device.c (Rob)
* Use IS_ENABLED() instead of 'static inline' stub (Rob)
This applies on Konrad's devel/for-linus-5.15 branch in swiotlb.git
Cheers,
Will
Cc: Claire Chang <tientzu@chromium.org>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: Robin Murphy <robin.murphy@arm.com>
--->8
Will Deacon (2):
of: Move of_dma_set_restricted_buffer() into device.c
of: restricted dma: Don't fail device probe on rmem init failure
drivers/of/address.c | 33 ---------------------------------
drivers/of/device.c | 39 ++++++++++++++++++++++++++++++++++++++-
drivers/of/of_private.h | 7 -------
3 files changed, 38 insertions(+), 41 deletions(-)
--
2.33.0.rc1.237.g0d66db33f3-goog
next reply other threads:[~2021-08-16 13:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 13:26 Will Deacon [this message]
2021-08-16 13:26 ` [PATCH v2 1/2] of: Move of_dma_set_restricted_buffer() into device.c Will Deacon
2021-08-16 13:26 ` [PATCH v2 2/2] of: restricted dma: Don't fail device probe on rmem init failure Will Deacon
2021-08-16 19:40 ` [PATCH v2 0/2] Don't fail device probing due to of_dma_set_restricted_buffer() Rob Herring
2021-08-23 10:47 ` Konrad Rzeszutek Wilk
2021-08-23 12:40 ` Will Deacon
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=20210816132618.11707-1-will@kernel.org \
--to=will@kernel.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=tientzu@chromium.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