From: Christoph Hellwig <hch@lst.de>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Christoph Hellwig <hch@lst.de>,
dri-devel@lists.freedesktop.org,
iommu@lists.linux-foundation.org, linaro-mm-sig@lists.linaro.org,
linux-kernel@vger.kernel.org, Robin Murphy <robin.murphy@arm.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
linux-arm-kernel@lists.infradead.org,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: [PATCH v3 02/25] drm: core: fix common struct sg_table related issues
Date: Fri, 8 May 2020 09:16:09 +0200 [thread overview]
Message-ID: <20200508071609.GA31690@lst.de> (raw)
In-Reply-To: <b887c355-14db-ad37-0e93-733ff2249967@samsung.com>
On Fri, May 08, 2020 at 09:12:13AM +0200, Marek Szyprowski wrote:
> Then we would just need one more helper to construct scatterlist, as the
> above two are read-only don't allow to modify scatterlist:
>
> #define for_each_sgtable_sg(sgt, sg, i) \
> for_each_sg(sgt->sgl, sg, sgt->orig_nents, i)
>
> With the above 3 helpers we can probably get rid of all instances of
> sg_table->{nents,orig_nents} from the DRM code. I will prepare patches soon.
Sounds great, thanks!
next prev parent reply other threads:[~2020-05-08 7:16 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200505084308eucas1p1aa040c3ae325a6c7d92f956b1f5aad0d@eucas1p1.samsung.com>
2020-05-05 8:43 ` [PATCH v3 00/25] DRM: fix struct sg_table nents vs. orig_nents misuse Marek Szyprowski
2020-05-05 8:45 ` [PATCH v3 01/25] dma-mapping: add generic helpers for mapping sgtable objects Marek Szyprowski
2020-05-05 8:45 ` [PATCH v3 02/25] drm: core: fix common struct sg_table related issues Marek Szyprowski
2020-05-05 10:15 ` Christoph Hellwig
2020-05-05 10:51 ` Marek Szyprowski
2020-05-05 11:09 ` Christoph Hellwig
2020-05-08 7:12 ` Marek Szyprowski
2020-05-08 7:16 ` Christoph Hellwig [this message]
2020-05-12 9:05 ` Marek Szyprowski
2020-05-05 8:45 ` [PATCH v3 03/25] drm: amdgpu: " Marek Szyprowski
2020-05-05 8:45 ` [PATCH v3 04/25] drm: armada: " Marek Szyprowski
2020-05-05 8:45 ` [PATCH v3 05/25] drm: etnaviv: " Marek Szyprowski
2020-05-05 8:45 ` [PATCH v3 06/25] drm: exynos: " Marek Szyprowski
2020-05-05 8:45 ` [PATCH v3 07/25] drm: i915: " Marek Szyprowski
2020-05-05 8:45 ` [PATCH v3 08/25] drm: lima: " Marek Szyprowski
2020-05-05 8:45 ` [PATCH v3 09/25] drm: msm: " Marek Szyprowski
2020-05-05 8:45 ` [PATCH v3 10/25] drm: panfrost: " Marek Szyprowski
2020-05-11 15:51 ` Steven Price
2020-05-05 8:46 ` [PATCH v3 11/25] drm: radeon: " Marek Szyprowski
2020-05-05 8:46 ` [PATCH v3 12/25] drm: rockchip: " Marek Szyprowski
2020-05-05 8:46 ` [PATCH v3 13/25] drm: tegra: " Marek Szyprowski
2020-05-05 8:46 ` [PATCH v3 14/25] drm: virtio: " Marek Szyprowski
2020-05-05 8:46 ` [PATCH v3 15/25] drm: vmwgfx: " Marek Szyprowski
2020-05-12 0:19 ` [Linux-graphics-maintainer] " Roland Scheidegger
2020-05-05 8:46 ` [PATCH v3 16/25] xen: gntdev: " Marek Szyprowski
2020-05-05 8:46 ` [PATCH v3 17/25] drm: host1x: " Marek Szyprowski
2020-05-05 8:46 ` [PATCH v3 18/25] drm: rcar-du: " Marek Szyprowski
2020-05-05 9:24 ` Geert Uytterhoeven
2020-05-05 8:46 ` [PATCH v3 19/25] dmabuf: " Marek Szyprowski
2020-05-05 8:46 ` [PATCH v3 20/25] staging: ion: " Marek Szyprowski
2020-05-05 8:46 ` [PATCH v3 21/25] staging: tegra-vde: " Marek Szyprowski
2020-05-05 8:46 ` [PATCH v3 22/25] misc: fastrpc: " Marek Szyprowski
2020-05-05 8:46 ` [PATCH v3 23/25] rapidio: " Marek Szyprowski
2020-05-05 8:46 ` [PATCH v3 24/25] samples: vfio-mdev/mbochs: " Marek Szyprowski
2020-05-05 8:46 ` [PATCH v3 25/25] media: pci: fix common ALSA DMA-mapping related codes Marek Szyprowski
2020-05-05 10:22 ` [PATCH v3 01/25] dma-mapping: add generic helpers for mapping sgtable objects Christoph Hellwig
2020-05-05 10:44 ` Marek Szyprowski
2020-05-07 8:47 ` Hans Verkuil
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=20200508071609.GA31690@lst.de \
--to=hch@lst.de \
--cc=airlied@linux.ie \
--cc=b.zolnierkie@samsung.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=robin.murphy@arm.com \
--cc=tzimmermann@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox