lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 9 Nov 2020 10:39:46 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     Loic Poulain <loic.poulain@...aro.org>
Cc:     David Miller <davem@...emloft.net>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
        cjhuang@...eaurora.org,
        Network Development <netdev@...r.kernel.org>
Subject: Re: [PATCH v2 0/5] net: qrtr: Add distant node support

On Mon, 9 Nov 2020 09:49:24 +0100 Loic Poulain wrote:
> > Looks like patch 1 is a bug fix and patches 2-5 add a new feature.
> > Is that correct?  
> 
> That's correct, though strictly speaking 2-5 are also bug fix since remote node
> communication is supposed to be supported in QRTR to be compatible with
> other implementations (downstream or private implementations).

Is there a spec we can quote to support that, or is QRTR purely 
a vendor interface?

What's the end user issue that we're solving? After firmware upgrade
things stop working? Things don't work on HW platforms on which this
was not tested? Don't work on new HW platforms?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