From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Luca Boccassi <bluca@debian.org>, dpdk stable <stable@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>
Subject: [dpdk-stable] [PATCH 0/1] 17.11.x kni build issue with kernels 5.3
Date: Thu, 24 Oct 2019 09:31:29 +0200 [thread overview]
Message-ID: <20191024073130.11217-1-christian.ehrhardt@canonical.com> (raw)
I submitted issues against kernel 5.4 a few days ago, now 17.11.x failed
against kernel 5.3. Reported as [1] I'm wondering why this triggers only
for 17.11.x but not 18.11.x (the related content seems the same), but
OTOH the fix seems trivial so I thought I submit it for either
acceptance into 17.11.x or for a discussion why it might be different on
18.11.x that might help to spot a different change that could be
backported from there.
[1]: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1849571
Christian Ehrhardt (1):
kni: fix build with kernel 5.3
lib/librte_eal/linuxapp/kni/kni_net.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.23.0
next reply other threads:[~2019-10-24 7:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 7:31 Christian Ehrhardt [this message]
2019-10-24 7:31 ` [dpdk-stable] [PATCH 1/1] kni: fix build with kernel 5.3 Christian Ehrhardt
2019-10-24 8:05 ` Luca Boccassi
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=20191024073130.11217-1-christian.ehrhardt@canonical.com \
--to=christian.ehrhardt@canonical.com \
--cc=bluca@debian.org \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).