From: Haixu Cui <quic_haixcui@quicinc.com>
To: Harald Mommer <Harald.Mommer@opensynergy.com>
Cc: <quic_ztu@quicinc.com>, Matti Moell <Matti.Moell@opensynergy.com>,
"Mikhail Golubev" <Mikhail.Golubev@opensynergy.com>,
<linux-kernel@vger.kernel.org>, <linux-spi@vger.kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
"Mark Brown" <broonie@kernel.org>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>
Subject: Re: [RFC PATCH v3 3/3] SPI: Add virtio SPI driver.
Date: Mon, 4 Mar 2024 15:11:25 +0800 [thread overview]
Message-ID: <e2e5a7a0-7a2b-40d3-acf7-6f0b91bd5d40@quicinc.com> (raw)
In-Reply-To: <20240213135350.5878-4-Harald.Mommer@opensynergy.com>
On 2/13/2024 9:53 PM, Harald Mommer wrote:
> +static struct spi_board_info board_info = {
> + .modalias = "spi-virtio",
> +};
Hi Harald,
Do you add "spi-virtio" in spidev_spi_ids in spidev.c when you
doing the tests, to probe spidev driver?
Thanks
next prev parent reply other threads:[~2024-03-04 7:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 13:53 [RFC PATCH v3 0/3] Virtio SPI Linux driver compliant to draft spec V10 Harald Mommer
2024-02-13 13:53 ` [RFC PATCH v3 1/3] virtio: Add ID for virtio SPI Harald Mommer
2024-02-13 13:53 ` [RFC PATCH v3 2/3] virtio-spi: Add virtio-spi.h Harald Mommer
2024-02-13 13:53 ` [RFC PATCH v3 3/3] SPI: Add virtio SPI driver Harald Mommer
2024-02-13 17:49 ` Mark Brown
2024-02-27 14:12 ` Harald Mommer
2024-02-27 14:25 ` Mark Brown
2024-02-20 8:30 ` Haixu Cui
2024-02-26 10:41 ` Harald Mommer
2024-03-04 7:11 ` Haixu Cui [this message]
2024-03-04 10:52 ` [virtio-dev] " Harald Mommer
2024-03-05 7:46 ` Haixu Cui
2024-03-05 10:57 ` Harald Mommer
2024-03-05 17:54 ` [virtio-dev] Re: [RFC PATCH v3 3/3] SPI: Add virtio SPI driver. - Correction Harald Mommer
2024-03-06 7:48 ` Haixu Cui
2024-03-06 16:18 ` Harald Mommer
2024-03-11 9:28 ` Haixu Cui
2024-03-13 7:05 ` Haixu Cui
2024-02-14 16:22 ` [virtio-dev] [RFC PATCH v3 0/3] Virtio SPI Linux driver compliant to draft spec V10 Cornelia Huck
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=e2e5a7a0-7a2b-40d3-acf7-6f0b91bd5d40@quicinc.com \
--to=quic_haixcui@quicinc.com \
--cc=Harald.Mommer@opensynergy.com \
--cc=Matti.Moell@opensynergy.com \
--cc=Mikhail.Golubev@opensynergy.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=quic_ztu@quicinc.com \
--cc=viresh.kumar@linaro.org \
--cc=virtio-dev@lists.oasis-open.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®