Re: [linux-yocto] [PATCH 8/8] meta/common-pc-64: Add USB 3.0 support

[[linux-yocto] [PATCH 8/8] meta/common-pc-64: Add USB 3.0 support] On 06/09/2013 (Fri 15:44) Darren Hart wrote: Add missing xhci-hcd to common-pc-64.scc. At the risk of being a nag, the commit log just repeats what is obvious from patch inspection. I try and encourage people to list three

Re: [linux-yocto] [PATCH 3/8] meta/common-pc: Add common Realtek and Atheros Ethernet drivers

[[linux-yocto] [PATCH 3/8] meta/common-pc: Add common Realtek and Atheros Ethernet drivers] On 06/09/2013 (Fri 15:44) Darren Hart wrote: Add the 8139*, R8169, and ATL1E drivers per popular demand. Are the Atheros things not wireless? Perhaps separate out the generic COTS PCI ethernet cards

Re: [linux-yocto] [PATCH 7/8] meta/common-pc*: Refactor common-pc-64 to reuse common-pc drivers

[[linux-yocto] [PATCH 7/8] meta/common-pc*: Refactor common-pc-64 to reuse common-pc drivers] On 06/09/2013 (Fri 15:44) Darren Hart wrote: Factor out the x86_64 CPU-specific options into common-pc-64-cpu.cfg and move any missing driver CONFIGs into common-pc-drivers.cfg. Reuse the eth, wifi,

Re: [linux-yocto] [PATCHv2 4/4] valleyisland-io: update valleyisland-io.scc file

On 13-12-11 12:17 PM, Darren Hart wrote: On Wed, 2013-12-11 at 12:19 +0800, rebecca.swee.fun.ch...@intel.com wrote: From: Chang, Rebecca Swee Fun rebecca.swee.fun.ch...@intel.com valleyisland-io.scc was updated with new patch added. Signed-off-by: Chang, Rebecca Swee Fun

Re: [linux-yocto] ERROR: Failed to allocate 0x3dbd bytes below 0x800000.

On 13-12-18 11:50 PM, Ravi Rao wrote: Hi All, We have a custom Board which is based on mpc8349EMDS which is based on e300. I got the Toolchain downloaded using poky-dora-10.0.0 project which supports e300 core Now when I cross compile Linux kernel ver 2.6.32 the system boots up and works

Re: [linux-yocto] ERROR: Failed to allocate 0x3dbd bytes below 0x800000.

[Re: [linux-yocto] ERROR: Failed to allocate 0x3dbd bytes below 0x80.] On 19/12/2013 (Thu 15:24) Ravi Rao wrote: Hi Paul, Appreciate the feed back. My responses are in line below.. On 12/19/13 09:30, Paul Gortmaker wrote: On 13-12-18 11:50 PM, Ravi Rao wrote: Hi

Re: [linux-yocto] [PATCH 1/3] x86, kaslr: randomize module base load address

On 14-07-28 10:58 PM, Yang Shi wrote: From: Kees Cook keesc...@chromium.org commit e2b32e6785138d92d2a40e0d0473575c8c7310a2 upstream Unless I missed it, it would be nice if these 3 patches had a 0/3 that had some context about what they are fixing and why they are selected for cherry pick.

Re: [linux-yocto] how to detect unstable builds

On 14-07-30 09:56 AM, Andreas Schultz wrote: Hi, Unstable might be not the right term, but I couldn't think of another. The issue is that two builds on exactly the same build host, produce packages that have different runtime dependencies and also different behaviors. This list is meant

Re: [linux-yocto] [PATCH v3] Meta: add qemuppc64 bsp config

[[linux-yocto] [PATCH v3] Meta: add qemuppc64 bsp config] On 30/08/2014 (Sat 23:03) Armin Kuster wrote: This is the initial meta data for qemu ppc64 bsp that supports the IBM pseries power* arch which is supported in Qemu. V2: Pruned config : Added standard.scc V3: More cleanup :

Re: [linux-yocto] [PATCH] serial, 8250_dw: fix linux-yocto merge build issue since v3.10.48

On 14-10-08 02:39 AM, Ong Boon Leong wrote: There is an build issue in following merge-point: Merge tag 'v3.10.48' into standard/base 60a9d9fc565e4503dbb8705803e83d906afc4ad2 For 8250_dw.c: dw8250_handle_irq() requires the following line to be restored in order to build successfully.

[linux-yocto] [PATCH] 8250/8250_dw: fix compile failure due to stable/Yocto conflict

cause info to commit log.] Signed-off-by: Paul Gortmaker paul.gortma...@windriver.com diff --git a/drivers/tty/serial/8250/8250_dw.c b/drivers/tty/serial/8250/8250_dw.c index 36fe9d9262c0..5caf10ee14b1 100644 --- a/drivers/tty/serial/8250/8250_dw.c +++ b/drivers/tty/serial/8250/8250_dw.c @@ -217,6

Re: [linux-yocto] [PATCH 1/7] workqueue: use manager lock only to protect worker_idr

