| Age | Commit message (Collapse) | Author |
|---|
|
Signed-off-by: Armin Kuster <akuster@mvista.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
When selecting SMP, some dependencies are needed, in the case
of a 32 bit build CONFIG_X86_BIGSMP=y is required, but adding that
to a 64 bit build causes warnings to be shown since X86_BIGSMP
requires X86_32 [n] itself, which can only be true for a 32 bit build.
This patch creates a 64 bit version of smp (smp_64), avoiding the
dependecy issues.
[YOCTO #11742]
Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
mohonpeak.scc and mohonpeak32.scc are based on x86.scc and x86_64.scc
which already include smp.scc, so remove the unnecessary include.
[YOCTO #11743]
Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
rangeley.scc and rangeley32.scc are based on x86.scc and x86_64.scc
which already include smp.scc, so remove the unnecessary include.
[YOCTO #11743]
Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
These lines don't belong in the .cfg and cause warnings during
the configme process
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The '+' dont belong here and cause warnings
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Useful for integrity protection of a read-only partition.
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The recent commit accidentally had CONFIG_TCG_TPM twice in the tpm.cfg
file, which triggers a warning when checking the kernel config because
the resulting config only contains the entry once.
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
While there are intel-quark configurations for the KTYPEs standard and
tiny in bsp/intel-common, there's none for the preempt-rt KTYPE.
Trying to build preempt-rt enabled kernels such as linux-yocto-rt for
intel-quark yields a .config having a potentially misconfigured
architecture. More importantly, however, preempt-rt related CONFIG
options are not enabled. Hence, a build of, e.g., linux-yocto-rt, does
not result in a preempt-rt enabled kernel.
This patch qualifies to be (back)ported to other branches than master.
Signed-off-by: Christian Storm <christian.storm@siemens.com>
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Some hardware has a TPM chip and in addition, qemu can emulate it
using swtpm.
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
|
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
|
|
|
commit e498b1662ce9fc156cd2391b06bda9356d5977a3 upstream.
Dear RT folks!
I'm pleased to announce the v4.8.15-rt10 patch set.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git v4.8.15-rt10
The RT patch against v4.8.15 can be found here:
https://cdn.kernel.org/pub/linux/kernel/projects/rt/4.8/patch-4.8.15-rt10.patch.xz
The split quilt queue is available at:
https://cdn.kernel.org/pub/linux/kernel/projects/rt/4.8/patches-4.8.15-rt10.tar.xz
Sebastian
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
[PG: update paths to match yocto-4.8 kernel cache. ]
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
|
commit af8baa079eec1bda7e7d9df85acc65a7bcec28c6 upstream.
Dear RT folks!
I'm pleased to announce the v4.8.14-rt9 patch set.
Changes since v4.8.14-rt8:
- If network interface is removed we move all skbs which are active to
a list and free it later. The hunk where the list was cleaned up was
lost and is back.
- bnx2x and a few others could corrupt their ->poll_list. Patch by
Steven Rostedt.
- A missing RCU section in the workqueue code could lead to a "use after
free" condition if the worqueue was removed. Reported by John Keeping
Known issues
- CPU hotplug got a little better but can deadlock.
The delta patch against v4.8.14-rt9 is appended below and can be found here:
https://cdn.kernel.org/pub/linux/kernel/projects/rt/4.8/incr/patch-4.8.14-rt8-rt9.patch.xz
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git v4.8.14-rt9
The RT patch against v4.8.14 can be found here:
https://cdn.kernel.org/pub/linux/kernel/projects/rt/4.8/patch-4.8.14-rt9.patch.xz
The split quilt queue is available at:
https://cdn.kernel.org/pub/linux/kernel/projects/rt/4.8/patches-4.8.14-rt9.tar.xz
Sebastian
[PG: remove kernel patch fragment from long log, as it confuses
"git-am". Update paths to match yocto-4.8 kernel cache.]
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
|
commit c297bb37b26a1d9f59f5ce2978279e990e1428c5 upstream.
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
[PG: update paths to match yocto-4.8 kernel.]
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
This changes adds 'nat' table in iptables. The netfilter side
is already configured for NAT but iptables config was missing.
Further, CONFIG_IP_NF_TARGET* configured below depend on
CONFIG_IP_NF_NAT but remain disabled unless CONFIG_IP_NF_NAT
is explicitly enabled.
CONFIG_IP_NF_TARGET_MASQUERADE is needed by Connman to
support tethering.
Signed-off-by: Mikko Ylinen <mikko.ylinen@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The 'serial-all' feature doesn't really make sense to begin with, and
certainly isn't required for all quark-derived BSPs, so remove it and
replace it with just the base USB serial support.
If a particular bsp requires more specific support, it should include
it explicitly.
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Separate out base usb serial support so we don't have to include
everything in the serial-all feature, which amounts to unnecessary
bloat.
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
'Default policy' features don't belong in soc features - if needed,
they should be added to '*-standard' or similar.
A representative x1000 platform, the Galileo2, works fine with these
features removed.
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
There's no reason for the x1000 feature to include iwlwifi, amt, iio,
or, uio - they should belong to higher-level configuration, and they
cause unnecessary bloat for those systems that don't need them.
If a particular bsp requires anything included here, it should include
it explicitly.
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
There's no reason for the x1000 feature to include anything from
common-pc, and it causes unnecessary bloat.
If a particular bsp requires anything included here, it should include
it explicitly.
A representative x1000 platform, the Galileo2, works fine without any
of this.
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Quark and tiny have no need or desire to drag around pointless
features like eg20t, so use the common-drivers-32-essential feature
instead of the full common-drivers-32.
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The intel-common-drivers-32 contains features such as eg20t that that
aren't applicable to some platforms such as quark, and unwanted in a
tiny configuration.
Splitting out and reusing an 'essential' subset allows them to include
only those features.
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Add a feature for enabling debug files to be generated by kernel LTO.
To enable LTO debug for the kernel, add (for example):
KERNEL_FEATURES_append_galileo += " features/lto-debug.scc"
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Add features/lto/lto-disable, a feature to disable LTO. This isn't
really needed, since it's the default, but it makes kernel feature
selection for currently incompatible features such as tracing less
confusing - disable by adding (for example):
KERNEL_FEATURES_append_galileo += " features/lto/lto-disable.scc"
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Add a feature allowing the enablement of LTO (Link-Time Optimization)
for the Linux kernel. To enable LTO for the kernel, add (for
example):
KERNEL_FEATURES_append_galileo += " features/lto.scc"
Note that this feature requires special toolchain support (HJ Lu's
Linux binutils and gcc >= 4.9).
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
In case of the DROP policy in the INPUT chain a host using IPv6 still
might need to receive TCP packets for established connections, that is
to have the rule
-A INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
in its INPUT chain of ip6tables. For this feature to work the option
CONFIG_NF_CONNTRACK_IPV6 needs to be enabled.
Signed-off-by: Dmitry Rozhkov <dmitry.rozhkov@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
|
Upstream announce:
[ANNOUNCE] v4.8.11-rt7
Dear RT folks!
I'm pleased to announce the v4.8.11-rt7 patch set.
Changes since v4.8.11-rt6:
- A fix for a race in the futex/rtmutex code which was there since the
very beginning. Reported by David Daney, fixed Thomas Gleixner
- A fix for the kprobe code on ARM by Yang Shi.
- It is no longer possible to force an expedited RCU grace period on
-RT. We had one spot in the network where it was disabled on RT
due to high latencies it caused. Suggested by Luiz Capitulino and
patched by Julia Cartwright.
- Expedited RCU grace periods are now forced during boot which should
speed the boot process (even on -RT).
Known issues
- CPU hotplug got a little better but can deadlock.
The delta patch against 4.8.11-rt6 is appended below and can be found here:
https://cdn.kernel.org/pub/linux/kernel/projects/rt/4.8/incr/patch-4.8.11-rt6-rt7.patch.xz
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git v4.8.11-rt7
The RT patch against 4.8.11 can be found here:
https://cdn.kernel.org/pub/linux/kernel/projects/rt/4.8/patch-4.8.11-rt7.patch.xz
The split quilt queue is available at:
https://cdn.kernel.org/pub/linux/kernel/projects/rt/4.8/patches-4.8.11-rt7.tar.xz
Sebastian
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
|
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
|
|
|
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
1/1 [
Author: "Kexin(Casey) Chen"
Email: Casey.Chen@windriver.com
Subject: aufs: fix compile warning
Date: Tue, 29 Nov 2016 14:14:07 -0800
fs/aufs/debug.h:95:19: warning: comparison of constant '0'
with boolean expression is always false [-Wbool-compare]
if (unlikely((e) < 0)) \
^
fs/aufs/vdir.c:852:2: note: in expansion of macro 'AuTraceErr'
AuTraceErr(!valid);
^~~~~~~~~~
In expansion of AuTraceErr(!valid), comparison of (!valid)
and constant '0' always passes unlikely(x) false. function
'static int seek_vdir(struct file *file, struct dir_context *ctx)'
is to find whether there is a valid vd_deblk following ctx->pos.
return 1 means valid, 0 for not. Change to AuTraceErr(valid - 1)
makes more sense.
Signed-off-by: Kexin(Casey) Chen <Casey.Chen@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
This is incompatible with preempt-rt and would be a mess to fix any
other way. If we were to move CONFIG_LEDS_TRIGGER_CPU to a new feature
such as leds-full, it would require us to add leds-full to every non-rt
BSP wanting leds support, and -rt BSPs would need the feature without
it. Setting "# CONFIG_LEDS_TRIGGER_CPU is not set" also doesn't work, as
it depends on !PREEMPT_RT_BASE, making it completely unavailable for
setting and still giving us a warning in kernel_configcheck.
All this option does is allow CPUs to trigger LEDs based on their usage,
so it is not a major loss anyway.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The newer BMP280 IIO driver appears to support the BMP085 chip as well,
and the old BMP085 driver cannot be enabled at the same time, giving us
configcheck warnings if we try.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Some drivers (e.g. INV_MPU6050_I2C) rely on this, and in most cases
this gets selected automatically, but in some cases its not and it
causes a configcheck warning.
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The option CONFIG_CPU_MIPSR2 is no longer directly selectable (or
is not set'able), so we can get the following warning when building
qemumips64:
Config: CONFIG_CPU_MIPSR2
From: kernel-source/.kernel-meta/configs/standard/mti-malta64/bsp/mti-malta64/mti-malta64-common.cfg
Requested value: # CONFIG_CPU_MIPSR2 is not set
Actual value:
Since this always takes the default value, we can safely drop it from
our configuration fragment.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
1/2 [
Author: Shuah Khan
Email: shuahkh@osg.samsung.com
Subject: fs/nfs: Fix used uninitialized warn in nfs4_slot_seqid_in_use()
Date: Wed, 16 Nov 2016 15:36:39 -0500
commit 0ac84b72c0ed96ace1d8973a06f0120a3b905177 upstream.
Fix the following warn:
fs/nfs/nfs4session.c: In function ‘nfs4_slot_seqid_in_use’:
fs/nfs/nfs4session.c:203:54: warning: ‘cur_seq’ may be used uninitialized in this function [-Wmaybe-uninitialized]
if (nfs4_slot_get_seqid(tbl, slotid, &cur_seq) == 0 &&
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
cur_seq == seq_nr && test_bit(slotid, tbl->used_slots))
~~~~~~~~~~~~~~~~~
Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]
2/2 [
Author: Arnd Bergmann
Email: arnd@arndb.de
Subject: NFSv4.1: work around -Wmaybe-uninitialized warning
Date: Wed, 16 Nov 2016 15:36:40 -0500
commit e84efa32b9d2763fb92e73c8942100d8f55ad4ed upstream.
A bugfix introduced a harmless gcc warning in nfs4_slot_seqid_in_use if
we enable -Wmaybe-uninitialized again:
fs/nfs/nfs4session.c:203:54: error: 'cur_seq' may be used uninitialized in this function [-Werror=maybe-uninitialized]
gcc is not smart enough to conclude that the IS_ERR/PTR_ERR pair results
in a nonzero return value here. Using PTR_ERR_OR_ZERO() instead makes
this clear to the compiler.
Fixes: e09c978aae5b ("NFSv4.1: Fix Oopsable condition in server callback races")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The inclusion of the mei feature was invalid, since it is missing
the "include" keyword .. adding it gets us the features we expect
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
Armin Kuster
Bruce Ashfield
Alejandro Hernandez
Saul Wold
Patrick Ohly
Christian Storm
Paul Gortmaker
Sebastian Andrzej Siewior
Mikko Ylinen
Tom Zanussi
Dmitry Rozhkov
California Sullivan