mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Shuai Liu <847807867@qq.com>
Cc: linux-spi@vger.kernel.org, rust-for-linux@vger.kernel.org,
	ojeda@kernel.org, dakr@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 0/3] rust: spi: add SPI driver abstractions
Date: Fri, 13 Nov 2026 12:25:05 +0000	[thread overview]
Message-ID: <f8d00405-e8cf-4c77-a75c-9792ea81a546@sirena.org.uk> (raw)
In-Reply-To: <tencent_097BA6F40A0B8FBC4C130C6EBF58F8048006@qq.com>

[-- Attachment #1: Type: text/plain, Size: 768 bytes --]

On Fri, Nov 13, 2026 at 10:05:28AM +0800, Shuai Liu wrote:
> Rework the device I/O to map onto the lower-level C APIs, as suggested
> by Mark Brown [1]: instead of leveraging the C convenience wrappers
> (spi_write(), spi_read() and spi_write_then_read()), all device I/O is
> now built on a single `SpiDevice::transfer()` primitive that maps onto
> spi_sync(). The convenience methods `write()`, `read()` and
> `write_then_read()` remain as thin wrappers on top of `transfer()`.

Please don't send new patches in reply to old patches or serieses, this
makes it harder for both people and tools to understand what is going
on - it can bury things in mailboxes and make it difficult to keep track
of what current patches are, both for the new patches and the old ones.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2026-11-13 12:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20261027054209.904654-1-847807867@qq.com>
2026-10-27  5:42 ` [PATCH v6 1/3] rust: helpers: add SPI helpers Shuai Liu
2026-10-27  5:42 ` [PATCH v6 2/3] rust: spi: add SPI driver abstractions Shuai Liu
2026-11-12 19:30   ` Mark Brown
2026-11-13  2:04     ` Shuai Liu
2026-11-13  2:05     ` [PATCH v7 0/3] " Shuai Liu
2026-11-13  2:25       ` [PATCH v7 1/3] rust: helpers: add SPI helpers Shuai Liu
     [not found]       ` <20261113022539.601421-1-847807867@qq.com>
2026-11-13  2:25         ` [PATCH v7 2/3] rust: spi: add SPI driver abstractions Shuai Liu
2026-11-13  2:25         ` [PATCH v7 3/3] samples: rust: add SPI driver sample Shuai Liu
2026-11-13  2:25       ` [PATCH v7 1/3] rust: helpers: add SPI helpers Shuai Liu
     [not found]       ` <20261113022552.601873-1-847807867@qq.com>
2026-11-13  2:25         ` [PATCH v7 2/3] rust: spi: add SPI driver abstractions Shuai Liu
2026-11-13  2:25         ` [PATCH v7 3/3] samples: rust: add SPI driver sample Shuai Liu
2026-11-13 12:25       ` Mark Brown [this message]
2026-10-27  5:42 ` [PATCH v6 " Shuai Liu

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=f8d00405-e8cf-4c77-a75c-9792ea81a546@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=847807867@qq.com \
    --cc=dakr@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.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 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®