From mboxrd@z Thu Jan  1 00:00:00 1970
From: bugzilla@dpdk.org
Subject: [Bug 12] Request for submit in Kernel Upstream
Date: Mon, 22 Jan 2018 12:33:01 +0000
Message-ID: <bug-12-3@http.dpdk.org/tracker/>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
To: dev@dpdk.org
Return-path: <dev-bounces@dpdk.org>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

https://dpdk.org/tracker/show_bug.cgi?id=3D12

            Bug ID: 12
           Summary: Request for submit in Kernel Upstream
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: CONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: dpdk@leonardoamaral.com.br
  Target Milestone: ---

Hello!

As reported in https://bugzilla.redhat.com/show_bug.cgi?id=3D1536589#c3 -
distribution packagers could not use KNI in their default packaging system
since the kernel module isn't in upstream (I think it also leads to Secure =
Boot
issues too).

So can DPDK modules be submitted to Upstream Linux Kernel?

Thanks!

--=20
You are receiving this mail because:
You are the assignee for the bug.=