From: Hemant Kumar <hemantk@codeaurora.org>
To: gregkh@linuxfoundation.org, manivannan.sadhasivam@linaro.org
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
jhugo@codeaurora.org, bbhatt@codeaurora.org
Subject: Re: [PATCH v5 0/4] user space client interface driver
Date: Wed, 2 Sep 2020 13:31:34 -0700 [thread overview]
Message-ID: <81cdf27e-b962-3b0b-3f78-dfd95e2cf9bc@codeaurora.org> (raw)
In-Reply-To: <1596696063-17802-1-git-send-email-hemantk@codeaurora.org>
Hi Jeff and Mani,
On 8/5/20 11:40 PM, Hemant Kumar wrote:
> V5:
> - Removed mhi_uci_drv structure.
> - Used idr instead of creating global list of uci devices.
> - Used kref instead of local ref counting for uci device and
> open count.
> - Removed unlikely macro.
>
> V4:
> - Fix locking to protect proper struct members.
> - Updated documentation describing uci client driver use cases.
> - Fixed uci ref counting in mhi_uci_open for error case.
> - Addressed style related review comments.
>
> V3: Added documentation for MHI UCI driver.
>
> V2: Added mutex lock to prevent multiple readers to access same
> mhi buffer which can result into use after free.
>
> Hemant Kumar (4):
> bus: mhi: core: Add helper API to return number of free TREs
> bus: mhi: core: Move MHI_MAX_MTU to external header file
> docs: Add documentation for userspace client interface
> bus: mhi: clients: Add userspace client interface driver
>
> Documentation/mhi/index.rst | 1 +
> Documentation/mhi/uci.rst | 39 +++
> drivers/bus/mhi/Kconfig | 6 +
> drivers/bus/mhi/Makefile | 1 +
> drivers/bus/mhi/clients/Kconfig | 15 +
> drivers/bus/mhi/clients/Makefile | 3 +
> drivers/bus/mhi/clients/uci.c | 662 +++++++++++++++++++++++++++++++++++++++
> drivers/bus/mhi/core/internal.h | 1 -
> drivers/bus/mhi/core/main.c | 12 +
> include/linux/mhi.h | 12 +
> 10 files changed, 751 insertions(+), 1 deletion(-)
> create mode 100644 Documentation/mhi/uci.rst
> create mode 100644 drivers/bus/mhi/clients/Kconfig
> create mode 100644 drivers/bus/mhi/clients/Makefile
> create mode 100644 drivers/bus/mhi/clients/uci.c
>
Could you please review my changes on V5? I tried addressing Greg's
comment and would need help getting it reviewed from other contributors
to MHI driver as well.
Thanks,
Hemant
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2020-09-02 20:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 6:40 [PATCH v5 0/4] user space client interface driver Hemant Kumar
2020-08-06 6:41 ` [PATCH v5 1/4] bus: mhi: core: Add helper API to return number of free TREs Hemant Kumar
2020-08-06 6:41 ` [PATCH v5 2/4] bus: mhi: core: Move MHI_MAX_MTU to external header file Hemant Kumar
2020-08-06 6:41 ` [PATCH v5 3/4] docs: Add documentation for userspace client interface Hemant Kumar
2020-08-06 6:41 ` [PATCH v5 4/4] bus: mhi: clients: Add userspace client interface driver Hemant Kumar
2020-09-07 9:37 ` Greg KH
2020-09-11 6:28 ` Hemant Kumar
[not found] ` <010101747bd97269-a941d364-78ea-488c-baae-5a1c924d9e43-000000@us-west-2.amazonses.com>
2020-09-11 7:47 ` Greg KH
2020-09-02 20:31 ` Hemant Kumar [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=81cdf27e-b962-3b0b-3f78-dfd95e2cf9bc@codeaurora.org \
--to=hemantk@codeaurora.org \
--cc=bbhatt@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=jhugo@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.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