From: Leon Romanovsky <leon@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: Jeffrey Hugo <jhugo@codeaurora.org>,
Jakub Kicinski <kuba@kernel.org>,
Hemant Kumar <hemantk@codeaurora.org>,
gregkh@linuxfoundation.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, bbhatt@codeaurora.org,
loic.poulain@linaro.org, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org, Kalle Valo <kvalo@codeaurora.org>
Subject: Re: [PATCH v13 0/4] userspace MHI client interface driver
Date: Tue, 8 Dec 2020 21:16:03 +0200 [thread overview]
Message-ID: <20201208191603.GJ4430@unreal> (raw)
In-Reply-To: <20201208165927.GE9925@work>
On Tue, Dec 08, 2020 at 10:29:27PM +0530, Manivannan Sadhasivam wrote:
> On Sun, Dec 06, 2020 at 10:33:02AM +0200, Leon Romanovsky wrote:
> > On Tue, Dec 01, 2020 at 09:59:53PM -0700, Jeffrey Hugo wrote:
> > > On 12/1/2020 7:55 PM, Jakub Kicinski wrote:
> > > > On Tue, 1 Dec 2020 13:48:36 -0700 Jeffrey Hugo wrote:
> > > > > On 12/1/2020 1:03 PM, Jakub Kicinski wrote:
> > > > > > On Tue, 1 Dec 2020 12:40:50 -0700 Jeffrey Hugo wrote:
> > > > > > > On 12/1/2020 12:29 PM, Jakub Kicinski wrote:
> > > > > > > > On Fri, 27 Nov 2020 19:26:02 -0800 Hemant Kumar wrote:
> > > > > > > > > This patch series adds support for UCI driver. UCI driver enables userspace
> > > > > > > > > clients to communicate to external MHI devices like modem and WLAN. UCI driver
> > > > > > > > > probe creates standard character device file nodes for userspace clients to
> > > > > > > > > perform open, read, write, poll and release file operations. These file
> > > > > > > > > operations call MHI core layer APIs to perform data transfer using MHI bus
> > > > > > > > > to communicate with MHI device. Patch is tested using arm64 based platform.
> > > > > > > >
> > > > > > > > Wait, I thought this was for modems.
> > > > > > > >
>
> [...]
>
> > Like it or not, but Jakub is absolutely right with his claim that
> > providing user-visible interfaces without any standardization is proven
> > as wrong.
> >
>
> Everybody agrees with standardizing things but the problem is, the
> standardization will only happen when more than one person implements the
> same functionality.
From my experience in RDMA and netdev, I can't agree with both of your
statements. There are a lot of people who see standardization as a bad
thing. Also we are pushing even one person to make user visible interfaces
right from the beginning without relation to how wide it will be adopted
later.
Thanks
next prev parent reply other threads:[~2020-12-08 20:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 3:26 [PATCH v13 0/4] userspace MHI client interface driver Hemant Kumar
2020-11-28 3:26 ` [PATCH v13 1/4] bus: mhi: core: Add helper API to return number of free TREs Hemant Kumar
2020-11-28 3:26 ` [PATCH v13 2/4] bus: mhi: core: Move MHI_MAX_MTU to external header file Hemant Kumar
2020-11-28 3:26 ` [PATCH v13 3/4] docs: Add documentation for userspace client interface Hemant Kumar
2020-11-28 3:26 ` [PATCH v13 4/4] bus: mhi: Add userspace client interface driver Hemant Kumar
2020-11-28 6:11 ` Manivannan Sadhasivam
2020-12-01 1:08 ` Hemant Kumar
2020-11-30 18:22 ` Loic Poulain
2020-12-01 1:16 ` Hemant Kumar
2020-12-01 17:36 ` Loic Poulain
2020-12-01 17:37 ` Jeffrey Hugo
2020-12-01 17:52 ` Loic Poulain
2020-12-01 17:51 ` Jeffrey Hugo
2020-12-01 18:05 ` Loic Poulain
2020-12-01 18:04 ` Jeffrey Hugo
2020-12-01 21:59 ` Hemant Kumar
2020-12-01 19:29 ` [PATCH v13 0/4] userspace MHI " Jakub Kicinski
2020-12-01 19:40 ` Jeffrey Hugo
2020-12-01 20:03 ` Jakub Kicinski
2020-12-01 20:48 ` Jeffrey Hugo
2020-12-02 2:55 ` Jakub Kicinski
2020-12-02 4:59 ` Jeffrey Hugo
2020-12-06 8:33 ` Leon Romanovsky
2020-12-08 16:59 ` Manivannan Sadhasivam
2020-12-08 19:16 ` Leon Romanovsky [this message]
2020-12-02 4:15 ` Manivannan Sadhasivam
2020-12-02 4:38 ` Bjorn Andersson
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=20201208191603.GJ4430@unreal \
--to=leon@kernel.org \
--cc=bbhatt@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=hemantk@codeaurora.org \
--cc=jhugo@codeaurora.org \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=netdev@vger.kernel.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).