All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Deepak Kumar Singh <deesin@codeaurora.org>
Cc: clew@codeaurora.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH V1 0/2] soc: qcom: aoss: Expose send for generic usecase
Date: Sun, 4 Apr 2021 12:20:37 -0500	[thread overview]
Message-ID: <YGn1ZXihsTyk4sIW@builder.lan> (raw)
In-Reply-To: <1617344238-12137-1-git-send-email-deesin@codeaurora.org>

On Fri 02 Apr 01:17 CDT 2021, Deepak Kumar Singh wrote:

> [Change from V0]

It's typical that the first patchset, without a version specified, is
considered "version 1", and as such the second submission would be
"v2".

> Update qmp_get to parse qmp handle with binding qcom,qmp
> 

I won't be able to merge this until we have a user of the API, so would
it be possible to get at least one consumer introduced?

Regards,
Bjorn

> Deepak Kumar Singh (2):
>   soc: qcom: aoss: Expose send for generic usecase
>   soc: qcom: aoss: Add debugfs entry
> 
>  drivers/soc/qcom/qcom_aoss.c | 77 +++++++++++++++++++++++++++++++++++++++++++-
>  1 file changed, 76 insertions(+), 1 deletion(-)
> 
> -- 
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> a Linux Foundation Collaborative Project
> 

      parent reply	other threads:[~2021-04-04 17:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-02  6:17 Deepak Kumar Singh
2021-04-02  6:17 ` [PATCH V1 1/2] " Deepak Kumar Singh
2021-04-02  9:09   ` kernel test robot
2021-04-02  9:50   ` kernel test robot
2021-04-04 17:17   ` Bjorn Andersson
2021-04-09  7:31     ` Manivannan Sadhasivam
2021-04-13  0:06       ` Bjorn Andersson
2021-04-02  6:17 ` [PATCH V1 2/2] soc: qcom: aoss: Add debugfs entry Deepak Kumar Singh
2021-04-04 16:59   ` Bjorn Andersson
2021-04-04 17:20 ` Bjorn Andersson [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=YGn1ZXihsTyk4sIW@builder.lan \
    --to=bjorn.andersson@linaro.org \
    --cc=clew@codeaurora.org \
    --cc=deesin@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --subject='Re: [PATCH V1 0/2] soc: qcom: aoss: Expose send for generic usecase' \
    /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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.