[yocto] Reminder: Yocto Project Technical Team Meeting @ Monthly from 8am to 8:30am on the first Tuesday (PST)

[sjolley.yp.pm]

All,

 

Just a reminder we will hold the monthly Yocto Project Technical Meeting at
8am PST tomorrow. (8/6)  

 

Yocto Project Technical Team Meeting: We encourage people attending the
meeting to logon and announce themselves on the Yocto Project IRC chancel
during the meeting (optional):

Yocto IRC: http://webchat.freenode.net/?channels=#yocto

 

Wiki: https://www.yoctoproject.org/public-virtual-meetings/

 

WhenMonthly from 8am to 8:30am on the first Tuesday Pacific Time

Where   Zoom Meeting: https://zoom.us/j/990892712 

 

I will be tracking the minutes at:
https://docs.google.com/document/d/1Y5IIuE-z0Ykdl-DwuzUJh52flOZuhN_TSAfw2tdU
9pg/edit?ts=5c06b22d  Please request access if you want to assist in editing
them.  The world should have view access. 

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

[sjolley.yp.pm]

All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

 

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs

 

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 297
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now, "2.8", "2.9', "2.99" and "Future", the more pressing/urgent
issues being in "2.8" and then "2.9".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [layerindex-web][PATCH 00/15] REST API / import_layers improvements (cover letter only)

[Paul Eggleton]

Add some missing items to the REST API and extend the import_layers
script in order to make it possible to create and update a clone of an
existing layer index without needing to fetch and parse all of the layer
repositories.


The following changes since commit 9ce9f7d2d1870a90b95809f43bae5d4e9f1ebd93:

  dockersetup: fix regression with https enabled (2019-07-31 09:03:46 +1200)

are available in the Git repository at:

  git://git.yoctoproject.org/layerindex-web paule/importlayers
  http://git.yoctoproject.org/cgit.cgi/layerindex-web/log/?h=paule/importlayers

Paul Eggleton (15):
  API: add sources, patches, dependencies to recipes
  API: add BBAppend and IncFile objects to REST API
  import_layers: avoid importing duplicate objects
  import_layers: enable incremental LayerItem/LayerBranch import
  import_layers: import recipes
  import_layers: import other missing items
  admin: add layerbranch to BBAppend string representation
  Add simple script for testing web API
  import_layers: switch to argparse
  import_layers: allow filtering branches
  import_layers: allow filtering layers
  import_layers: delete non-matching LayerBranch objects
  import_layers: add reload option
  import_layers: show basic progress
  README: add reference to using import_layers to update

 README|  10 +-
 layerindex/models.py  |   2 +-
 layerindex/restviews.py   |  74 +-
 layerindex/tools/import_layers.py | 405 +++---
 layerindex/tools/webapi-test.py   |  71 ++
 layerindex/urls.py|   2 +
 6 files changed, 469 insertions(+), 95 deletions(-)
 create mode 100755 layerindex/tools/webapi-test.py

-- 
2.20.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Loading a Yocto kernel on Hyper-V hangs

[Yair Itzhaki]

Hi ,
I'm using Poky (Warrior).
Built a Plain Vanilla system for bare-metal x64, and put it on a hard-drive.
The system boots well on an Intel MB.

Then, added a WIC image target, and converted the disk iamge (using qemu-img) 
into a VMDK.
The image boots well (Grub prompt, followed by kernel loading) on a Windows 
VmWare (though I had to add some kernel features to make the root FS available).

Next, I converted the same image to VHDX using qemu-img.
Configured a HyperV Gen2 machine (to use UEFI). Security is turned off.
Grub2 loads well:
I get a Grub prompt, select the kernel – but once selected - the system hangs.
Tried on different Windows machine (Win10, Server 2016)

When replacing the kernel with a stock Ubuntu kernel – the kernel loads well.
Tried other (pre-built) kernels from 
http://downloads.yoctoproject.org/releases/yocto/yocto-x.y/ – same odd 
behavior: Grub loads, kernel does not load.
Tried a different compression (other than gzip) – same.

