mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Honghui  Jiang" <jiang_hh2019@163.com>
To: "Mark Brown" <broonie@kernel.org>
Cc: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Serge Semin" <fancer.lancer@gmail.com>,
	"Brendan Higgins" <brendan.higgins@linux.dev>,
	"David Gow" <david@davidgow.net>,
	"Rae Moar" <raemoar63@gmail.com>,
	linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com
Subject: Re: [PATCH v2 4/4] spi: Add KUnit coverage for DMA mapping error paths
Date: Sat, 15 Aug 2026 01:38:11 +0800 (CST)	[thread overview]
Message-ID: <53943105.8b50.1a0015a531c.Coremail.jiang_hh2019@163.com> (raw)
In-Reply-To: <93950eda-ee8e-4a28-8e3c-707d64c956fe@sirena.org.uk>

On Fri, Aug 14, 2026 at 01:49:50PM +0100, Mark Brown wrote:
> On Fri, Aug 14, 2026 at 03:27:13PM +0300, Andy Shevchenko wrote:
> > This is a stray change.
>
> Well, one of the config changes is.  Clearly spi is critical enough to
> be tested by default!  :P


Thanks, both. I'll drop CONFIG_SPI=y from default.config in v3 and keep
it in all_tests.config.

  reply	other threads:[~2026-08-14 17:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-14  3:14 [PATCH v2 0/4] spi: Fix DMA mapping ownership on partial map failure Honghui Jiang
2026-08-14  3:14 ` [PATCH v2 1/4] " Honghui Jiang
2026-08-14  3:14 ` [PATCH v2 2/4] spi: Move __spi_unmap_msg() before __spi_map_msg() Honghui Jiang
2026-08-14  3:14 ` [PATCH v2 3/4] spi: Clear current DMA devices when unmapping a message Honghui Jiang
2026-08-14  3:14 ` [PATCH v2 4/4] spi: Add KUnit coverage for DMA mapping error paths Honghui Jiang
2026-08-14 12:27   ` Andy Shevchenko
2026-08-14 12:49     ` Mark Brown
2026-08-14 17:38       ` Honghui  Jiang [this message]
2026-08-14 17:41         ` Mark Brown
2026-08-15  2:32         ` David Gow
2026-08-14 12:28 ` [PATCH v2 0/4] spi: Fix DMA mapping ownership on partial map failure Andy Shevchenko
2026-08-14 15:49 ` Mark Brown

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=53943105.8b50.1a0015a531c.Coremail.jiang_hh2019@163.com \
    --to=jiang_hh2019@163.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=andy@kernel.org \
    --cc=brendan.higgins@linux.dev \
    --cc=broonie@kernel.org \
    --cc=david@davidgow.net \
    --cc=fancer.lancer@gmail.com \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=raemoar63@gmail.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
all inboxes | Powered by JetHome®