From: Mark Brown <broonie@kernel.org>
To: Vishwaroop A <va@nvidia.com>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
Thierry Reding <thierry.reding@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
smangipudi@nvidia.com
Subject: Re: [PATCH v2 0/2] spi: add sysfs interface for userspace device instantiation
Date: Fri, 1 May 2026 11:12:39 +0900 [thread overview]
Message-ID: <afQMF96WKJMZKU-E@sirena.co.uk> (raw)
In-Reply-To: <20260425173425.622042-1-va@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 554 bytes --]
On Sat, Apr 25, 2026 at 05:34:23PM +0000, Vishwaroop A wrote:
> Development boards such as the Jetson AGX Orin expose SPI buses on
> expansion headers so that users can connect and interact with SPI
> peripherals from userspace via /dev/spidevB.C character devices.
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 --]
prev parent reply other threads:[~2026-05-01 2:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 3:14 [PATCH 0/2] spi: add sysfs interface for userspace device instantiation Vishwaroop A
2026-04-20 3:14 ` [PATCH 1/2] spi: add new_device/delete_device sysfs interface Vishwaroop A
2026-04-22 14:41 ` Mark Brown
2026-04-20 3:14 ` [PATCH 2/2] docs: spi: add documentation for userspace device instantiation Vishwaroop A
2026-04-25 17:34 ` [PATCH v2 0/2] spi: add sysfs interface " Vishwaroop A
2026-04-25 17:34 ` [PATCH v2 1/2] spi: add new_device/delete_device sysfs interface Vishwaroop A
2026-05-01 2:15 ` Mark Brown
2026-04-25 17:34 ` [PATCH v2 2/2] docs: spi: add documentation for userspace device instantiation Vishwaroop A
2026-05-01 2:12 ` Mark Brown [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=afQMF96WKJMZKU-E@sirena.co.uk \
--to=broonie@kernel.org \
--cc=francesco.dolcini@toradex.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=smangipudi@nvidia.com \
--cc=thierry.reding@kernel.org \
--cc=va@nvidia.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