Any idea?

Thanks,
Yair


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Pyro, bitbake, git pull for my recipe (Why not?)

[Mauro Ziliani]

Hi all.

It seems that bitbake doesn't check the remote git repository of my 
application (terminal is the name of the recipe) every time I do



bitbake  terminal


The recipe is this

#  the recipe -

SRCREV="${AUTOREV}"

SRC_URI = " \

    git://git@server/terminal.git;protocol=ssh;branch=master \

"


S := "${WORKDIR}/git"

inherit qmake5

#  the end of recipe -


Any idea to force git pull?


Best regards,

  MZ

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] installed-vs-shipped

[Mauro Ziliani]

Thanks.

My final purpore is install the application into its own home folder: 
/home/terminal


So I have to write

FILES_${PN} += " /home/terminal "


I think that, due to Makefile install: rules which install in 
/usr/local, Yocto can track this has "home folder" for the application



Thansk again

 MZ

Il 02/08/2019 22:05, Khem Raj ha scritto:

Add

FILES_${PN} += "/usr/local/bin"

in recipe. but it would be nicer if it was installed into /usr/bin by
qmake/make files itself

On Fri, Aug 2, 2019 at 11:59 AM Mauro Ziliani  wrote:

Hi all.

This is my problem.

I have my terminal.pro project (qmake5) with target "terminal".

The default destination folder for the binary is /usr/local/bin

With this setup I get installed-vs-shipped error.


Why?

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-dpdk][PATCH] dpdk: igb_uio: fix build on Linux 5.3 for fall through

[zhe.he]

From: He Zhe 

Since kernel v5.3 "-Wimplicit-fallthrough=3" gcc flag is enabled by default by
a035d552a93b ("Makefile: Globally enable fall-through warning") and would cause
the following build failure.

x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.c:248:
6: error: this statement may fall through [-Werror=implicit-fallthrough=]

Backport a patch from upstream and adjust context respectively for v17 and v18.
c96bbbd010f7abb88c2ca2ed9dfc5ecd37e9027d

Signed-off-by: He Zhe 
---
 ...o-fix-build-on-Linux-5.3-for-fall-through.patch | 81 ++
 ...o-fix-build-on-Linux-5.3-for-fall-through.patch | 80 +
 recipes-extended/dpdk/dpdk_17.11.6.bb  |  1 +
 recipes-extended/dpdk/dpdk_18.11.2.bb  |  4 ++
 4 files changed, 166 insertions(+)
 create mode 100644 
recipes-extended/dpdk/dpdk/dpdk-17.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
 create mode 100644 
recipes-extended/dpdk/dpdk/dpdk-18.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch

diff --git 
a/recipes-extended/dpdk/dpdk/dpdk-17.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
 
