All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karl Mehltretter <kmehltretter@gmail.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: "Sumit Semwal" <sumit.semwal@linaro.org>,
	"Christian König" <christian.koenig@amd.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Jason Gunthorpe" <jgg@nvidia.com>,
	"Rob Clark" <rob.clark@oss.qualcomm.com>,
	"Jianfeng Liu" <liujianfeng1994@gmail.com>,
	"Diederik de Haas" <diederik@cknow-tech.com>,
	"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
	"Vinod Koul" <vkoul@kernel.org>,
	"Bjorn Andersson" <andersson@kernel.org>,
	linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org,
	"Linux kernel regressions list" <regressions@lists.linux.dev>
Subject: Re: [RFC PATCH 0/3] dma-buf: warn-only mode for DMABUF_DEBUG
Date: Mon, 12 Oct 2026 20:51:33 +0200	[thread overview]
Message-ID: <as0r7Q4dHt9gQm_8@gmail.com> (raw)
In-Reply-To: <d1ef135e-1b5d-4656-9229-348c7029efbb@leemhuis.info>

On Mon, Oct 12, 2026 at 10:12:02AM +0100, Thorsten Leemhuis wrote:
> 
> What's the status here given that 7.3 will likely be released in a few
> days? Note, I can see from the discussion that this is a complex problem
> that can't be quickly solved. That's how it is sometimes. But I wonder
> if the current state of things is the best compromise for now or if
> Rob's revert or some other option would be better.
> 

I think reverting my commit 143755bdabaa ("dma-buf: Make DMABUF_DEBUG
default to y on DEBUG_KERNEL kernels") is the best interim solution for
v7.3.

Christian, Sumit, could one of you apply Jianfeng's revert before the
final release?

https://lore.kernel.org/r/20260926022026.10539-1-liujianfeng1994@gmail.com/

Thanks,
Karl

  reply	other threads:[~2026-10-12 18:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05  6:41 [RFC PATCH 0/3] dma-buf: warn-only mode for DMABUF_DEBUG Karl Mehltretter
2026-10-05  6:41 ` [RFC PATCH 1/3] dma-buf: keep the DMA flags in the DMABUF_DEBUG copy Karl Mehltretter
2026-10-09 13:29   ` Christian König
2026-10-05  6:41 ` [RFC PATCH 2/3] dma-buf: add a warn-only mode to DMABUF_DEBUG Karl Mehltretter
2026-10-07 12:02   ` Diederik de Haas
2026-10-09 12:53     ` Jason Gunthorpe
2026-10-09 13:21       ` Christian König
2026-10-09 14:24         ` Jason Gunthorpe
2026-10-09 13:29       ` Diederik de Haas
2026-10-09 13:29         ` Diederik de Haas
2026-10-09 12:42   ` Jason Gunthorpe
2026-10-09 13:18     ` Christian König
2026-10-05  6:41 ` [RFC PATCH 3/3] dma-buf: test the debug scatterlist wrapper Karl Mehltretter
2026-10-12  8:12 ` [RFC PATCH 0/3] dma-buf: warn-only mode for DMABUF_DEBUG Thorsten Leemhuis
2026-10-12 18:51   ` Karl Mehltretter [this message]
2026-10-13 11:47     ` Sumit Semwal
2026-10-13 14:16     ` Sumit Semwal

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=as0r7Q4dHt9gQm_8@gmail.com \
    --to=kmehltretter@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=andersson@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=christian.koenig@amd.com \
    --cc=diederik@cknow-tech.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jgg@nvidia.com \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=liujianfeng1994@gmail.com \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=rob.clark@oss.qualcomm.com \
    --cc=sumit.semwal@linaro.org \
    --cc=vkoul@kernel.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 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.