From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Deepak Kumar Singh <quic_deesin@quicinc.com>
Cc: bjorn.andersson@linaro.org, arnaud.pouliquen@foss.st.com,
swboyd@chromium.org, quic_clew@quicinc.com,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH V4 0/2] rpmsg_char/ctrl driver fixes
Date: Mon, 19 Sep 2022 14:40:38 -0600 [thread overview]
Message-ID: <20220919204038.GF759648@p14s> (raw)
In-Reply-To: <1663584840-15762-1-git-send-email-quic_deesin@quicinc.com>
On Mon, Sep 19, 2022 at 04:23:58PM +0530, Deepak Kumar Singh wrote:
> Change from v4:
> Corrcted mistaked in commit message for patch2.
>
> Deepak Kumar Singh (2):
> rpmsg: glink: Add lock to avoid race when rpmsg device is released
> rpmsg: glink: Add lock to rpmsg_ctrldev_remove
>
Why does 'glink' still shows up in this cover letter and the version number wrong?
> drivers/rpmsg/rpmsg_char.c | 8 ++++++++
> drivers/rpmsg/rpmsg_ctrl.c | 2 ++
> 2 files changed, 10 insertions(+)
>
> --
> 2.7.4
>
next prev parent reply other threads:[~2022-09-19 20:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 10:53 [PATCH V4 0/2] rpmsg_char/ctrl driver fixes Deepak Kumar Singh
2022-09-19 10:53 ` [PATCH V5 1/2] rpmsg: char: Add lock to avoid race when rpmsg device is released Deepak Kumar Singh
2022-09-19 10:54 ` [PATCH V5 2/2] rpmsg: ctrl: Add lock to rpmsg_ctrldev_remove Deepak Kumar Singh
2022-09-19 20:40 ` Mathieu Poirier [this message]
2022-12-28 18:18 ` (subset) [PATCH V4 0/2] rpmsg_char/ctrl driver fixes Bjorn Andersson
-- strict thread matches above, loose matches on Subject: below --
2022-09-15 9:44 Deepak Kumar Singh
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=20220919204038.GF759648@p14s \
--to=mathieu.poirier@linaro.org \
--cc=arnaud.pouliquen@foss.st.com \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=quic_clew@quicinc.com \
--cc=quic_deesin@quicinc.com \
--cc=swboyd@chromium.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;
as well as URLs for NNTP newsgroup(s).