b/recipes-extended/dpdk/dpdk/dpdk-17.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
new file mode 100644
index 000..94310dd
--- /dev/null
+++ 
b/recipes-extended/dpdk/dpdk/dpdk-17.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
@@ -0,0 +1,81 @@
+From c0307019689d5f8b4d5ca7d92a5585c94088afeb Mon Sep 17 00:00:00 2001
+From: Ferruh Yigit 
+Date: Mon, 29 Jul 2019 13:32:16 +0100
+Subject: [PATCH] igb_uio: fix build on Linux 5.3 for fall through
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+build error:
+kernel/linux/igb_uio/igb_uio.c:
+   In function ‘igbuio_pci_enable_interrupts’:
+   kernel/linux/igb_uio/igb_uio.c:230:6:
+   error: this statement may fall through
+   [-Werror=implicit-fallthrough=]
+  230 |   if (pci_alloc_irq_vectors(udev->pdev, 1, 1, 
+kernel/linux/igb_uio/igb_uio.c:240:2: note: here
+  240 |  case RTE_INTR_MODE_MSI:
+  |  ^~~~
+
+The build error is caused by Linux kernel commit in 5.3 that enables the
+"-Wimplicit-fallthrough=3" gcc flag.
+Commit a035d552a93b ("Makefile: Globally enable fall-through warning")
+
+To fix the error, either a gcc attribute can be provided [1] or a code
+comment with some defined syntax need to be provided [2], since there is
+already comments, updated them slightly to match the required syntax to
+fix the build error.
+
+[1]
+"__attribute__ ((fallthrough));"
+
+[2]
+[ \t.!]*([Ee]lse,? |[Ii]ntentional(ly)? )?
+fall(s | |-)?thr(ough|u)[ \t.!]*(-[^\n\r]*)?
+
+Cc: sta...@dpdk.org
+
+Signed-off-by: Ferruh Yigit 
+
+Upstream-Status: Backport[c96bbbd010f7abb88c2ca2ed9dfc5ecd37e9027d]
+Adjust code context
+
+Signed-off-by: He Zhe 
+---
+ lib/librte_eal/linuxapp/igb_uio/igb_uio.c | 6 +++---
+ 1 file changed, 3 insertions(+), 3 deletions(-)
+
+diff --git a/lib/librte_eal/linuxapp/igb_uio/igb_uio.c 
b/lib/librte_eal/linuxapp/igb_uio/igb_uio.c
+index 45d7027..3073bca 100644
+--- a/lib/librte_eal/linuxapp/igb_uio/igb_uio.c
 b/lib/librte_eal/linuxapp/igb_uio/igb_uio.c
+@@ -254,7 +254,7 @@ igbuio_pci_enable_interrupts(struct rte_uio_pci_dev *udev)
+   }
+ #endif
+ 
+-  /* fall back to MSI */
++  /* falls through - to MSI */
+   case RTE_INTR_MODE_MSI:
+ #ifndef HAVE_ALLOC_IRQ_VECTORS
+   if (pci_enable_msi(udev->pdev) == 0) {
+@@ -273,7 +273,7 @@ igbuio_pci_enable_interrupts(struct rte_uio_pci_dev *udev)
+   break;
+   }
+ #endif
+-  /* fall back to INTX */
++  /* falls through - to INTX */
+   case RTE_INTR_MODE_LEGACY:
+   if (pci_intx_mask_supported(udev->pdev)) {
+   dev_dbg(&udev->pdev->dev, "using INTX");
+@@ -283,7 +283,7 @@ igbuio_pci_enable_interrupts(struct rte_uio_pci_dev *udev)
+   break;
+   }
+   dev_notice(&udev->pdev->dev, "PCI INTX mask not supported\n");
+-  /* fall back to no IRQ */
++  /* falls through - to no IRQ */
+   case RTE_INTR_MODE_NONE:
+   udev->mode = RTE_INTR_MODE_NONE;
+   udev->info.irq = UIO_IRQ_NONE;
+-- 
+2.7.4
+
diff --git 
a/recipes-extended/dpdk/dpdk/dpdk-18.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
 
b/recipes-extended/dpdk/dpdk/dpdk-18.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
new file mode 100644
index 000..3222a3c
--- /dev/null
+++ 
b/recipes-extended/dpdk/dpdk/dpdk-18.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
@@ -0,0 +1,80 @@
+From af89b90b4e5e9d1533b6debd86ae38bbd82df8c8 Mon Sep 17 00:00:00 2001
+From: Ferruh Yigit 
+Date: Mon, 29 Jul 2019 13:32:16 +0100
+Subject: [PATCH] igb_uio: fix build on Linux 5.3 for fall through
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+build error:
+kernel/linux/igb_uio/igb_uio.c:
+   In function 

Re: [yocto] [meta-dpdk][PATCH] dpdk: igb_uio: fix build on Linux 5.3 for fall through

[He Zhe]

Please ignore.

Zhe

On 8/5/19 3:51 PM, zhe...@windriver.com wrote:
> From: He Zhe 
>
> Since kernel v5.3 "-Wimplicit-fallthrough=3" gcc flag is enabled by default by
> a035d552a93b ("Makefile: Globally enable fall-through warning") and would 
> cause
> the following build failure.
>
> x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.c:248:
> 6: error: this statement may fall through [-Werror=implicit-fallthrough=]
>
> Backport a patch from upstream and adjust context respectively for v17 and 
> v18.
> c96bbbd010f7abb88c2ca2ed9dfc5ecd37e9027d
>
> Signed-off-by: He Zhe 
> ---
>  ...o-fix-build-on-Linux-5.3-for-fall-through.patch | 81 
> ++
>  ...o-fix-build-on-Linux-5.3-for-fall-through.patch | 80 +
>  recipes-extended/dpdk/dpdk_17.11.6.bb  |  1 +
>  recipes-extended/dpdk/dpdk_18.11.2.bb  |  4 ++
>  4 files changed, 166 insertions(+)
>  create mode 100644 
> recipes-extended/dpdk/dpdk/dpdk-17.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
>  create mode 100644 
> recipes-extended/dpdk/dpdk/dpdk-18.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
>
> diff --git 
> a/recipes-extended/dpdk/dpdk/dpdk-17.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
>  
> b/recipes-extended/dpdk/dpdk/dpdk-17.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
> new file mode 100644
> index 000..90901eb
> --- /dev/null
> +++ 
> b/recipes-extended/dpdk/dpdk/dpdk-17.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
> @@ -0,0 +1,81 @@
> +From c0307019689d5f8b4d5ca7d92a5585c94088afeb Mon Sep 17 00:00:00 2001
> +From: Ferruh Yigit 
> +Date: Mon, 29 Jul 2019 13:32:16 +0100
> +Subject: [PATCH] igb_uio: fix build on Linux 5.3 for fall through
> +MIME-Version: 1.0
> +Content-Type: text/plain; charset=UTF-8
> +Content-Transfer-Encoding: 8bit
> +
> +build error:
> +kernel/linux/igb_uio/igb_uio.c:
> +   In function ‘igbuio_pci_enable_interrupts’:
> +   kernel/linux/igb_uio/igb_uio.c:230:6:
> +   error: this statement may fall through
> +   [-Werror=implicit-fallthrough=]
> +  230 |   if (pci_alloc_irq_vectors(udev->pdev, 1, 1, 
> +kernel/linux/igb_uio/igb_uio.c:240:2: note: here
> +  240 |  case RTE_INTR_MODE_MSI:
> +  |  ^~~~
> +
> +The build error is caused by Linux kernel commit in 5.3 that enables the
> +"-Wimplicit-fallthrough=3" gcc flag.
> +Commit a035d552a93b ("Makefile: Globally enable fall-through warning")
> +
> +To fix the error, either a gcc attribute can be provided [1] or a code
> +comment with some defined syntax need to be provided [2], since there is
> +already comments, updated them slightly to match the required syntax to
> +fix the build error.
> +
> +[1]
> +"__attribute__ ((fallthrough));"
> +
> +[2]
> +[ \t.!]*([Ee]lse,? |[Ii]ntentional(ly)? )?
> +fall(s | |-)?thr(ough|u)[ \t.!]*(-[^\n\r]*)?
> +
> +Cc: sta...@dpdk.org
> +
> +Signed-off-by: Ferruh Yigit 
> +
> +commit c96bbbd010f7abb88c2ca2ed9dfc5ecd37e9027d upstream
> +Adjust code context
> +
> +Signed-off-by: He Zhe 
> +---
> + lib/librte_eal/linuxapp/igb_uio/igb_uio.c | 6 +++---
> + 1 file changed, 3 insertions(+), 3 deletions(-)
> +
> +diff --git a/lib/librte_eal/linuxapp/igb_uio/igb_uio.c 
> b/lib/librte_eal/linuxapp/igb_uio/igb_uio.c
> +index 45d7027..3073bca 100644
> +--- a/lib/librte_eal/linuxapp/igb_uio/igb_uio.c
>  b/lib/librte_eal/linuxapp/igb_uio/igb_uio.c
> +@@ -254,7 +254,7 @@ igbuio_pci_enable_interrupts(struct rte_uio_pci_dev 
> *udev)
> + }
> + #endif
> + 
> +-/* fall back to MSI */
> ++/* falls through - to MSI */
> + case RTE_INTR_MODE_MSI:
> + #ifndef HAVE_ALLOC_IRQ_VECTORS
> + if (pci_enable_msi(udev->pdev) == 0) {
> +@@ -273,7 +273,7 @@ igbuio_pci_enable_interrupts(struct rte_uio_pci_dev 
> *udev)
> + break;
> + }
> + #endif
> +-/* fall back to INTX */
> ++/* falls through - to INTX */
> + case RTE_INTR_MODE_LEGACY:
> + if (pci_intx_mask_supported(udev->pdev)) {
> + dev_dbg(&udev->pdev->dev, "using INTX");
> +@@ -283,7 +283,7 @@ igbuio_pci_enable_interrupts(struct rte_uio_pci_dev 
> *udev)
> + break;
> + }
> + dev_notice(&udev->pdev->dev, "PCI INTX mask not supported\n");
> +-/* fall back to no IRQ */
> ++/* falls through - to no IRQ */
> + case RTE_INTR_MODE_NONE:
> + udev->mode = RTE_INTR_MODE_NONE;
> + udev->info.irq = UIO_IRQ_NONE;
> +-- 
> +2.7.4
> +
> diff --git 
> a/recipes-extended/dpdk/dpdk/dpdk-18.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
>  
> b/recipes-extended/dpdk/dpdk/dpdk-18.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
> new file mode 100644
> index 000..417d93b
> --- /dev/null
> +++ 
> b/recipes-extended/dpdk/dpdk/dpdk-18.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
> @@ -0,0 +1,80 @@
> +From af89b90b4e5e9d1533b6debd86ae38bbd82df8c8 Mon Sep 17 00:00:00 2001
>

[yocto] [meta-dpdk][PATCH] dpdk: igb_uio: fix build on Linux 5.3 for fall through

[zhe.he]

From: He Zhe 

Since kernel v5.3 "-Wimplicit-fallthrough=3" gcc flag is enabled by default by
a035d552a93b ("Makefile: Globally enable fall-through warning") and would cause
the following build failure.

x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.c:248:
6: error: this statement may fall through [-Werror=implicit-fallthrough=]

Backport a patch from upstream and adjust context respectively for v17 and v18.
c96bbbd010f7abb88c2ca2ed9dfc5ecd37e9027d

Signed-off-by: He Zhe 
---
 ...o-fix-build-on-Linux-5.3-for-fall-through.patch | 81 ++
 ...o-fix-build-on-Linux-5.3-for-fall-through.patch | 80 +
 recipes-extended/dpdk/dpdk_17.11.6.bb  |  1 +
 recipes-extended/dpdk/dpdk_18.11.2.bb  |  4 ++
 4 files changed, 166 insertions(+)
 create mode 100644 
recipes-extended/dpdk/dpdk/dpdk-17.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
 create mode 100644 
recipes-extended/dpdk/dpdk/dpdk-18.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch

diff --git 
a/recipes-extended/dpdk/dpdk/dpdk-17.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
 
b/recipes-extended/dpdk/dpdk/dpdk-17.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
new file mode 100644
index 000..90901eb
--- /dev/null
+++ 
b/recipes-extended/dpdk/dpdk/dpdk-17.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
@@ -0,0 +1,81 @@
+From c0307019689d5f8b4d5ca7d92a5585c94088afeb Mon Sep 17 00:00:00 2001
+From: Ferruh Yigit 
+Date: Mon, 29 Jul 2019 13:32:16 +0100
+Subject: [PATCH] igb_uio: fix build on Linux 5.3 for fall through
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+build error:
+kernel/linux/igb_uio/igb_uio.c:
+   In function ‘igbuio_pci_enable_interrupts’:
+   kernel/linux/igb_uio/igb_uio.c:230:6:
+   error: this statement may fall through
+   [-Werror=implicit-fallthrough=]
+  230 |   if (pci_alloc_irq_vectors(udev->pdev, 1, 1, 
+kernel/linux/igb_uio/igb_uio.c:240:2: note: here
+  240 |  case RTE_INTR_MODE_MSI:
+  |  ^~~~
+
+The build error is caused by Linux kernel commit in 5.3 that enables the
+"-Wimplicit-fallthrough=3" gcc flag.
+Commit a035d552a93b ("Makefile: Globally enable fall-through warning")
+
+To fix the error, either a gcc attribute can be provided [1] or a code
+comment with some defined syntax need to be provided [2], since there is
+already comments, updated them slightly to match the required syntax to
+fix the build error.
+
+[1]
+"__attribute__ ((fallthrough));"
+
+[2]
+[ \t.!]*([Ee]lse,? |[Ii]ntentional(ly)? )?
+fall(s | |-)?thr(ough|u)[ \t.!]*(-[^\n\r]*)?
+
+Cc: sta...@dpdk.org
+
+Signed-off-by: Ferruh Yigit 
+
+commit c96bbbd010f7abb88c2ca2ed9dfc5ecd37e9027d upstream
+Adjust code context
+
+Signed-off-by: He Zhe 
+---
+ lib/librte_eal/linuxapp/igb_uio/igb_uio.c | 6 +++---
+ 1 file changed, 3 insertions(+), 3 deletions(-)
+
+diff --git a/lib/librte_eal/linuxapp/igb_uio/igb_uio.c 
b/lib/librte_eal/linuxapp/igb_uio/igb_uio.c
+index 45d7027..3073bca 100644
+--- a/lib/librte_eal/linuxapp/igb_uio/igb_uio.c
 b/lib/librte_eal/linuxapp/igb_uio/igb_uio.c
+@@ -254,7 +254,7 @@ igbuio_pci_enable_interrupts(struct rte_uio_pci_dev *udev)
+   }
+ #endif
+ 
+-  /* fall back to MSI */
++  /* falls through - to MSI */
+   case RTE_INTR_MODE_MSI:
+ #ifndef HAVE_ALLOC_IRQ_VECTORS
+   if (pci_enable_msi(udev->pdev) == 0) {
+@@ -273,7 +273,7 @@ igbuio_pci_enable_interrupts(struct rte_uio_pci_dev *udev)
+   break;
+   }
+ #endif
+-  /* fall back to INTX */
++  /* falls through - to INTX */
+   case RTE_INTR_MODE_LEGACY:
+   if (pci_intx_mask_supported(udev->pdev)) {
+   dev_dbg(&udev->pdev->dev, "using INTX");
+@@ -283,7 +283,7 @@ igbuio_pci_enable_interrupts(struct rte_uio_pci_dev *udev)
+   break;
+   }
+   dev_notice(&udev->pdev->dev, "PCI INTX mask not supported\n");
+-  /* fall back to no IRQ */
++  /* falls through - to no IRQ */
+   case RTE_INTR_MODE_NONE:
+   udev->mode = RTE_INTR_MODE_NONE;
+   udev->info.irq = UIO_IRQ_NONE;
+-- 
+2.7.4
+
diff --git 
a/recipes-extended/dpdk/dpdk/dpdk-18.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
 
b/recipes-extended/dpdk/dpdk/dpdk-18.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
new file mode 100644
index 000..417d93b
--- /dev/null
+++ 
b/recipes-extended/dpdk/dpdk/dpdk-18.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
@@ -0,0 +1,80 @@
+From af89b90b4e5e9d1533b6debd86ae38bbd82df8c8 Mon Sep 17 00:00:00 2001
+From: Ferruh Yigit 
+Date: Mon, 29 Jul 2019 13:32:16 +0100
+Subject: [PATCH] igb_uio: fix build on Linux 5.3 for fall through
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+build error:
+kernel/linux/igb_uio/igb_uio.c:
+   In function ‘igbuio_pci