DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 12] Request for submit in Kernel Upstream
Date: Mon, 22 Jan 2018 12:33:01 +0000	[thread overview]
Message-ID: <bug-12-3@http.dpdk.org/tracker/> (raw)

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

            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=1536589#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!

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

             reply	other threads:[~2018-01-22 12:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-22 12:33 bugzilla [this message]
2018-02-07  9:54 ` bugzilla

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=bug-12-3@http.dpdk.org/tracker/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.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).