Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Wed, 08 Apr 2020 14:33:27 -0700 (PDT)
Message-Id: <20200408.143327.2268546094613330028.davem@davemloft.net>
To:     wenhu.wang@vivo.com
Cc:     akpm@linux-foundation.org, kuba@kernel.org,
        gregkh@linuxfoundation.org, tglx@linutronix.de,
        bjorn.andersson@linaro.org, hofrat@osadl.org, allison@lohutok.net,
        johannes.berg@intel.com, arnd@arndb.de, cjhuang@codeaurora.org,
        linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
        kernel@vivo.com
Subject: Re: [PATCH RESEND] net: qrtr: support qrtr service and lookup route
From:   David Miller <davem@davemloft.net>
In-Reply-To: <20200408104833.6880-1-wenhu.wang@vivo.com>
References: <20200408104833.6880-1-wenhu.wang@vivo.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

From: Wang Wenhu <wenhu.wang@vivo.com>
Date: Wed,  8 Apr 2020 03:46:35 -0700

> QSR implements maintenance of qrtr services and lookups. It would
> be helpful for developers to work with QRTR without the none-opensource
> user-space implementation part of IPC Router.
> 
> As we know, the extremely important point of IPC Router is the support
> of services form different nodes. But QRTR was pushed into mainline
> without route process support of services, and the router port process
> is implemented in user-space as none-opensource codes, which is an
> great unconvenience for developers.
> 
> QSR also implements a interface via chardev and a set of sysfs class
> files for the communication and debugging in user-space. We can get
> service and lookup entries conveniently via sysfs file in /sys/class/qsr/.
> Currently add-server, del-server, add-lookup and del-lookup control
> packatets are processed and enhancements could be taken easily upon
> currently implementation.
> 
> Signed-off-by: Wang Wenhu <wenhu.wang@vivo.com>

New features are only appropriate for net-next which is closed right now.