On 14-12-19 03:43 AM, Zumeng Chen wrote: From: Lai Jiangshan la...@cn.fujitsu.com worker_idr is highly bound to managers and is always/only accessed in manager lock context. So we don't need pool-lock for it. Signed-off-by: Lai Jiangshan la...@cn.fujitsu.com Signed-off-by: Tejun Heo

Re: [linux-yocto] [PATCH v2 06/11] stmicro: Add support for the STMMAC Ethernet controller family

[Re: [PATCH v2 06/11] stmicro: Add support for the STMMAC Ethernet controller family] On 05/07/2015 (Sun 22:30) Saul Wold wrote: On 07/05/2015 08:52 PM, Bruce Ashfield wrote: On 2015-07-01 7:15 PM, Darren Hart wrote: On 7/1/15 4:06 PM, Saul Wold wrote: This is needed for the meta-quark BSP

Re: [linux-yocto] [Asterisk] recipe 13.1.1

On 2015-07-29 09:07 AM, Laurent Joli wrote: Hi everybody, I am try to build an recipe for asterisk 13.1.1 but I have some errors. This list is primarily for kernel development. https://www.yoctoproject.org/tools-resources/community/mailing-lists Paul. -- I will show you my recipe :

Re: [linux-yocto] preempt and meta support in linux-yocto-4.1

On 2015-08-05 03:44 PM, Cristian Bercaru wrote: Hello! Does linux-yocto-4.1 implement all the preempt-rt support in standard/preempt-rt branch? or Does it have a preempt-rt patch, like 3.4, 3.10 and 3.14? It has always been on a branch IIRC, and I don't think we've ever used a monolithic

[linux-yocto] [PULL] kernel-cache; yocto-4.6: stage latest -rt content

.2-rt5 (2016-06-26 18:01:55 -0400) ---- Paul Gortmaker (5): powerpc:drop perf build fix now in mainline treewide: re-export patches autonominated for refresh kver: 4.6 ---> 4.6.1 treewide: re-export patches autonominated for refresh [4.6 --> 4.6.1]

Re: [linux-yocto] [PATCH 23/29] acpi: updated DSDT table for SPI devices.

[[linux-yocto] [PATCH 23/29] acpi: updated DSDT table for SPI devices.] On 05/02/2016 (Fri 06:53) Saul Wold wrote: > From: Ismo Puustinen > > ACPI version 5 assumes SPI devices to be under the SPI bus in the ACPI > definitions. In addition to my comments about the

Re: [linux-yocto] [PATCH 25/29] staging:iio: add support for ADC1x8s102.

[[linux-yocto] [PATCH 25/29] staging:iio: add support for ADC1x8s102.] On 05/02/2016 (Fri 06:53) Saul Wold wrote: > From: Todor Minchev > > Upstream-status: Pending > > Signed-off-by: Saul Wold The patch pending for upstream doesn't have any commit

Re: [linux-yocto] [PATCH 20/29] acpi: added a custom DSDT file.

[[linux-yocto] [PATCH 20/29] acpi: added a custom DSDT file.] On 05/02/2016 (Fri 06:53) Saul Wold wrote: > From: Ismo Puustinen > > The file has fixed GPIO IRQ assignment. > > Upstream-status: Inappropriate, custom firmware > > Signed-off-by: Saul Wold

Re: [linux-yocto] [PATCH 13/29] mfd: core: redo ACPI matching of the children devices

[[linux-yocto] [PATCH 13/29] mfd: core: redo ACPI matching of the children devices] On 05/02/2016 (Fri 06:53) Saul Wold wrote: > From: Andy Shevchenko > > There is at least one board on the market, i.e. Intel Galileo Gen2, that uses > _ADR to distinguish the

Re: [linux-yocto] [PATCH 05/29] i2c: core: fix typo in comment

[[linux-yocto] [PATCH 05/29] i2c: core: fix typo in comment] On 05/02/2016 (Fri 06:53) Saul Wold wrote: > From: Shailendra Verma > > Signed-off-by: Shailendra Verma > Signed-off-by: Wolfram Sang > >

Re: [linux-yocto] [PATCH 01/13] features/debug: add debug-kernel feature

[[linux-yocto] [PATCH 01/13] features/debug: add debug-kernel feature] On 04/02/2016 (Thu 16:25) California Sullivan wrote: > Since EMBEDDED, EXPERT, and DEBUG_KERNEL are being removed from the base > ktype, we can no longer assume DEBUG_KERNEL is enabled. > > Also add this fragment to features

Re: [linux-yocto] [PATCH 06/13] intel-common-drivers.scc: move profiling and latencytop to a new file

[[linux-yocto] [PATCH 06/13] intel-common-drivers.scc: move profiling and latencytop to a new file] On 04/02/2016 (Thu 16:25) California Sullivan wrote: > Profiling and latencytop enable DEBUG_KERNEL, which is no longer a > standard config option. Move these features to a new file called >

Re: [linux-yocto] [PATCH 27/29] gpio-pca953x: add "drive" property.

[[linux-yocto] [PATCH 27/29] gpio-pca953x: add "drive" property.] On 05/02/2016 (Fri 06:53) Saul Wold wrote: > From: Ismo Puustinen > > Galileo gen 2 has support for setting GPIO modes. Expose these > properties through the GPIO sysfs interface. This approach is bit

