public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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>
Subject: Re: [PATCH v2 00/21] DRM: fix struct sg_table nents vs. orig_nents misuse
Date: Mon, 4 May 2020 15:11:10 +0200	[thread overview]
Message-ID: <20200504131110.GA18918@lst.de> (raw)
In-Reply-To: <b257279c-4138-b28e-584d-92bd15571ae1@samsung.com>

On Mon, May 04, 2020 at 03:05:30PM +0200, Marek Szyprowski wrote:
> Hi Christoph,
> 
> On 04.05.2020 14:52, Christoph Hellwig wrote:
> > On Mon, May 04, 2020 at 02:50:17PM +0200, Marek Szyprowski wrote:
> >> v2:
> >> - dropped most of the changes to drm/i915
> >> - added fixes for rcar-du, xen, media and ion
> >> - fixed a few issues pointed by kbuild test robot
> >> - added wide cc: list for each patch
> > Didn't you plan to add dma_map_sgbuf and co helper?
> 
> Yes, I have a followup patches for that, but I wanted to fix the 
> existing code in the first step. Then I wanted to send a wrappers and 
> their application. Do you think I should do everything at once, in one 
> patchset?

That would be my preference.  The helpers should be mostly trivial
wrappers, so they can easily backported, and they force passing of the
correct parameters.  So I don't really see a need to fix up all the 20+
places up first just to convert them to the proper API a little later.

  reply	other threads:[~2020-05-04 13:11 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200504125032eucas1p2eeaf22690e6b557d69c834cc9dd75855@eucas1p2.samsung.com>
2020-05-04 12:50 ` [PATCH v2 00/21] DRM: fix struct sg_table nents vs. orig_nents misuse Marek Szyprowski
2020-05-04 12:52   ` Christoph Hellwig
2020-05-04 13:05     ` Marek Szyprowski
2020-05-04 13:11       ` Christoph Hellwig [this message]
2020-05-04 12:53   ` [PATCH v2 01/21] drm: core: fix " Marek Szyprowski
2020-05-04 12:53     ` [PATCH v2 02/21] drm: amdgpu: " Marek Szyprowski
2020-05-04 12:53     ` [PATCH v2 03/21] drm: armada: " Marek Szyprowski
2020-05-04 12:53     ` [PATCH v2 04/21] drm: etnaviv: " Marek Szyprowski
2020-05-04 12:53     ` [PATCH v2 05/21] drm: exynos: " Marek Szyprowski
2020-05-04 12:53     ` [PATCH v2 06/21] drm: i915: fix sg_table nents vs. orig_nents misuse for dmabuf objects Marek Szyprowski
2020-05-04 12:53     ` [PATCH v2 07/21] drm: lima: fix sg_table nents vs. orig_nents misuse Marek Szyprowski
2020-05-04 12:53     ` [PATCH v2 08/21] drm: msm: " Marek Szyprowski
2020-05-04 12:53     ` [PATCH v2 09/21] drm: panfrost: " Marek Szyprowski
2020-05-04 13:27       ` Steven Price
2020-05-04 12:53     ` [PATCH v2 10/21] drm: radeon: " Marek Szyprowski
2020-05-04 12:53     ` [PATCH v2 11/21] drm: rockchip: " Marek Szyprowski
2020-05-04 12:53     ` [PATCH v2 12/21] drm: tegra: " Marek Szyprowski
2020-05-04 12:53     ` [PATCH v2 13/21] drm: virtio: " Marek Szyprowski
2020-05-04 12:53     ` [PATCH v2 14/21] drm: vmwgfx: " Marek Szyprowski
2020-05-04 12:53     ` [PATCH v2 15/21] drm: xen: " Marek Szyprowski
2020-05-04 12:53     ` [PATCH v2 16/21] drm: host1x: " Marek Szyprowski
2020-05-04 12:53     ` [PATCH v2 17/21] drm: rcar-du: " Marek Szyprowski
2020-05-04 12:53     ` [PATCH v2 18/21] xen: gntdev: " Marek Szyprowski
2020-05-04 12:53     ` [PATCH v2 19/21] dmabuf: " Marek Szyprowski
2020-05-04 12:53     ` [PATCH v2 20/21] media: pci: fix common ALSA DMA-mapping related code Marek Szyprowski
2020-05-04 12:53     ` [PATCH v2 21/21] staging: ion: fix sg_table nents vs. orig_nents misuse Marek Szyprowski

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=20200504131110.GA18918@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=robin.murphy@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: 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