From: Praveen Talari <praveen.talari@oss.qualcomm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-spi@vger.kernel.org,
MukeshKumarSavaliyamukesh.savaliya@oss.qualcomm.com,
AniketRandiveaniket.randive@oss.qualcomm.com,
chandana.chiluveru@oss.qualcomm.com,
jyothi.seerapu@oss.qualcomm.com
Subject: Re: [PATCH v1 2/2] spi: qcom-geni: Add trace events for Qualcomm GENI SPI driver
Date: Thu, 7 May 2026 08:58:49 +0530 [thread overview]
Message-ID: <3ab480af-247f-498f-95f4-ab17526876a5@oss.qualcomm.com> (raw)
In-Reply-To: <afvltFJzKLaO9weP@sirena.co.uk>
Hi Mark,
On 07-05-2026 06:37, Mark Brown wrote:
> On Wed, May 06, 2026 at 10:59:43PM +0530, Praveen Talari wrote:
>
>> @@ -717,6 +726,7 @@ static bool geni_spi_handle_tx(struct spi_geni_master *mas)
>> max_bytes = mas->tx_rem_bytes;
>>
>> tx_buf = mas->cur_xfer->tx_buf + mas->cur_xfer->len - mas->tx_rem_bytes;
>> +
>> while (i < max_bytes) {
>> unsigned int j;
>> unsigned int bytes_to_write;
> Unrelated whitespace change.
oh its my bad. will fix in next patch set.
Thanks,
Praveen Talari
prev parent reply other threads:[~2026-05-07 3:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 17:29 [PATCH 0/2] Add trace events for Qualcomm GENI SPI drivers Praveen Talari
2026-05-06 17:29 ` [PATCH v1 1/2] spi: qcom-geni: trace: Add trace events for Qualcomm GENI SPI Praveen Talari
2026-05-07 1:02 ` Mark Brown
2026-05-07 3:28 ` Praveen Talari
2026-05-07 8:13 ` Mark Brown
2026-05-07 17:33 ` Praveen Talari
2026-05-08 14:01 ` Mark Brown
2026-05-08 23:14 ` Trilok Soni
2026-05-09 2:07 ` Praveen Talari
2026-05-10 12:37 ` Mark Brown
2026-05-11 2:50 ` Praveen Talari
2026-05-06 17:29 ` [PATCH v1 2/2] spi: qcom-geni: Add trace events for Qualcomm GENI SPI driver Praveen Talari
2026-05-07 1:07 ` Mark Brown
2026-05-07 3:28 ` Praveen Talari [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=3ab480af-247f-498f-95f4-ab17526876a5@oss.qualcomm.com \
--to=praveen.talari@oss.qualcomm.com \
--cc=AniketRandiveaniket.randive@oss.qualcomm.com \
--cc=MukeshKumarSavaliyamukesh.savaliya@oss.qualcomm.com \
--cc=broonie@kernel.org \
--cc=chandana.chiluveru@oss.qualcomm.com \
--cc=jyothi.seerapu@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.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