mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marek Szyprowski <m.szyprowski@samsung.com>
To: iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: Robin Murphy <robin.murphy@arm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Claire Chang <tientzu@chromium.org>,
	Petr Tesarik <petr.tesarik.ext@huawei.com>,
	Nicolas Saenz Julienne <nsaenz@kernel.org>,
	Christoph Hellwig <hch@lst.de>,
	Lucas Stach <l.stach@pengutronix.de>
Subject: Re: [PATCH 0/5] dma-mapping: assorted sashiko.dev fixes
Date: Thu, 5 Nov 2026 09:03:27 +0100	[thread overview]
Message-ID: <286d09f6-0fd6-46be-9290-a7d89af18892@samsung.com> (raw)
In-Reply-To: <20261026095423.966856-1-m.szyprowski@samsung.com>

On 26.10.2026 10:54, Marek Szyprowski wrote:
> This series collects fixes for the DMA-mapping code, developed while
> analyzing issues reported by the sashiko.dev automated review. All
> patches were prepared with LLM assistance and then reviewed manually.
>
> Best regards
> Marek Szyprowski, PhD
> Samsung R&D Institute Poland
>
>
> Marek Szyprowski (5):
>   dma-coherent: serialize reserved memory pool initialization
>   dma: swiotlb: Serialize restricted DMA pool initialization
>   dma: swiotlb: Remove default pool from the pools list on exit
>   dma-pool: release CMA pages on atomic_pool_expand() error path
>   dma-direct: zero memory allocated with DMA_ATTR_NO_KERNEL_MAPPING
Applied patches 1,2 & 4 to dma-mapping-fixes. The remaining two patches
need more work, I will post v2 soon.

Best regards
-- 
Marek Szyprowski, PhD
Samsung R&D Institute Poland


      parent reply	other threads:[~2026-11-05  8:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20261026095434eucas1p29408e916eda327a5e9c83f64b0df4e66@eucas1p2.samsung.com>
2026-10-26  9:54 ` Marek Szyprowski
     [not found]   ` <CGME20261026095434eucas1p1bb0ac7f1e94bcac196fdc97a0f2c9e9f@eucas1p1.samsung.com>
2026-10-26  9:54     ` [PATCH 1/5] dma-coherent: serialize reserved memory pool initialization Marek Szyprowski
     [not found]   ` <CGME20261026095435eucas1p1f2245a6982ef110340685dc66be53590@eucas1p1.samsung.com>
2026-10-26  9:54     ` [PATCH 2/5] dma: swiotlb: Serialize restricted DMA " Marek Szyprowski
     [not found]   ` <CGME20261026095435eucas1p129baa137891d2e9f5408b47afd6c556c@eucas1p1.samsung.com>
2026-10-26  9:54     ` [PATCH 3/5] dma: swiotlb: Remove default pool from the pools list on exit Marek Szyprowski
     [not found]   ` <CGME20261026095436eucas1p295baef3daff27873165c70d6d578c1b6@eucas1p2.samsung.com>
2026-10-26  9:54     ` [PATCH 4/5] dma-pool: release CMA pages on atomic_pool_expand() error path Marek Szyprowski
     [not found]   ` <CGME20261026095436eucas1p1338aced1035d6754d5094555237b6748@eucas1p1.samsung.com>
2026-10-26  9:54     ` [PATCH 5/5] dma-direct: zero memory allocated with DMA_ATTR_NO_KERNEL_MAPPING Marek Szyprowski
2026-11-05  8:03   ` Marek Szyprowski [this message]

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=286d09f6-0fd6-46be-9290-a7d89af18892@samsung.com \
    --to=m.szyprowski@samsung.com \
    --cc=akpm@linux-foundation.org \
    --cc=hch@lst.de \
    --cc=iommu@lists.linux.dev \
    --cc=konrad.wilk@oracle.com \
    --cc=l.stach@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nsaenz@kernel.org \
    --cc=petr.tesarik.ext@huawei.com \
    --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

all inboxes | Powered by JetHome®