Re: [linux-yocto] [PATCH 29/29] ARM: dts: am335x-boneblack: configure i2c1 and 2

[[linux-yocto] [PATCH 29/29] ARM: dts: am335x-boneblack: configure i2c1 and 2] On 05/02/2016 (Fri 06:53) Saul Wold wrote: > From: Nishanth Menon > > Configure i2c1 and 2 at 400KHz. Incomplete commit log. It should say why this is required and for what hardware. As it is fairly

Re: [linux-yocto] [PATCH 28/29] iio: light: add support for ROHM BH1710/BH1715/BH1721/BH1750/BH1751 ambient light sensors

[[linux-yocto] [PATCH 28/29] iio: light: add support for ROHM BH1710/BH1715/BH1721/BH1750/BH1751 ambient light sensors] On 05/02/2016 (Fri 06:53) Saul Wold wrote: > From: Tomasz Duszynski > > Add support for ROHM BH1710/BH1715/BH1721/BH1750/BH1751 ambient light > sensors.

Re: [linux-yocto] [PATCH 03/13] ktypes/base: Disable EMBEDDED and DEBUG_KERNEL

[[linux-yocto] [PATCH 03/13] ktypes/base: Disable EMBEDDED and DEBUG_KERNEL] On 04/02/2016 (Thu 16:25) California Sullivan wrote: > DEBUG_KERNEL should not be in the base ktype, as a production kernel > may not necessarily want any debug turned on. EMBEDDED is also removed, > as EMBEDDED selects

Re: [linux-yocto] [PATCH 04/13] base.cfg: disable some HIDs

[[linux-yocto] [PATCH 04/13] base.cfg: disable some HIDs] On 04/02/2016 (Thu 16:25) California Sullivan wrote: > These options default to !EXPERT. Since we removed EXPERT from base, > these became enabled, adding functionality and size that we do not need. I wonder about the "do not need" part.

Re: [linux-yocto] [PATCH 09/13] preempt-rt.scc: inlcude extended ktype instead of standard

[[linux-yocto] [PATCH 09/13] preempt-rt.scc: inlcude extended ktype instead of standard] On 04/02/2016 (Thu 16:25) California Sullivan wrote: > The extended ktype now has the functionality of the previous standard > ktype. To keep preempt-rt's functionality consistent we must include > extended.

Re: [linux-yocto] [PATCH 11/13] CONFIG_I2C_I801: set option to yes in intel-core* bsps

[[linux-yocto] [PATCH 11/13] CONFIG_I2C_I801: set option to yes in intel-core* bsps] On 04/02/2016 (Thu 16:25) California Sullivan wrote: > Without EXPERT, we hit a select on I2C_I801, forcing it to yes and > causing a warning. Set I2C_I801 to yes, and if a bsp wants to build it > as a module,

Re: [linux-yocto] [PATCH 12/13] bsp: add extended common-pc bsps

[[linux-yocto] [PATCH 12/13] bsp: add extended common-pc bsps] On 04/02/2016 (Thu 16:25) California Sullivan wrote: > By using the extended ktype instead of standard, these bsps have the > same functionality of the old -standard bsps. Same here, if we don't use a ktype, vs. say a "devel"

Re: [linux-yocto] [PATCH 01/29] i2c / ACPI: Use 0 to indicate that device does not have interrupt assigned

