Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: manivannan.sadhasivam@linaro.org
Cc: kuba@kernel.org, bjorn.andersson@linaro.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	kvalo@codeaurora.org
Subject: Re: [PATCH v2 0/2] Migrate QRTR Nameservice to Kernel
Date: Fri, 21 Feb 2020 12:05:30 -0800 (PST)	[thread overview]
Message-ID: <20200221.120530.2053615303875944335.davem@davemloft.net> (raw)
In-Reply-To: <20200220151327.4823-1-manivannan.sadhasivam@linaro.org>

From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Date: Thu, 20 Feb 2020 20:43:25 +0530

> This patchset migrates the Qualcomm IPC Router (QRTR) Nameservice from userspace
> to kernel under net/qrtr.
> 
> The userspace implementation of it can be found here:
> https://github.com/andersson/qrtr/blob/master/src/ns.c
> 
> This change is required for enabling the WiFi functionality of some Qualcomm
> WLAN devices using ATH11K without any dependency on a userspace daemon. Since
> the QRTR NS is not usually packed in most of the distros, users need to clone,
> build and install it to get the WiFi working. It will become a hassle when the
> user doesn't have any other source of network connectivity.
> 
> The original userspace code is published under BSD3 license. For migrating it
> to Linux kernel, I have adapted Dual BSD/GPL license.
> 
> This patchset has been verified on Dragonboard410c and Intel NUC with QCA6390
> WLAN device.

Series applied, thank you.

  parent reply	other threads:[~2020-02-21 20:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-20 15:13 [PATCH v2 0/2] Migrate QRTR Nameservice to Kernel Manivannan Sadhasivam
2020-02-20 15:13 ` [PATCH v2 1/2] net: qrtr: Migrate nameservice to kernel from userspace Manivannan Sadhasivam
2020-02-20 15:13 ` [PATCH v2 2/2] net: qrtr: Fix the local node ID as 1 Manivannan Sadhasivam
2020-02-21 20:05 ` David Miller [this message]
2020-03-06 16:18 ` [PATCH v2 0/2] Migrate QRTR Nameservice to Kernel Daniele Palmas
2020-03-06 17:17   ` Manivannan Sadhasivam

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=20200221.120530.2053615303875944335.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bjorn.andersson@linaro.org \
    --cc=kuba@kernel.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.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