From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: "Goud, Srinivas" <srinivas.goud@amd.com>
Cc: "broonie@kernel.org" <broonie@kernel.org>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"patches@opensource.cirrus.com" <patches@opensource.cirrus.com>
Subject: Re: [PATCH v2 1/2] spi: spi-cadence: Interleave write of TX and read of RX FIFO
Date: Mon, 21 Aug 2023 08:55:14 +0000 [thread overview]
Message-ID: <20230821085514.GC103419@ediswmail.ad.cirrus.com> (raw)
In-Reply-To: <PH8PR12MB66754DDE4373E3667B882C46E11EA@PH8PR12MB6675.namprd12.prod.outlook.com>
On Mon, Aug 21, 2023 at 07:26:57AM +0000, Goud, Srinivas wrote:
> >
> >Do you have a web link to this ticket? Would be good to get some more
> >background.
> Here AR link which contains the issue description
> https://support.xilinx.com/s/article/65885?language=en_US
>
> Thanks,
> Srinivas
Apologies for the delay, the patch tests out fine for me. You
probably want to send it properly as a patch rather than just an
attachment. But when you do feel free to add my:
Reviewed-by: Charles Keepax <ckeepax@opensource.cirrus.com>
Tested-by: Charles Keepax <ckeepax@opensource.cirrus.com>
Thanks,
Charles
prev parent reply other threads:[~2023-08-21 8:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 9:39 [PATCH v2 1/2] spi: spi-cadence: Interleave write of TX and read of RX FIFO Charles Keepax
2023-05-18 9:39 ` [PATCH 2/2] spi: spi-cadence: Add missing kernel doc for clk_rate in cdns_spi Charles Keepax
2023-05-22 9:52 ` Mark Brown
2023-05-22 14:21 ` Charles Keepax
2023-05-22 14:26 ` Mark Brown
2023-05-22 14:29 ` [PATCH v2 1/2] spi: spi-cadence: Interleave write of TX and read of RX FIFO Mark Brown
2023-08-09 11:31 ` Goud, Srinivas
2023-08-10 10:09 ` Charles Keepax
2023-08-21 7:26 ` Goud, Srinivas
2023-08-21 8:55 ` Charles Keepax [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=20230821085514.GC103419@ediswmail.ad.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=srinivas.goud@amd.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;
as well as URLs for NNTP newsgroup(s).