Bruce, Yocto kernel folks:
Here is the next 5.2.x stable update "extension" primarily created for
the Yocto project, continuing from the first v5.2.22 post-EOL release.
This 5.2.22 release only contains about 22 mainline commits. Rather
than continue the audit of what went into 5.3.8 - I jumped
[Re: v5.2.x - stable updates comprising v5.2.22] On 10/11/2019 (Sun 22:36)
Bruce Ashfield wrote:
> This is merged, that being said .. there are a couple of things that
> could use a second set of eyes.
>
> 1) I had a preempt-rt conflict in fs/libfs.c. It looks like
> scan_positives() was
Bruce, Yocto kernel folks:
Here is the *final* 4.18.x stable update "extension" primarily created
for the Yocto project, continuing from the previous v4.18.44 release.
This final release closes out a run of 25 releases and about 4600
backports since GregKH stopped maintenance at v4.18.20, just
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.42 release.
There are about 125 commits here, based on the commits that were used
in the 4.19.[48/49/50] linux-stable releases.
A note to
[Re: v4.18.x - stable updates comprising v4.18.42] On 25/08/2019 (Sun 22:10)
Bruce Ashfield wrote:
> On Sun, Aug 18, 2019 at 10:14 AM Paul Gortmaker
> wrote:
> >
> > Bruce, Yocto kernel folks:
> >
> > Here is the next 4.18.x stable update "extension" pri
[Re: v4.18.x - stable updates comprising v4.18.42] On 25/08/2019 (Sun 22:10)
Bruce Ashfield wrote:
> On Sun, Aug 18, 2019 at 10:14 AM Paul Gortmaker
> wrote:
> >
> > Bruce, Yocto kernel folks:
> >
> > Here is the next 4.18.x stable update "extension" pri
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.41 release.
There are about 150 commits here, based on the remaining commits that
were used in the 4.19.46/47 stable releases -- but not put
[[linux-yocto] [PATCH] modules: always page-align module section allocations]
On 16/08/2019 (Fri 15:36) zhe...@windriver.com wrote:
It helps maintainers if the version is embedded in the subject, like:
[PATCH v4.18] modules: always page-align module section
> From: Jessica Yu
>
> Some
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.40 release.
There are about 220 commits here, based on commits chosen from what were
used in the 4.19.46/47 stable releases -- plus some TCP
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.39 release.
There are about 260 commits here, based on commits chosen from what were
used in the 4.19.42/44/45 stable releases -- so another
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.38 release.
There are about 180 commits here, based on commits chosen from what were
used in the 4.19.39/40/41 stable releases -- so another
[Re: v4.18.x - stable updates comprising v4.18.38] On 16/05/2019 (Thu 16:47)
Paul Gortmaker wrote:
[...]
> > The conflicts just look like one of the changes is already in my tree ..
> > which
> > IIRC is the case, but it would be great if you could check the la
[Re: v4.18.x - stable updates comprising v4.18.38] On 16/05/2019 (Thu 15:59)
Bruce Ashfield wrote:
>
>
> On Wed, May 15, 2019 at 6:07 PM Paul Gortmaker
> wrote:
>
> Bruce, Yocto kernel folks:
>
> Here is the next 4.18.x stable update "extension" pri
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.37 release.
There is one trivial one line commit to fix a build error on PPC64 from
the MDS patches of v4.18.37 - which was also present in
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.36 release.
There are just over 30 commits here, based only on commits chosen from
what was used in the MDS stable releases that came out
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.35 release.
There are just over 185 commits here, based on commits chosen from what
was used in the 4.19.35 and 4.19.36 stable releases.
I'd
her than a
failure contingency mitigation is broken by design.
Given all that, I decided that the best path forward was to revert
the two of the three chunks of the backport that remain in the -rt
branch, and return us to the pre-4.19.31 merge behaviour for -rt.
Signed-off-by: Paul Gortmaker
diff --git
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.33 release.
There are just over 160 commits here, based on commits chosen from what
was used in the recent 4.19.32 stable release.
That
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.32 release.
There are about 260 commits here, based on commits chosen from what
was used in the recent 4.19.31 stable release. So, yes,
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.30 release.
There are about 165 commits here, based on commits chosen from what
were used in the existing 4.19.29 --> 4.19.30 stable releases.
19.15-rt12).
Reported-by: Yue Tao
Signed-off-by: Paul Gortmaker
diff --git a/drivers/of/base.c b/drivers/of/base.c
index 904c7686f9d7..4a33ef482bcc 100644
--- a/drivers/of/base.c
+++ b/drivers/of/base.c
@@ -106,31 +106,34 @@ static u32 phandle_cache_mask;
/*
* Caller must hold d
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.30 release.
There are about 125 commits here, based on commits chosen from what
were used in the existing 4.19.27 --> 4.19.28 stable releases.
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.29 release.
There are about 245 commits here, based on commits chosen from what
were used in the existing 4.19.22 --> 4.19.26 stable releases.
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.28 release.
There are about 275 commits here, based on commits chosen from what
was used in the existing 4.19.21 stable release that had over
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.27 release.
There are about 140 commits here, based on commits chosen from what
were used in the existing 4.19.19 --> 4.19.20 stable releases.
[[linux-yocto] Modify sysctl.conf] On 14/02/2019 (Thu 11:06) Franz Forstmayr
wrote:
> Hi,
>
> I have a board with more than one ethernet ports, which should get
> connected to the same network, at least for now. I wanted to prevent
> arp flux for my build and appended the procps recipe with
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.26 release.
There are about 215 commits here, based on commits chosen from what
were used in the existing 4.19.16 --> 4.19.18 stable releases,
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.25 release.
This release is slightly different in terms of how the commits were
chosen. Instead of taking references from 4.19.x *stable*
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.24 release.
There are about 125 commits here, based on commits chosen from what
was used in the existing 4.19.15 stable release.
I've put this
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.23 release.
There are about 230 commits here, based on commits chosen from what
was used in existing 4.19.12 to 4.19.14 (inclusive) stable
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
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.21 release.
There are about 250 commits here, based on commits chosen from what
was used in existing 4.19.6 to 4.19.8 stable releases.
And it
Bruce, Yocto kernel folks:
Here is the first 4.18.x stable update "extension" primarily created
for the Yocto project, continuing on top of the v4.18.20 kernel.
As some may already be aware, the v4.18.20 was the final release done
by Greg KH and team, and so just like was done for 4.12.x and
-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
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
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
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/
-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
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
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
(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
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
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
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
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
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
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
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
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
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
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
() (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
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
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
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
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
-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
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
---
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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.
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
[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
[[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
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
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
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
[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.
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
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,
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
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
[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
[[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
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
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
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
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
Signed-off-by: Paul Gortmaker <paul.gortma...@windriver.com>
---
README | 1 +
1 file changed, 1 insertion(+)
diff --git a/README b/README
index 9fdd5eb523df..19c38c3a085a 100644
--- a/README
+++ b/README
@@ -80,6 +80,7 @@ c. Set MACHINE in local.conf to one of the supported
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] 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
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
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
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
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
.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]
1 - 100 of 142 matches
Mail list logo