[Cc trimmed of non-yocto folks to spare them the noise] [Re: [linux-yocto] [PATCH 01/29] i2c / ACPI: Use 0 to indicate that device does not have interrupt assigned] On 08/02/2016 (Mon 09:13) Saul Wold wrote: > On Sun, 2016-02-07 at 17:09 -0500, Paul Gortmaker wrote: > > [[linux-yocto]

Re: [linux-yocto] [PATCH 02/13] ktypes: add extended ktype

[Re: [linux-yocto] [PATCH 02/13] ktypes: add extended ktype] On 10/02/2016 (Wed 20:37) Sullivan, California L wrote: > On 02/08/2016 11:24 AM, Bruce Ashfield wrote: > > On 2016-02-07 6:14 PM, Paul Gortmaker wrote: > >> [[linux-yocto] [PATCH 02/13] ktypes: add extended kt

Re: [linux-yocto] [PATCH v2 00/12] bsp: add developer common-pc BSPs

[[PATCH v2 00/12] bsp: add developer common-pc BSPs] On 12/02/2016 (Fri 17:42) California Sullivan wrote: > By using the developer ktype instead of standard, these BSPs have the > same functionality of the old -standard BSPs. > > Signed-off-by: California Sullivan

[linux-yocto] v4.8.x - stable updates comprising v4.8.18

Bruce, Yocto kernel folks: The current v4.8.17 baseline was released at the same time as v4.9.2 stable. This means that we need to start looking at the v4.9.3 stable content in terms of what makes sense for v4.8.x -- also since v4.9 was completed well before v4.8.17 was done, we know we don't

[linux-yocto] v4.8.x - stable updates comprising v4.8.19

Bruce, Yocto kernel folks: Continuing on the previously released v4.8.18 kernel, we now have the appropriate content from 4.9.4 and 4.9.5 applied on top of that. I've combined the two since 4.9.4 alone only contributed about 50 changesets; adding in the appropriate 4.9.5 content gets us to about

[linux-yocto] v4.8.x - stable updates comprising v4.8.20

Bruce, Yocto kernel folks: Another week, another stable update. Continuing on the previously released v4.8.19 kernel, we now have the appropriate content from 4.9.6 and 4.9.7 applied on top of our latest 4.8 baseline. Once again, I've combined two 4.9.x which results in about 150 backported

Re: [linux-yocto] hid-multitouch driver missing from 4.8.3

[[linux-yocto] hid-multitouch driver missing from 4.8.3] On 28/03/2017 (Tue 16:13) Paul Knopf wrote: > I am using meta-intel BSP's on a board that has a multitouch device, but it > isn't working. I need hd-multitouch.c, specifically. > > I checked the local kernel that was built, but didn't see

[linux-yocto] v4.8.x - stable updates comprising v4.8.21

Bruce, Yocto kernel folks: Here is yet another 4.8.x stable update. Continuing on the previously released v4.8.20 kernel, we now have the appropriate content from 4.9.8 to 4.9.11 applied on top of our latest 4.8 baseline. Once again, I've combined several 4.9.x which results in about 150

Re: [linux-yocto] [PATCH] base.cfg: Add POSIX_TIMERS to fix ping hang

On 2017-04-17 08:31 PM, Saul Wold wrote: > busybox ping was hanging after 1 loop with 4.10.x/4.11.x kernel. > ping was hanging waiting for alarm to expire. > 4.10.x kernel intrdoduced new kernel config CONFIG_POSIX_TIMERS > which needs to be enabled to enable calls timer_create, settimer, > alarm

[linux-yocto] v4.8.x - stable updates comprising v4.8.22

Bruce, Yocto kernel folks: Here is yet another 4.8.x stable update. Continuing on the previously released v4.8.21 kernel, we now have the appropriate content from 4.9.12 to 4.9.14 applied on top of our latest 4.8 baseline. Once again, I've combined several 4.9.x which results in about 170

[linux-yocto] v4.8.x - stable updates comprising v4.8.25

Bruce, Yocto kernel folks: Here is another 4.8.x stable update. Continuing on top of the previously released v4.8.24 kernel, we now have the appropriate content from 4.9.22 to 4.9.24 (inclusive) applied on top of our latest 4.8 baseline. Once again, I've combined several 4.9.x which results in

[linux-yocto] v4.8.x - stable updates comprising v4.8.23

Bruce, Yocto kernel folks: Here is another 4.8.x stable update. Continuing on top of the previously released v4.8.22 kernel, we now have the appropriate content from 4.9.15 to 4.9.17 applied on top of our latest 4.8 baseline. Once again, I've combined several 4.9.x which results in about 165

[linux-yocto] v4.8.x - stable updates comprising v4.8.24

Bruce, Yocto kernel folks: Here is another 4.8.x stable update. Continuing on top of the previously released v4.8.23 kernel, we now have the appropriate content from 4.9.18 to 4.9.21 (inclusive) applied on top of our latest 4.8 baseline. Once again, I've combined several 4.9.x which results in

Re: [linux-yocto] [linux-yocto-4.8][PATCH] mm/workingset.c: fix implicit declaration of __list_lru_init_key

[[linux-yocto-4.8][PATCH] mm/workingset.c: fix implicit declaration of __list_lru_init_key] On 22/09/2017 (Fri 15:48) California Sullivan wrote: > __list_lru_init_key does not exist. We're looking for __list_lru_init as > shown in the patch "26690f5 mm: workingset: fix premature shadow node I

Re: [linux-yocto] [linux-yocto-4.8][PATCH] mm/workingset.c: fix implicit declaration of __list_lru_init_key

[Re: [linux-yocto-4.8][PATCH] mm/workingset.c: fix implicit declaration of __list_lru_init_key] On 28/09/2017 (Thu 10:37) Cal Sullivan wrote: > > > On 09/28/2017 07:53 AM, Paul Gortmaker wrote: > >[[linux-yocto-4.8][PATCH] mm/workingset.c: fix implicit declaration of > &g

Re: [linux-yocto] v4.12.x - stable updates comprising v4.12.15

[v4.12.x - stable updates comprising v4.12.15] On 26/11/2017 (Sun 02:49) Paul Gortmaker wrote: > Bruce, Yocto kernel folks: > > Here is the 1st 4.12.x stable update. Continuing on top of the final > Greg KH released v4.12.14 kernel, we now have the appropriate content > from 4.

[linux-yocto] v4.12.x - stable updates comprising v4.12.15

Bruce, Yocto kernel folks: Here is the 1st 4.12.x stable update. Continuing on top of the final Greg KH released v4.12.14 kernel, we now have the appropriate content from 4.13.4 --> 4.13.5 (inclusive) applied on top of the GregKH baseline. Since the last 4.12 release was done at the same time

[linux-yocto] v4.12.x - stable updates comprising v4.12.18

Bruce, Yocto kernel folks: Here is the 4th 4.12.x stable update "extension" primarily created for the Yocto project. Continuing on top of the previous v4.12.17 kernel, we now have the appropriate content from 4.13.14 --> 4.13.16 (inclusive) applied on top of where we left off previously. It

[linux-yocto] [PATCH yocto 4.12] add UDP patch to fix DHCP regression

Bruce, It turns out that unfortunately a fix found in 4.13.6 was overlooked for addition to 4.12 because the "Fixes:" tag was newer than the 4.12 kernel. However that doesn't allow for the fact that this fix is a fix for a fix we backported to 4.12 already. This is a corner case I can script an

[linux-yocto] v4.8.x - stable updates comprising v4.8.26

Bruce, Yocto kernel folks: Here is another 4.8.x stable update. Continuing on top of the previously released v4.8.25 kernel, we now have the appropriate content from 4.9.25 --> 4.9.29 (inclusive) applied on top of the latest 4.8 baseline. Once again, I've combined several 4.9.x which results in

Re: [linux-yocto] Contribute meta-installer to yocto

On 2017-11-21 12:41 AM, Hongxu Jia wrote: > Hi all, > > Wind River has maintained meta-installer for several years, > and now we want to contribute it to yocto community. > > This layer provides an installation program based on > OE platform. The installation program is anaconda from > fedora,

[linux-yocto] v4.12.x - stable updates comprising v4.12.17

Bruce, Yocto kernel folks: Here is the 3rd 4.12.x stable update "extension" primarily created for the Yocto project. Continuing on top of the previous v4.12.16 kernel, we now have the appropriate content from 4.13.10 --> 4.13.13 (inclusive) applied on top of where we left off previously. It

[linux-yocto] [PATCH 4.12] edac: split scc into enablement and patching (for treegen)

tion files external to the kernel-cache. Note that we also hook the remaining patch chunk into the standard ktype so that "rebase" branches (when created) will faithfully mirror the content merged into the fast forward branches. Signed-off-by: Paul Gortmaker <paul.gortma...@win

[linux-yocto] v4.12.x - stable updates comprising v4.12.24

Bruce, Yocto kernel folks: Here is another 4.12.x stable update "extension" primarily created for the Yocto project, continuing on top of the previous v4.12.23 kernel. There are about 90 commits here, and for the 2nd release in a row, we are with no real multi-commit topics, meaning things are

[linux-yocto] v4.12.x - stable updates comprising v4.12.25

Bruce, Yocto kernel folks: Here is another 4.12.x stable update "extension" primarily created for the Yocto project, continuing on top of the previous v4.12.24 kernel. This is also a good time to note that people using 4.12.x should be getting their plans in place to moving to a newer kernel in

[linux-yocto] v4.12.x - stable updates comprising v4.12.23

Bruce, Yocto kernel folks: Here is another 4.12.x stable update "extension" primarily created for the Yocto project, continuing on top of the previous v4.12.22 kernel. There about 150 commits here, with no real multi-commit topics, meaning things are returning to what is normal for a stable

[linux-yocto] v4.12.x - stable updates comprising v4.12.19

Bruce, Yocto kernel folks: Here is the 5th 4.12.x stable update "extension" primarily created for the Yocto project, continuing on top of the previous v4.12.18 kernel. As indicated in the previous release, the 4.13 source that was being used as a reference for commits we'd want here has been

[linux-yocto] [PATCH 1/2] lockdep: disable self-test

needs to be investigated… Signed-off-by: Sebastian Andrzej Siewior <bige...@linutronix.de> Signed-off-by: Paul Gortmaker <paul.gortma...@windriver.com> --- lib/Kconfig.debug | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug index 1f1cb510

[linux-yocto] [PATCH 4.12-rt 0/2] Two small fixes for rt/base on yocto-4.12

Two small fixlets for real world issues on standard/preempt-rt/base in the linux-yocto-4.12 repository: The 1st fixes an issue where the LTP testcase timerfd01 failed. The second resolves a known issue where AUFS causes false positives of a lockdep fail by claiming there are not enough classes.

[linux-yocto] [PATCH 2/2] hrtimer: Update offset for soft bases

iewior <bige...@linutronix.de> Signed-off-by: Paul Gortmaker <paul.gortma...@windriver.com> --- kernel/time/hrtimer.c | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/kernel/time/hrtimer.c b/kernel/time/hrtimer.c index fd26eade86a3..db396eafc774 100644 --- a/kernel/tim

[linux-yocto] v4.12.x - stable updates comprising v4.12.20

Bruce, Yocto kernel folks: Here is another 4.12.x stable update "extension" primarily created for the Yocto project, continuing on top of the previous v4.12.19 kernel. As hinted at in the previous release, there was a desire to clear the queue of the stand-alone fixes to make room for more

[linux-yocto] v4.12.x - stable updates comprising v4.12.27

Bruce, Yocto kernel folks: Here is another 4.12.x stable update "extension" primarily created for the Yocto project, continuing on top of the previous v4.12.26 kernel. Hopefully people using 4.12.x are already getting their plans in place to moving to a newer kernel in the near future, as the

[linux-yocto] v4.12.x - stable updates comprising v4.12.28

Bruce, Yocto kernel folks: Here is another 4.12.x stable update "extension" primarily created for the Yocto project, continuing on top of the previous v4.12.27 kernel. Hopefully people using 4.12.x have their plans well underway to move to a newer kernel, as I have been indicating for several

[linux-yocto] v4.12.x - stable updates comprising v4.12.29

Bruce, Yocto kernel folks: Here is the final 4.12.x stable update "extension" primarily created for the Yocto project, continuing on top of the previous v4.12.28 kernel. After months of warning, hopefully it comes as no surprise to anyone that this is the last 4.12.x release. There are about

[linux-yocto] v4.12.x - stable updates comprising v4.12.26

Bruce, Yocto kernel folks: Here is another 4.12.x stable update "extension" primarily created for the Yocto project, continuing on top of the previous v4.12.25 kernel. And a reminder: people using 4.12.x should be getting their plans in place to moving to a newer kernel in the near future, as

Re: [linux-yocto] [PULL REQUEST] Intel Axxia updates to linux-yocto-4.12

[Re: [linux-yocto] [PULL REQUEST] Intel Axxia updates to linux-yocto-4.12] On 23/01/2018 (Tue 15:57) Dragomir Daniel wrote: > > On 20.01.2018 04:18, Paul Gortmaker wrote: > >[[linux-yocto] [PULL REQUEST] Intel Axxia updates to linux-yocto-4.12] On > >18/01/2018 (Thu 20:0

Re: [linux-yocto] [PULL REQUEST] Intel Axxia updates to linux-yocto-4.12

[[linux-yocto] [PULL REQUEST] Intel Axxia updates to linux-yocto-4.12] On 18/01/2018 (Thu 20:03) Daniel Dragomir wrote: > Hello Bruce! > > This is the first pull request for Axxia changes on kernel 4.12 which were > ported from our 4.9 Yocto branches. > I checked all the patches with

[linux-yocto] v4.8.x - stable updates comprising v4.8.27

Bruce, Yocto kernel folks: Here is another 4.8.x stable update. Continuing on top of the previously released v4.8.26 kernel, we now have content selected from the 4.9.x series to address some of the high profile CVEs that have garnered a lot of attention this year. One departure of note, is

[linux-yocto] v4.8.x - stable updates comprising v4.8.28

Bruce, Yocto kernel folks: Here is a quick 4.8.x stable update. There are only about 10 patches here as this release is primarily to set the stage for better compatibility with the existing preempt-rt content in Yocto. To that end, I've tested it with the Yocto kernel-cache preempt-rt patches

[linux-yocto] v4.12.x - stable updates comprising v4.12.21

Bruce, Yocto kernel folks: Here is another 4.12.x stable update "extension" primarily created for the Yocto project, continuing on top of the previous v4.12.20 kernel. There about 90 commits here, with the main thing being addition of the mainline retpoline commits based on what was used for

[linux-yocto] v4.12.x - stable updates comprising v4.12.22

Bruce, Yocto kernel folks: Here is another 4.12.x stable update "extension" primarily created for the Yocto project, continuing on top of the previous v4.12.21 kernel. There about 125 commits here, with the main thing being addition of the ARM/64 mainline retpoline commits based on what was used

[linux-yocto] [PATCH 1/5] kthread: convert worker lock to raw spinlock

the work performed under the lock is well-bounded and minimal. Cc: Sebastian Andrzej Siewior Cc: Guenter Roeck Reported-and-tested-by: Steffen Trumtrar Reported-by: Tim Sander Signed-off-by: Julia Cartwright Signed-off-by: Sebastian Andrzej Siewior Signed-off-by: Paul Gortmaker --- include/linux

[linux-yocto] [PATCH 5/5] rt: update localversion to match latest content

RT 5c8919eed1cf kthread: convert worker lock to raw spinlock 5b0efb356a7b (tag: v4.18.12-rt6) v4.18.12-rt6 986610231899 Merge tag 'v4.18.12' into linux-4.18.y-rt Signed-off-by: Paul Gortmaker --- localversion-rt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/localvers

[linux-yocto] [PATCH 3/5] mm/kasan: make quarantine_lock a raw_spinlock_t

of quarantine_lock is confined to quarantine.c and the work performed while the lock is held is limited. Signed-off-by: Clark Williams Signed-off-by: Sebastian Andrzej Siewior Signed-off-by: Paul Gortmaker --- mm/kasan/quarantine.c | 18 +- 1 file changed, 9 insertions(+), 9 deletions

[linux-yocto] [PATCH 2/5] watchdog: prevent deferral of watchdogd wakeup on RT

HRTIMER_MODE_REL_HARD] Signed-off-by: Sebastian Andrzej Siewior Signed-off-by: Paul Gortmaker --- drivers/watchdog/watchdog_dev.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/watchdog/watchdog_dev.c b/drivers/watchdog/watchdog_dev.c index ffbdc4642ea5

[linux-yocto] [PATCH 4/5] tty: serial: pl011: explicitly initialize the flags variable

and resolves the warning. Signed-off-by: Kurt Kanzenbach Signed-off-by: Sebastian Andrzej Siewior Signed-off-by: Paul Gortmaker --- drivers/tty/serial/amba-pl011.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/tty/serial/amba-pl011.c b/drivers/tty/serial/amba-pl011.c

[linux-yocto] [PATCH 4.18-rt 0/5] Add most recent linux-rt-devel updates

initialize the flags variable Paul Gortmaker (1): rt: update localversion to match latest content drivers/tty/serial/amba-pl011.c | 2 +- drivers/watchdog/watchdog_dev.c | 8 include/linux/kthread.h | 2 +- kernel/kthread.c| 42

[linux-yocto] [PATCH 02/10] f2fs: fix to do sanity check with node footer and iblocks

u Signed-off-by: Chao Yu Signed-off-by: Jaegeuk Kim Signed-off-by: Paul Gortmaker --- fs/f2fs/inode.c | 25 +++-- 1 file changed, 23 insertions(+), 2 deletions(-) diff --git a/fs/f2fs/inode.c b/fs/f2fs/inode.c index cf0f944fcaea..75a85b3341a3 100644 --- a/fs/f2fs/inode.c +++ b/fs/f

[linux-yocto] [PATCH 01/10] f2fs: fix to do sanity check with user_block_count

rn div_u64((u64)valid_user_blocks(sbi) * 100, sbi->user_block_count); Missing checks on sbi->user_block_count. Reported-by: Wen Xu Signed-off-by: Chao Yu Signed-off-by: Jaegeuk Kim Signed-off-by: Paul Gortmaker --- fs/f2fs/super.c | 13 - 1 file c

[linux-yocto] [PATCH v4.18 00/10] Collection of mainline backports for CVEs

Bruce, yocto kernel folks, Here is a group of mainline backports to our v4.18 standard/base that address the following CVE items from this year: CVE-2018-5391 CVE-2018-13096 CVE-2018-13097 CVE-2018-14610 CVE-2018-14611 CVE-2018-14612 CVE-2018-14613 I've applied them onto our standard/base at

[linux-yocto] [PATCH 03/10] ip: discard IPv4 datagrams with overlapping segments.

(not yet available uptream). Suggested-by: David S. Miller Signed-off-by: Peter Oskolkov Signed-off-by: Eric Dumazet Cc: Florian Westphal Acked-by: Stephen Hemminger Signed-off-by: David S. Miller Signed-off-by: Paul Gortmaker --- include/uapi/linux/snmp.h | 1 + net/ipv4/ip_fragment.c

[linux-yocto] [PATCH 10/10] btrfs: tree-checker: Verify block_group_item

-by: Paul Gortmaker --- fs/btrfs/tree-checker.c | 100 fs/btrfs/volumes.c | 2 +- fs/btrfs/volumes.h | 2 + 3 files changed, 103 insertions(+), 1 deletion(-) diff --git a/fs/btrfs/tree-checker.c b/fs/btrfs/tree-checker.c index d014af352ce0

[linux-yocto] [PATCH 04/10] net: modify skb_rbtree_purge to return the truesize of all purged skbs.

From: Peter Oskolkov commit 385114dec8a49b5e5945e77ba7de6356106713f4 upstream. Tested: see the next patch is the series. Suggested-by: Eric Dumazet Signed-off-by: Peter Oskolkov Signed-off-by: Eric Dumazet Cc: Florian Westphal Signed-off-by: David S. Miller Signed-off-by: Paul Gortmaker

[linux-yocto] [PATCH 06/10] btrfs: validate type when reading a chunk

combinations. Link: https://bugzilla.kernel.org/show_bug.cgi?id=199839 Reported-by: Xu Wen Reviewed-by: Qu Wenruo Signed-off-by: Gu Jinxiang Signed-off-by: David Sterba Signed-off-by: Paul Gortmaker --- fs/btrfs/volumes.c | 28 1 file changed, 28 insertions(+) diff

[linux-yocto] [PATCH 05/10] ip: use rb trees for IP frag queue.

-by: Jann Horn Reported-by: Juha-Matti Tilli Suggested-by: Eric Dumazet Signed-off-by: Peter Oskolkov Signed-off-by: Eric Dumazet Cc: Florian Westphal Signed-off-by: David S. Miller Signed-off-by: Paul Gortmaker --- include/linux/skbuff.h | 9 +- include/net/inet_frag.h

[linux-yocto] [PATCH 07/10] btrfs: Check that each block group has corresponding chunk at mount time

199837 Reported-by: Xu Wen Signed-off-by: Qu Wenruo Reviewed-by: Su Yue Reviewed-by: David Sterba Signed-off-by: David Sterba Signed-off-by: Paul Gortmaker --- fs/btrfs/extent-tree.c | 28 +++- 1 file changed, 27 insertions(+), 1 deletion(-) diff --git a/fs/btrfs/ex

[linux-yocto] [PATCH 09/10] btrfs: Introduce mount time chunk <-> dev extent mapping check

revent a lot of unexpected behavior (BUG_ON). Reported-by: Xu Wen Link: https://bugzilla.kernel.org/show_bug.cgi?id=200403 Link: https://bugzilla.kernel.org/show_bug.cgi?id=200407 Signed-off-by: Qu Wenruo Reviewed-by: Su Yue Reviewed-by: David Sterba Signed-off-by: David Sterba Signed-off-by

[linux-yocto] [PATCH 08/10] btrfs: Verify that every chunk has corresponding block group at mount time

ff-by: David Sterba Signed-off-by: Paul Gortmaker --- fs/btrfs/extent-tree.c | 58 +- 1 file changed, 57 insertions(+), 1 deletion(-) diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c index 9c0f9d7d4c73..e942f7be 100644 --- a/fs/

[linux-yocto] [PATCH 03/10] powerpc: correct the preempt-lazy assembly

TIF_32BIT and fixup the assembly in one assembly file to get it to compile again. Signed-off-by: Sebastian Andrzej Siewior Signed-off-by: Paul Gortmaker --- arch/powerpc/include/asm/thread_info.h | 4 ++-- arch/powerpc/kernel/entry_64.S | 2 +- 2 files changed, 3 insertions(+), 3

[linux-yocto] [PATCH 06/10] of: allocate / free phandle cache outside of the devtree_lock

the kfree() and kcalloc() while the lock is dropped. Cc: Rob Herring Cc: Frank Rowand Cc: devicet...@vger.kernel.org Signed-off-by: Sebastian Andrzej Siewior Signed-off-by: Paul Gortmaker --- drivers/of/base.c | 22 ++ 1 file changed, 14 insertions(+), 8 deletions(-) diff --git

[linux-yocto] [PATCH 04/10] irqchip/gic-v3-its: Move pending table allocation to init time

From: Marc Zyngier commit 4a0819bb25d12d39c0390636122eefba232596c1 from linux-rt-devel. Signed-off-by: Marc Zyngier [bigeasy: backport commit effe377d415 ("irqchip/gic-v3-its: Move pending table allocation to init time")] Signed-off-by: Sebastian Andrzej Siewior Signed-of

[linux-yocto] [PATCH 02/10] staging: android: vsoc: use hrtimer_init_sleeper_on_stack()

r. Signed-off-by: Sebastian Andrzej Siewior Signed-off-by: Paul Gortmaker --- drivers/staging/android/vsoc.c | 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/drivers/staging/android/vsoc.c b/drivers/staging/android/vsoc.c index 806beda1040b..6c7f666c0e33 100644 ---

[linux-yocto] [PATCH 05/10] Drivers: hv: vmbus: include header for get_irq_regs()

-by: Bernhard Landauer Reported-by: Ralf Ramsauer Signed-off-by: Sebastian Andrzej Siewior Signed-off-by: Paul Gortmaker --- drivers/hv/hyperv_vmbus.h | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/hv/hyperv_vmbus.h b/drivers/hv/hyperv_vmbus.h index 72eaba3d50fc..797f07918197 100644

[linux-yocto] [PATCH 08/10] rcu: Use cpus_read_lock() while looking at cpu_online_mask

() (and we can have multiple jobs running on NUMA systems). Fixes: fcc6354365015 ("rcu: Make expedited GPs handle CPU 0 being offline") Signed-off-by: Sebastian Andrzej Siewior Signed-off-by: Paul Gortmaker --- kernel/rcu/tree_exp.h | 4 ++-- 1 file changed

[linux-yocto] [PATCH 10/10] rt: bump localversion

tch. Signed-off-by: Paul Gortmaker --- localversion-rt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/localversion-rt b/localversion-rt index 6f206be67cd2..0efe7ba1930e 100644 --- a/localversion-rt +++ b/localversion-rt @@ -1 +1 @@ --rt1 +-rt5 -- 2.1

[linux-yocto] [PATCH 09/10] work-simple: drop a shit statement in SWORK_EVENT_PENDING

places). Nevertheless I'm dropping that shift by zero to keep smatch quiet. Cc: Daniel Wagner Signed-off-by: Sebastian Andrzej Siewior Signed-off-by: Paul Gortmaker --- kernel/sched/swork.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/sched/swork.c b/kernel/sched

[linux-yocto] [PATCH 4.18-rt 00/10] upstream updates rt1 --> rt5

to init time Mike Galbraith (1): sched: Allow pinned user tasks to be awakened to the CPU they pinned Paul Gortmaker (1): rt: bump localversion Sebastian Andrzej Siewior (6): staging: android: vsoc: use hrtimer_init_sleeper_on_stack() powerpc: correct the preempt-lazy assembly Drivers

[linux-yocto] [PATCH 01/10] sched: Allow pinned user tasks to be awakened to the CPU they pinned

kernel.org Signed-off-by: Mike Galbraith Signed-off-by: Sebastian Andrzej Siewior Signed-off-by: Paul Gortmaker --- kernel/sched/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c index 530118fbfe21..7d789c1b316b 100644 --- a/ke

[linux-yocto] v4.18.x - stable updates comprising v4.18.23

Bruce, Yocto kernel folks: Here is the next 4.18.x stable update "extension" primarily created for the Yocto project, continuing from the previous v4.18.22 release. There are about 235 commits here, based on commits chosen from what was used in existing 4.19.9 to 4.19.11 (inclusive) stable

  1   2   >