On 10/07/2015 09:02 PM, Dave Chinner wrote:
On Wed, Oct 07, 2015 at 04:20:10PM -0700, Tejun Heo wrote:
Hello, Dave.
On Thu, Oct 08, 2015 at 10:04:42AM +1100, Dave Chinner wrote:
...
As it is, the update race you pointed out is easy to solve with
__this_cpu_cmpxchg rather than _this_cpu_sub (si
Hi,
Thank you very much for your reply and comments.
> -Original Message-
> From: Michal Hocko [mailto:mho...@kernel.org]
> Sent: Thursday, October 08, 2015 7:49 PM
> To: PINTU KUMAR
> Cc: a...@linux-foundation.org; minc...@kernel.org; d...@stgolabs.net;
> koc...@gmail.com; rient...@googl
2015-10-08 18:11 GMT+03:00 Catalin Marinas :
> On Thu, Oct 08, 2015 at 02:09:26PM +0200, Ard Biesheuvel wrote:
>> On 8 October 2015 at 13:23, Andrey Ryabinin wrote:
>> > On 10/08/2015 02:11 PM, Mark Rutland wrote:
>> >> On Thu, Oct 08, 2015 at 01:36:09PM +0300, Andrey Ryabinin wrote:
>> >>> 2015-1
On 08/10/15 16:56, Catalin Marinas wrote:
> On Fri, Oct 02, 2015 at 05:37:49PM +0100, Marc Zyngier wrote:
>> Recent evolutions of the ARM Trusted Firmware have outlined issues
>> when the system is equipped with a GICv3 interrupt controller, but the
>> firmware has decided to restrict it to GICv2 c
On 7/10/2015 12:06 p.m., Namhyung Kim wrote:
Hi Adrian,
On Tue, Oct 6, 2015 at 6:26 PM, Adrian Hunter wrote:
On 06/10/15 12:03, Namhyung Kim wrote:
Hi Adrian,
On Mon, Oct 5, 2015 at 8:29 PM, Adrian Hunter wrote:
On 02/10/15 21:45, Arnaldo Carvalho de Melo wrote:
Em Fri, Oct 02, 2015 at 02
On 10/08, Oleg Nesterov wrote:
>
> On 10/08, Peter Zijlstra wrote:
> >
> > On Thu, Oct 08, 2015 at 04:51:36PM +0200, Oleg Nesterov wrote:
> > > @@ -261,12 +276,8 @@ int stop_two_cpus(unsigned int cpu1, unsigned int
> > > cpu2, cpu_stop_fn_t fn, void *
> > > set_state(&msdata, MULTI_STOP_PREPARE)
Hi Marc,
Thanks for rebasing on top of my latest series.
On Tue, Oct 06 2015 at 08:27 -0600, Marc Titinger wrote:
Devices may register an intermediate retention state into the domain upon
I may agree with the usability of dynamic adding a state to the domain,
but I dont see why a device attac
On 08/10/15 15:43, Catalin Marinas wrote:
On Wed, Oct 07, 2015 at 06:03:34PM +0100, Suzuki K. Poulose wrote:
On 07/10/15 17:36, Catalin Marinas wrote:
On Mon, Oct 05, 2015 at 06:01:55PM +0100, Suzuki K. Poulose wrote:
* (Ref: ARMv8 ARM, Section: "System instruction class encoding overview",
On Thu, Oct 8, 2015 at 9:58 AM, Sudip Mukherjee
wrote:
> If amdgpu_ib_get() fails we returned the error code but we missed
> freeing ib.
>
> Cc: "Christian König"
> Cc: Jammy Zhou
> Cc: Chunming Zhou
> Cc: Alex Deucher
> Cc: "monk.liu"
> Signed-off-by: Sudip Mukherjee
> ---
>
> Sent on 18/09
On Tue, Oct 06 2015 at 08:27 -0600, Marc Titinger wrote:
This patch allows cluster-level C-states to being soaked in as generic
domain power states, in order for the domain governor to chose the most
efficient power state compatible with the device constraints. Similarly,
devices can register pow
On Thu 08-10-15 21:36:24, PINTU KUMAR wrote:
[...]
> Whereas, these OOM logs were not found in /var/log/messages.
> May be we do heavy logging because in ageing test we enable maximum
> functionality (Wifi, BT, GPS, fully loaded system).
If you swamp your logs so heavily that even critical message
On October 08, 2015 14:16, Rob Herring wrote:
> >> > +- dlg,micbias1-lvl : Voltage (mV) for Mic Bias 1
> >> > + [<1600>, <2200>, <2500>, <3000>]
> >> > +- dlg,micbias2-lvl : Voltage (mV) for Mic Bias 2
> >> > + [<1600>, <2200>, <2500>, <3000>]
> >>
> >> Please append the units (-microv
On 10/08/2015 05:44 AM, Hanjun Guo wrote:
> On 10/08/2015 11:21 AM, kernel test robot wrote:
>> FYI, we noticed the below changes on
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>> commit 7494b07ebaae2117629024369365f7be7adc16c3 ("ACPI: add in a
>> bad_madt_entry
From: Rich Felker
The ELF binary loader in binfmt_elf.c requires an MMU, making it
impossible to use regular ELF binaries on NOMMU archs. However, the
FDPIC ELF loader in binfmt_elf_fdpic.c is fully capable as a loader
for plain ELF, which requires constant displacements between LOAD
segments, si
On Thu, Oct 08, 2015 at 05:50:31PM +0200, Pavel Machek wrote:
> Hi!
>
> > On 08/16/2015 08:03 PM, Baolin Wang via device-mainlining wrote:
> > > On 14 August 2015 at 23:27, Greg KH wrote:
> > >> On Fri, Aug 14, 2015 at 05:47:45PM +0800, Baolin Wang wrote:
> > >>> + *
> > >>> + * This program is f
The OFFOUTENABLE bit of the omap PADCONF registers is active low.
The mux code assumed that it was active high and this patch fixes this
problem.
Tested on an AM37x device.
Signed-off-by: Ben Tucker
---
arch/arm/mach-omap2/mux.c | 2 +-
arch/arm/mach-omap2/mux.h | 13 +++--
2 files cha
On Thu, Oct 8, 2015 at 10:42 AM, Alexandre Belloni
wrote:
> Use "qiaodian" as the vendor prefix for QiaoDian Xianshi Corporation in
> device tree compatible strings.
>
> Signed-off-by: Alexandre Belloni
Acked-by: Rob Herring
> ---
>
> Changes in v3:
> -use qiaodian as the vendor prefix as pre
Hello,
On Thu, Oct 8, 2015 at 11:04 AM, Krzysztof Kozlowski
wrote:
> During probe if the regulator could not be enabled, the error exit path
> would still disable it. This could lead to unbalanced counter of
> regulator enable/disable.
>
Do you see a regulator unbalanced reported here during boot
Hello,
On Thu, Oct 8, 2015 at 11:04 AM, Krzysztof Kozlowski
wrote:
> The NULL check in probe's error path is not needed because in that time
> the regulator cannot be NULL (regulator_get() returns valid pointer or
> ERR_PTR).
>
> Signed-off-by: Krzysztof Kozlowski
> ---
Reviewed-by: Alim Akhtar
Hello,
On Thu, Oct 8, 2015 at 11:04 AM, Krzysztof Kozlowski
wrote:
> The 'ret' variable in exynos5440_tmu_initialize() is initialized to 0
> and returned as is. Replace it with direct return statement. This also
> fixes coccinelle warning:
> drivers/thermal/samsung/exynos_tmu.c:611:5-8: Unneeded
On Thu, Oct 08, 2015 at 04:28:34PM +0300, Gleb Natapov wrote:
> On Thu, Oct 08, 2015 at 04:20:04PM +0300, Michael S. Tsirkin wrote:
> > On Thu, Oct 08, 2015 at 03:27:37PM +0300, Gleb Natapov wrote:
> > > On Thu, Oct 08, 2015 at 03:06:07PM +0300, Michael S. Tsirkin wrote:
> > > > On Thu, Oct 08, 201
Hello,
On Thu, Oct 8, 2015 at 11:04 AM, Krzysztof Kozlowski
wrote:
> Thermal core could not read the temperature after registering the
> thermal sensor with thermal_zone_of_sensor_register() because the driver
> was not yet initialized.
>
> The call trace looked like:
> exynos_tmu_probe()
>
On Thu, Oct 8, 2015 at 8:31 AM, Sjoerd Simons
wrote:
> Add devicetree bindings for the spdif tranceiver found on
> found on rk3066, rk3188 and rk3288 SoCs
>
> Signed-off-by: Sjoerd Simons
>
> ---
>
> Changes in v4:
> - Require rockchip,grf on RK3288 as the 8 channel solution has to be
> selecte
Hi Jungseok,
On 08/10/2015:11:32:43 PM, Jungseok Lee wrote:
> On Oct 8, 2015, at 7:25 PM, Pratyush Anand wrote:
> > Hi Jungseok,
>
> Hi Pratyush,
>
> >
> > On 07/10/2015:03:28:11 PM, Jungseok Lee wrote:
> >> Currently, kernel context and interrupts are handled using a single
> >> kernel stack n
perf currently fails to link on all architectures other than arm,
arm64 and x86:
tools/perf/libperf.a(libperf-in.o): In function `parse_regs':
tools/perf/util/parse-regs-options.c:28: undefined reference to
`sample_reg_masks'
tools/perf/util/parse-regs-options.c:28: undefined reference to
`sampl
On Thu, 8 Oct 2015, Vladimir Davydov wrote:
> do_kmem_cache_create, do_kmem_cache_shutdown, and do_kmem_cache_release
> sound awkward for static helper functions that are not supposed to be
> used outside slab_common.c. Rename them to create_cache, shutdown_cache,
> and release_caches, respectivel
Some host adapters (e.g. Hyper-V storvsc) are known for not respecting the
SPC-2/3/4 requirement for 'INQUIRY data (see table ...) shall contain at
least 36 bytes'. As a result we get tons on 'scsi 0:7:1:1: scsi scan:
INQUIRY result too short (5), using 36' messages on console. This can be
problema
On Thu, 08 Oct 2015, Sergey Senozhatsky wrote:
>+/*
>+ * This task may be accessing a foreign mm via (for example)
>+ * get_user_pages()->find_vma(). The vmacache is task-local and this
>+ * task's vmacache pertains to a different mm (ie, its own). There is
>+ * nothing we can do here.
>+ *
>+
On Wed, Oct 07, 2015 at 02:36:41PM +, Sarbojit Ganguly wrote:
> Please have a look at this patch, please let me know if any modification
> is required.
> I have also submitted the same in your patch system.
There are some problems with the version in the patch system[1]:
(1) You still have
Hi,
i have an additional question regarding the Open Drain setting.
The register is currently impelemented as a read/write register
which means the pin mode is configurable by software to
Push Pull or Open Drain.
There is also the possiblity (normal way) that the HW (FPGA) configures
each pin to
The main goal of this patchset is to ensure that devices probing will not
happen during system transition to low power states like suspend or
hibernation, because it is unsafe [1] and system behavior will be
unpredictable in this case (for example: after successful probe the device
potentially has
Now wait_for_device_probe() waits for currently executing probes to finish,
but it doesn't take into account deferred probing mechanism. As result,
nothing prevents deferred probe workqueue to continue probing devices right
after wait_for_device_probe() is finished.
Hence, lest ensure deferred pro
It is unsafe [1] if probing of devices will happen during suspend or
hibernation and system behavior will be unpredictable in this case.
So, lets prohibit device's probing in dpm_prepare() and defer their
probing instead. The normal behavior will be restored in
dpm_complete().
This patch introduce
On Thu, Oct 08, 2015 at 07:43:04PM +0300, Michael S. Tsirkin wrote:
> On Thu, Oct 08, 2015 at 04:28:34PM +0300, Gleb Natapov wrote:
> > On Thu, Oct 08, 2015 at 04:20:04PM +0300, Michael S. Tsirkin wrote:
> > > On Thu, Oct 08, 2015 at 03:27:37PM +0300, Gleb Natapov wrote:
> > > > On Thu, Oct 08, 201
From: Colin Ian King
The size and value arguments are swapped in the call to memset
effectively making it a no-op because of the zero size. Swap
these arguments around to do the memset correctly.
Signed-off-by: Colin Ian King
---
drivers/dma/zx296702_dma.c | 2 +-
1 file changed, 1 insertion(
On Wed, Oct 07, 2015 at 03:18:09PM -0700, Kees Cook wrote:
> On Wed, Oct 7, 2015 at 2:46 AM, Tycho Andersen
> wrote:
> > This patch adds support for dumping a process' (classic BPF) seccomp
> > filters via ptrace.
> >
> > PTRACE_SECCOMP_GET_FILTER allows the tracer to dump the user's classic BPF
>
On Monday, October 05, 2015 02:45:41 PM Sangwoo wrote:
> The size of struct file_security_struct is 16byte at my setup.
> But, the real allocation size for per each file_security_struct
> is 64bytes in my setup that kmalloc min size is 64bytes
> because ARCH_DMA_MINALIGN is 64.
>
> This allocation
Hi!
> > > * This program is free software; you can redistribute it and/or modify
> > > * it under the terms of the GNU General Public License version 2 as
> > > * published by the Free Software Foundation.
> >
> > Please, keep it V2 or later, if you can. It makes sharing code with U-Boot
> > (fo
On 10/08, Oleg Nesterov wrote:
>
> + * We do not want to migrate to inactive CPU. FIXME: move this
> + * into the caller.
>*/
> if (!cpu_active(cpu1) || !cpu_active(cpu2)) {
> preempt_enable();
Of course, this comment is indeed wrong, thanks. Please see V2.
-
Eric Dumazet wrote...
[ commit 83fccfc3940c4a2db90fd7e7079f5b465cd8c6af ]
> It definitely should help !
Yesterday, I've experienced issues somewhat similar to this, but I'm
not entirely sure:
Four of five systems running 4.1.9 stopped working. No reaction on
network, keyboard, serial console. I
On Sat 03 Oct 09:55 PDT 2015, Marcel Holtmann wrote:
> Hi Bjorn,
>
[..]
> >> Especially the kbuild test robot complained loudly.
> >>
> >
> > Sorry, I forgot to mention in the patch that the patch depends on the
> > qcom_smd_id patch - that's available in linux-next. I will take another
> > look,
On Thu, Oct 08, 2015 at 08:33:51AM -0700, Paul E. McKenney wrote:
> > > o CPU B therefore moves up the tree, acquiring the parent
> > > rcu_node structures' ->lock. In so doing, it forces full
> > > ordering against all prior RCU read-side critical sections
> > > of all CPUs corresponding t
The clocksource does not provide clocksource_register() function since
f893598 commit (clocksource: Mostly kill clocksource_register()), so
let's remove unnecessary information about this function from a comment.
Signed-off-by: Alexander Kuleshov
Suggested-by: Herbert Xu
---
crypto/jitterentrop
On Thu, Oct 08, 2015 at 07:04:05PM +0200, Pavel Machek wrote:
> Hi!
>
> > > > * This program is free software; you can redistribute it and/or modify
> > > > * it under the terms of the GNU General Public License version 2 as
> > > > * published by the Free Software Foundation.
> > >
> > > Please,
On 10/08/2015 05:01 AM, K. Y. Srinivasan wrote:
From: Denis V. Lunev
K.Y.,
there is one subtle thing in this submission. You have changed "From:"
field in comparison with the original letter. I have submitted
the patch with "From: Andrey Smetanin "
In this case Author: in the resulted git mai
Hi
On Mon, Oct 5, 2015 at 5:55 PM, wrote:
> From: Stephen Chandler Paul
>
> Debugging input devices, specifically laptop touchpads, can be tricky
> without having the physical device handy. Here we try to remedy that
> with userio. This module allows an application to connect to a character
> d
On 08/10/15 15:45, Christoffer Dall wrote:
On Wed, Oct 07, 2015 at 10:26:14AM +0100, Marc Zyngier wrote:
On 07/10/15 09:26, Christoffer Dall wrote:
Hi Suzuki,
I just had a chat with Catalin, who did shed some light on this.
It all has to do with rounding up. What you would like to have her
On Thu, 8 Oct 2015, Grygorii Strashko wrote:
> It is unsafe [1] if probing of devices will happen during suspend or
> hibernation and system behavior will be unpredictable in this case.
> So, lets prohibit device's probing in dpm_prepare() and defer their
s/lets/let's/, and same for the comment i
On Thu, Oct 08, 2015 at 08:39:58AM -0700, David Daney wrote:
> On 10/08/2015 08:18 AM, Arnd Bergmann wrote:
> >On Thursday 08 October 2015 17:11:32 Arnd Bergmann wrote:
> --- a/Documentation/devicetree/bindings/pci/host-generic-pci.txt
> +++ b/Documentation/devicetree/bindings/pci/host-gene
On Thu, Oct 08, 2015 at 10:07:44AM -0700, Bjorn Andersson wrote:
> On Sat 03 Oct 09:55 PDT 2015, Marcel Holtmann wrote:
>
> > Hi Bjorn,
> >
> [..]
> > >> Especially the kbuild test robot complained loudly.
> > >>
> > >
> > > Sorry, I forgot to mention in the patch that the patch depends on the
>
On Thu, Oct 08, 2015 at 06:22:34PM +0100, Suzuki K. Poulose wrote:
> On 08/10/15 15:45, Christoffer Dall wrote:
> >On Wed, Oct 07, 2015 at 10:26:14AM +0100, Marc Zyngier wrote:
> >>I just had a chat with Catalin, who did shed some light on this.
> >>It all has to do with rounding up. What you would
> -Original Message-
> From: Denis V. Lunev [mailto:d...@openvz.org]
> Sent: Thursday, October 8, 2015 10:20 AM
> To: KY Srinivasan ; gre...@linuxfoundation.org; linux-
> ker...@vger.kernel.org; de...@linuxdriverproject.org; o...@aepfle.de;
> a...@canonical.com; vkuzn...@redhat.com; jasow
On 10/08/2015 08:28 PM, KY Srinivasan wrote:
-Original Message-
From: Denis V. Lunev [mailto:d...@openvz.org]
Sent: Thursday, October 8, 2015 10:20 AM
To: KY Srinivasan ; gre...@linuxfoundation.org; linux-
ker...@vger.kernel.org; de...@linuxdriverproject.org; o...@aepfle.de;
a...@canoni
On Thu, 08 Oct 2015, Bueso wrote:
Thinking a bit more about it, we don't want to be making vmacache_valid_mm()
visible, as users should only stick to vmacache_valid() calls.
^^ s/vmacache_valid/vmacache_update
(cache validity is always internal, obviously
Hi,
On Wed, Oct 7, 2015 at 5:48 PM, Douglas Anderson wrote:
> In (usb: dwc2: reset dwc2 core before dwc2_get_hwparams()) we added an
> extra reset to the probe path for the dwc2 USB controllers. This
> allowed proper detection of parameters even if the firmware had already
> used the USB part.
>
On 6 October 2015 at 03:22, Marcin Wojtas wrote:
> From: Nadav Haklai
>
> According to 'FE-2946959' erratum the clock inversion option is
> needed to support slow frequencies when the card input hold time
> requirement is high. This setting is not required for high speed
> MMC and might cause tim
On Thu, Oct 1, 2015 at 1:44 PM, Luis R. Rodriguez
wrote:
> From: David Howells
>
> We'll want to reuse this same code later in order to
> read two separate types of file contents. This generalizes
> fw_read_file() for reading a file rebrands it as fw_read_file().
Er, maybe that should read "...f
On 6 October 2015 at 03:22, Marcin Wojtas wrote:
> In case of armada_38x_quirks error, all clocks should be cleaned-up, same
> as after mv_conf_mbus_windows failure.
>
> Signed-off-by: Marcin Wojtas
> Cc: # v4.2
Thanks, applied for fixes!
Kind regards
Uffe
> ---
> drivers/mmc/host/sdhci-pxav
On 6 October 2015 at 03:22, Marcin Wojtas wrote:
> From: Nadav Haklai
>
> shci-pxav3 driver is enabling by default the
> SDHCI_QUIRK_CAP_CLOCK_BASE_BROKEN quirk. However this quirk is not
> required for Armada 38x and leads to wrong clock setting in the divider.
>
> Signed-off-by: Nadav Haklai
>
On Thu, Oct 08, 2015 at 08:01:21PM +0300, Gleb Natapov wrote:
> On Thu, Oct 08, 2015 at 07:43:04PM +0300, Michael S. Tsirkin wrote:
> > On Thu, Oct 08, 2015 at 04:28:34PM +0300, Gleb Natapov wrote:
> > > On Thu, Oct 08, 2015 at 04:20:04PM +0300, Michael S. Tsirkin wrote:
> > > > On Thu, Oct 08, 201
On Wed, Oct 7, 2015 at 3:25 AM, Daniel Borkmann wrote:
> On 10/07/2015 11:46 AM, Tycho Andersen wrote:
>>
>> This patch adds support for dumping a process' (classic BPF) seccomp
>> filters via ptrace.
>>
>> PTRACE_SECCOMP_GET_FILTER allows the tracer to dump the user's classic BPF
>> seccomp filte
On Wed, Oct 7, 2015 at 4:49 PM, Alexei Starovoitov wrote:
> On 10/7/15 3:22 PM, Kees Cook wrote:
>>>
>>> Yes, I agree with you that there would be a CVE regardless. I still
>>> >like the option of configurable access, not a big fan of the sysctl
>>> >either. Thinking out loudly, what about a Kconf
On Wed, Oct 7, 2015 at 10:23 PM, Alexei Starovoitov wrote:
> In order to let unprivileged users load and execute eBPF programs
> teach verifier to prevent pointer leaks.
> Verifier will prevent
> - any arithmetic on pointers
> (except R10+Imm which is used to compute stack addresses)
> - compari
On Wed, Oct 7, 2015 at 10:23 PM, Alexei Starovoitov wrote:
> Add new tests samples/bpf/test_verifier:
>
> unpriv: return pointer
> checks that pointer cannot be returned from the eBPF program
>
> unpriv: add const to pointer
> unpriv: add pointer to pointer
> unpriv: neg pointer
> checks that
On Thu, Oct 08, 2015 at 07:12:03PM +0200, Peter Zijlstra wrote:
> On Thu, Oct 08, 2015 at 08:33:51AM -0700, Paul E. McKenney wrote:
>
> > > > o CPU B therefore moves up the tree, acquiring the parent
> > > > rcu_node structures' ->lock. In so doing, it forces full
> > > > or
This series enables building all the dtb files in the kernel mostly
independent of the kernel config. The option is only dependent on
COMPILE_TEST, OF, and the new OF_ALL_DTBS options. This ensures that
allyesconfig builds can build all dtb files although most arches have to
build "dtbs" target
Enable building all dtb files when CONFIG_OF_ALL_DTBS is enabled. The dtbs
are not really dependent on a platform being enabled or any other kernel
config, so for testing coverage it is convenient to build all of the dtbs.
In order to only build dtbs, this option can be used by creating an
allno.c
Enable building all dtb files when CONFIG_OF_ALL_DTBS is enabled. The dtbs
are not really dependent on a platform being enabled or any other kernel
config, so for testing coverage it is convenient to build all of the dtbs.
This builds all dts files in the tree, not just targets listed.
Signed-off-
Enable building all dtb files when CONFIG_OF_ALL_DTBS is enabled. The dtbs
are not really dependent on a platform being enabled or any other kernel
config, so for testing coverage it is convenient to build all of the dtbs.
This builds all dts files in the tree, not just targets listed. This
is simp
On 10/8/15 10:46 AM, Kees Cook wrote:
samples/bpf/libbpf.h|8 +
> samples/bpf/test_verifier.c | 357
+--
Instead of living in samples/ could these be moved and hooked up to
tools/testing/selftests/ instead?
as a follow up patch. yes. of co
Enable building all dtb files when CONFIG_OF_ALL_DTBS is enabled. The dtbs
are not really dependent on a platform being enabled or any other kernel
config, so for testing coverage it is convenient to build all of the dtbs.
This builds all dts files in the tree, not just targets listed. This
is simp
Enable building all dtb files when CONFIG_OF_ALL_DTBS is enabled. The dtbs
are not really dependent on a platform being enabled or any other kernel
config, so for testing coverage it is convenient to build all of the dtbs.
This builds all dts files in the tree, not just targets listed.
Signed-off-
Enable building all dtb files when CONFIG_OF_ALL_DTBS is enabled. The dtbs
are not really dependent on a platform being enabled or any other kernel
config, so for testing coverage it is convenient to build all of the dtbs.
This builds all dts files in the tree, not just targets listed.
Supporting
Enable building all dtb files when CONFIG_OF_ALL_DTBS is enabled. The dtbs
are not really dependent on a platform being enabled or any other kernel
config, so for testing coverage it is convenient to build all of the dtbs.
This builds all dts files in the tree, not just targets listed.
Signed-off-
Enable building all dtb files when CONFIG_OF_ALL_DTBS is enabled. The dtbs
are not really dependent on a platform being enabled or any other kernel
config, so for testing coverage it is convenient to build all of the dtbs.
This builds all dts files in the tree, not just targets listed.
Signed-off-
Use dtb-y and always make variables to build dtbs instead of explicit
dtbs rule. This is in preparation to support building all dtbs.
Signed-off-by: Rob Herring
Cc: James Hogan
Cc: linux-me...@vger.kernel.org
---
arch/metag/Makefile | 2 +-
arch/metag/boot/dts/Makefile | 6 +-
2 fi
Enable building all dtb files when CONFIG_OF_ALL_DTBS is enabled. The dtbs
are not really dependent on a platform being enabled or any other kernel
config, so for testing coverage it is convenient to build all of the dtbs.
This builds all dts files in the tree, not just targets listed.
Signed-off-
Use common rules and dtb-y and always make variables to build dtbs
instead of explicit dtbs rule. Add the missing script dependencies as
well.
This is in preparation to support building all dtbs.
Signed-off-by: Rob Herring
Cc: Ley Foon Tan
Cc: nios2-...@lists.rocketboards.org
---
arch/nios2/Ma
Enable building all dtb files when CONFIG_OF_ALL_DTBS is enabled. The dtbs
are not really dependent on a platform being enabled or any other kernel
config, so for testing coverage it is convenient to build all of the dtbs.
This builds all dts files in the tree, not just targets listed.
Signed-off-
Use dtb-y and always make variables to build dtbs instead of explicit
dtbs rule. This is in preparation to support building all dtbs.
Signed-off-by: Rob Herring
Cc: Vineet Gupta
---
arch/arc/Makefile | 2 +-
arch/arc/boot/dts/Makefile | 4 ++--
2 files changed, 3 insertions(+), 3 delet
On Thu, Oct 08, 2015 at 08:39:10PM +0300, Michael S. Tsirkin wrote:
> On Thu, Oct 08, 2015 at 08:01:21PM +0300, Gleb Natapov wrote:
> > On Thu, Oct 08, 2015 at 07:43:04PM +0300, Michael S. Tsirkin wrote:
> > > On Thu, Oct 08, 2015 at 04:28:34PM +0300, Gleb Natapov wrote:
> > > > On Thu, Oct 08, 201
On Thu, Oct 1, 2015 at 1:44 PM, Luis R. Rodriguez
wrote:
> diff --git a/include/linux/sysdata.h b/include/linux/sysdata.h
> new file mode 100644
> index ..a69cf5ef082c
> --- /dev/null
> +++ b/include/linux/sysdata.h
> @@ -0,0 +1,208 @@
> +#ifndef _LINUX_SYSDATA_H
> +#define _LINUX_SYSD
Em Thu, Oct 08, 2015 at 05:53:05PM +0100, Ben Hutchings escreveu:
> perf currently fails to link on all architectures other than arm,
> arm64 and x86:
This was fixed recently, merged already, check:
https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?h=perf/urgent&id=9fb4765451f22c5e
+Russell
On 17 September 2015 at 10:16, Ludovic Desroches
wrote:
> The Atmel sdhci device needs a new quirk. sdhci_set_clock set the Clock
> Control Register to 0 before computing the new value and writing it.
> It disables the internal clock which causes a reset mecanism. If we
> write the new v
On Thu, Oct 08, 2015 at 08:19:03AM -0700, Paul E. McKenney wrote:
> On Thu, Oct 08, 2015 at 05:12:42PM +0200, Peter Zijlstra wrote:
> > On Thu, Oct 08, 2015 at 08:06:39AM -0700, Paul E. McKenney wrote:
> > > Please see below for the fixed version. Thoughts?
> >
> > > + __releases(rnp->lock) /* Bu
Improve consistency by reorganizing the code to use the same constructs
as do_close_on_exec.
Get rid of xchg of the file pointer. Since the table is about to be
freed there is no reason to NULLify the slot.
Get rid of the file NULL check. At this stage a bit set is supposed to
guarantee the slot
To avoid the confusion, let me repeat that I am not arguing with
this change, perhaps it makes sense too.
But unless I missed something it is not really correct and can't
fix the problem. So I still think the series I sent should be
applied first.
On 10/07, Peter Zijlstra wrote:
> static int sch
* Borislav Petkov wrote:
> On Thu, Oct 08, 2015 at 08:00:24AM -0700, Arjan van de Ven wrote:
> > I would like the success message to be there.
> > From an automated testing perspective (for the distro I work on for
> > example),
>
> Is that particular success message important? I mean, if we s
SIOCSIWAP (airo_set_wap) affects scan: only the AP specified by
SIOCSIWAP is present in scan results.
This makes NetworkManager work for the first time but then unable to
find any other APs.
Clear APList before starting scan and set it back after scan completes
to work-around the problem.
Signed
Instead of dynamically allocating APList, make it a member of struct
airo_info to always track state of APList_rid.
This simplifies suspend/resume and allows removal of readAPListRid.
Signed-off-by: Ondrej Zary
---
drivers/net/wireless/airo.c | 57 +++
1
On Thu, Oct 8, 2015 at 7:53 PM, Rob Herring wrote:
> Enable building all dtb files when CONFIG_OF_ALL_DTBS is enabled. The dtbs
> are not really dependent on a platform being enabled or any other kernel
> config, so for testing coverage it is convenient to build all of the dtbs.
> This builds all
On 10/08/2015 04:19 AM, Srinivas Kandagatla wrote:
> This patch enables spi buses on low speed and high speed expansion
> connectors on DB410C
>
> Signed-off-by: Srinivas Kandagatla
> ---
> arch/arm64/boot/dts/qcom/apq8016-sbc.dtsi | 10 ++
> 1 file changed, 10 insertions(+)
>
> diff --gi
On 10/08/2015 04:19 AM, Srinivas Kandagatla wrote:
> diff --git a/arch/arm64/boot/dts/qcom/msm8916.dtsi
> b/arch/arm64/boot/dts/qcom/msm8916.dtsi
> index 85f7bee..d49ac37 100644
> --- a/arch/arm64/boot/dts/qcom/msm8916.dtsi
> +++ b/arch/arm64/boot/dts/qcom/msm8916.dtsi
> @@ -233,6 +233,22 @@
>
Hi Alexei,
On Thu, Oct 8, 2015, at 07:23, Alexei Starovoitov wrote:
> The feature is controlled by sysctl kernel.unprivileged_bpf_disabled.
> This toggle defaults to off (0), but can be set true (1). Once true,
> bpf programs and maps cannot be accessed from unprivileged process,
> and the toggle
linux_spi_write(), linux_spi_read(), linux_spi_write_read():
nwi->io_func.u.spi.spi_tx = linux_spi_write;
nwi->io_func.u.spi.spi_rx = linux_spi_read;
nwi->io_func.u.spi.spi_trx = linux_spi_write_read;
are expected to accept arguments of 'u8 *', u32 types:
struct {
int (*s
A check using 'sparse' shows warnings in linux_wlan_spi.c:
drivers/staging/wilc1000/linux_wlan_spi.c:43:19: warning: symbol 'wilc_spi_dev'
was not declared. Should it be static?
drivers/staging/wilc1000/linux_wlan_spi.c:71:19: warning: symbol 'wilc_bus' was
not declared. Should it be static?
dri
After moving PIR to IRR, the interrupt needs to be delivered manually.
Reported-by: Paolo Bonzini
Cc:
Signed-off-by: Radim Krčmář
---
v2: completely rewritten
arch/x86/kvm/lapic.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c
index 944b38a5
KVM uses eoi_exit_bitmap to track vectors that need an action on EOI.
The problem is that IOAPIC can be reconfigured while an interrupt with
old configuration is pending and eoi_exit_bitmap only remembers the
newest configuration; thus EOI from the pending interrupt is not
recognized.
(Reconfigur
v2:
* rewritten [1/2] and
* refactored [2/2], all thanks to Paolo's comments
This problem is not fixed for split userspace part as I think that it
would be better to solve that by excluding edge interrupts from
eoi_exit_bitmap (see the next patch in kvm-list for discussion).
Radim Krčmář (2):
Hi!
I noticed that drivers/staging/wilc1000/Kconfic defines:
config WILC1000_DYNAMICALLY_ALLOCATE_MEMROY
bool "Dynamically allocate memory in real time"
---help---
This choice supports dynamic allocation of the memory
for the receive buffer. The driver will all
601 - 700 of 1105 matches
Mail list logo
