From: Praveen Talari <quic_ptalari@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@linaro.org>, <agross@kernel.org>,
<andersson@kernel.org>, <broonie@kernel.org>,
<linux-arm-msm@vger.kernel.org>, <linux-spi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <quic_msavaliy@quicinc.com>, <quic_vtanuku@quicinc.com>,
<quic_vnivarth@quicinc.com>, <quic_arandive@quicinc.com>
Subject: Re: [PATCH v5 0/2] spi-geni-qcom: Add SPI device mode support for GENI based QuPv3
Date: Thu, 13 Jul 2023 17:24:20 +0530 [thread overview]
Message-ID: <c1b4fe80-027d-4614-4186-dcfa5434fd23@quicinc.com> (raw)
In-Reply-To: <f26fed94-c6c2-cc39-62ec-8aee309456eb@linaro.org>
Hi
On 7/7/2023 5:59 PM, Konrad Dybcio wrote:
> On 7.07.2023 07:16, Praveen Talari wrote:
>> This series adds spi device mode functionality to geni based Qupv3.
>> The common header file contains spi slave related registers and masks.
>>
>> Praveen Talari (2):
>> soc: qcom: geni-se: Add SPI Device mode support for GENI based QuPv3
>> spi: spi-geni-qcom: Add SPI Device mode support for GENI based QuPv3
>> ---
>> v4 -> v5:
>> - Addressed review comments in driver
> "fix bug" says exactly nothing
Addressed
>
> Konrad
>> v3 -> v4:
>> - Used existing property spi-slave
>> - Hence dropped dt-binding changes
>>
>> v2 -> v3:
>> - Modified commit message
>> - Addressed comment on dt-binding
>>
>> v1 -> v2:
>> - Added dt-binding change for spi slave
>> - Modified commit message
>> - Addressed review comments in driver
>>
>> drivers/spi/spi-geni-qcom.c | 53 ++++++++++++++++++++++++++++----
>> include/linux/soc/qcom/geni-se.h | 9 ++++++
>> 2 files changed, 56 insertions(+), 6 deletions(-)
>>
prev parent reply other threads:[~2023-07-13 11:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 5:16 Praveen Talari
2023-07-07 5:16 ` [PATCH v5 1/2] soc: qcom: geni-se: Add SPI Device " Praveen Talari
2023-07-07 5:16 ` [PATCH v5 2/2] spi: spi-geni-qcom: " Praveen Talari
2023-07-07 12:29 ` [PATCH v5 0/2] spi-geni-qcom: Add SPI device " Konrad Dybcio
2023-07-13 11:54 ` 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=c1b4fe80-027d-4614-4186-dcfa5434fd23@quicinc.com \
--to=quic_ptalari@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=quic_arandive@quicinc.com \
--cc=quic_msavaliy@quicinc.com \
--cc=quic_vnivarth@quicinc.com \
--cc=quic_vtanuku@quicinc.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
all inboxes | Powered by JetHome®