On 2016/10/4 8:07, Michal Nazarewicz wrote:
> ffs_func_eps_disable is called from atomic context so it cannot sleep
> thus cannot grab a mutex. Change the handling of epfile->read_buffer
> to use non-sleeping synchronisation method.
>
> Reported-by: Chen Yu
> Signed-off-by: Michał Nazarewicz
>
Le 07/10/2016 à 22:58, Christophe JAILLET a écrit :
Size used with 'dma_alloc_coherent()' and 'dma_free_coherent()' should be
consistent.
Here, the size of a pointer is used in dma_alloc... and the size of the
pointed structure is used in dma_free...
This has been spotted with coccinelle, usin
On Fri, 2016-10-07 at 14:37 -0700, Linus Torvalds wrote:
> On Fri, Oct 7, 2016 at 2:06 PM, Linus Torvalds
> wrote:
> >
> > And btw, even without an explicit KERN_, you should still not
> > get any interleaving. Only an _explicit_ KERN_CONT should cause
> > interleaving
>
>
> Btw, note the "shou
In MADT, the 0xff is an invalid local APIC id.
When the kernel uses both the local APIC id and x2apic id, it may
affect x2apic.
Only add validation when the kernel parse the local APIC ids.
Reported-by: Yinghai Lu
Signed-off-by: Dou Liyang
---
arch/x86/kernel/acpi/boot.c | 4
1 file chan
The patches are for the problem which is in below link.
https://lkml.org/lkml/2016/10/4/39
Dou Liyang (2):
x86/acpi: Fix the local APIC id validation in case of 0xff
x86/acpi: Fix error handling steps in parsing the lapic/x2apic entry
arch/x86/kernel/acpi/boot.c | 35 +++
Originally, in acpi_parse_x2apic(), when the apic_id is invalid and
enabled is false, the acpi_register_lapic() also can be executed.
This does not make sense.
Optimize the decision logic to avoid performing meaningless operations
if the apic_id is invalid.
Signed-off-by: Dou Liyang
---
arch/x8
Use tabs instead of spaces.
Signed-off-by: Peter Griffin
Acked-by: Lee Jones
---
drivers/gpu/drm/virtio/Kconfig | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/virtio/Kconfig b/drivers/gpu/drm/virtio/Kconfig
index e1afc3d..81d1807 100644
--- a/drivers/g
On Fri, Oct 07, 2016 at 03:38:23PM -0400, Joseph Salisbury wrote:
> Hello Peter,
>
> A kernel bug report was opened against Ubuntu [0]. After a kernel
> bisect, it was found that reverting the following commit resolved this bug:
>
> commit 3d30544f02120b884bba2a9466c87dba980e3be5
> Author: Peter
On Friday, October 07, 2016 5:01 AM Chris Friesen
>
> I have Linux host running as a kvm hypervisor. It's running CentOS. (So the
> kernel is based on 3.10 but with loads of stuff backported by RedHat.) I
> realize this is not a mainline kernel, but I was wondering if anyone is aware
> of
> si
On Fri, Oct 07, 2016 at 07:26:36PM -0400, Jeff Layton wrote:
> Well spotted. Yeah, I think you're right. The assertion is this:
>
> percpu_rwsem_assert_held(&file_rwsem);
>
> I'm guessing this is probably fallout from the lglock to rwsem
> conversion (commit aba376607383).
>
> From a quick
> I am testing 4.8 on my sparcs and got this on Sun V210 (sparc64). This
> is reproducible. 4.8.0-rc3-00013 did not have this problem, will bisect
> when I get some time.
That did not go well - bisect found the following commit but that does
not seem to be related at all. So probably the reprod
* Peter Zijlstra wrote:
> On Fri, Oct 07, 2016 at 03:38:23PM -0400, Joseph Salisbury wrote:
> > Hello Peter,
> >
> > A kernel bug report was opened against Ubuntu [0]. After a kernel
> > bisect, it was found that reverting the following commit resolved this bug:
> >
> > commit 3d30544f02120b8
On Mon, Sep 26, 2016 at 02:26:49PM +0800, Peter Chen wrote:
> On Tue, Sep 20, 2016 at 11:36:39AM +0800, Peter Chen wrote:
> > Hi all,
> >
> > This is a follow-up for my last power sequence framework patch set [1].
> > According to Rob Herring and Ulf Hansson's comments[2]. The kinds of
> > power s
Both import_iovec() and rw_copy_check_uvector() take an array
(typically small and on-stack) which is used to hold an iovec array copy
from userspace. This is to avoid an expensive memory allocation in the
fast path (i.e. few iovec elements).
The caller may have to check whether these functions ac
Vijay Kumar B writes:
> The PXA GPIO controller has 3 interrupt outputs, this needs to be
> indicated in the DTS file. Without this mainstone's CPLD interrupt 0
> will not be raised to the processor.
>
> Signed-off-by: Vijay Kumar B.
> Reviewed-by: Deepak S.
> ---
> arch/arm/boot/dts/pxa2xx.dt
Robert Jarzmik writes:
> The method to acquire the input interrupt was working in a platform data
> based board, but was failing in a device-tree one when the gpio
> controller was probed after pxa_cplds.
>
> Use platform_get_irq() to benefit from the probe deferral
> mechanism. Moreover, as seen
Robert Jarzmik writes:
> Since gpio-pxa was redesigned to differenciate gpio0, gpio1 and the
> gpio-mux interrupt as in the hardware IP, the device-tree description
> should be amended so that interrupts from gpio0 and gpio1 can be mapped
> to consumers.
>
> This is especially true on lubbock and
Hi Shawn,
On 2016/10/8 10:44, Shawn Lin wrote:
> 在 2016/10/7 23:22, Gregory CLEMENT 写道:
>> From: Ziji Hu
>>
>> Marvell Xenon eMMC/SD/SDIO Host Controller contains PHY.
>> Three types of PHYs are supported.
>>
>> Add support to multiple types of PHYs init and configuration.
>> Add register definit
Greg Kroah-Hartman writes:
> On Fri, Oct 07, 2016 at 04:06:04AM -0700, kernelci.org bot wrote:
>> stable-rc boot: 164 boots: 1 failed, 158 passed with 5 offline
>> (v4.4.23-94-g5dba8e95fccc)
>>
>> Full Boot Summary:
>> https://kernelci.org/boot/all/job/stable-rc/kernel/v4.4.23-94-g5dba8e95fccc
On Fri, 7 Oct 2016, Yinghai Lu wrote:
> On Fri, Oct 7, 2016 at 10:33 PM, Yinghai Lu wrote:
> > On Fri, Oct 7, 2016 at 10:26 PM, Yinghai Lu wrote:
> >> On Fri, Oct 7, 2016 at 6:28 AM, tip-bot for Thomas Gleixner
> >>> diff --git a/arch/x86/kernel/acpi/boot.c b/arch/x86/kernel/acpi/boot.c
> >>> ind
There are some conditions on this driver that are tested with
BUG_ON() with are not serious enough to hang a machine.
So, just return an error if this happens.
Signed-off-by: Mauro Carvalho Chehab
---
v2: simplify the logic and use its own error message.
drivers/media/usb/dvb-usb/pctv452e.c
From: Wanpeng Li
Commit:
10e2f1acd01 ("sched/core: Rewrite and improve select_idle_siblings()")
... improved select_idle_sibling() but also triggered a regression:
BUG: unable to handle kernel NULL pointer dereference at 0078
IP: [] select_idle_sibling+0x1c2/0x4f0
PGD 0
Oops: 00
Commit-ID: df610d678893c85b82d3a68eea0d87dd4e03e615
Gitweb: http://git.kernel.org/tip/df610d678893c85b82d3a68eea0d87dd4e03e615
Author: Thomas Gleixner
AuthorDate: Fri, 7 Oct 2016 15:55:13 +0200
Committer: Thomas Gleixner
CommitDate: Sat, 8 Oct 2016 12:18:36 +0200
x86/apic: Prevent poin
Commit-ID: d4b05923f579c234137317cdf9a5eb69ddab76d1
Gitweb: http://git.kernel.org/tip/d4b05923f579c234137317cdf9a5eb69ddab76d1
Author: Dave Hansen
AuthorDate: Fri, 7 Oct 2016 09:23:42 -0700
Committer: Thomas Gleixner
CommitDate: Sat, 8 Oct 2016 12:26:44 +0200
x86/pkeys: Make protection
On Fri, Oct 7, 2016 at 9:47 PM, Andy Lutomirski wrote:
> On 06/25/2016 09:19 AM, Chen Yu wrote:
>>
>> Here's the story of what the problem is, why this
>> happened, and why this patch looks like this:
>>
>> Stress test from Varun Koyyalagunta reports that, the
>> nonboot CPU would hang occasionall
psmouse->name "Focaltech Touchpad" is an overkill. In xinput it is too long as
"FocaltechPS/2 Focaltech Focaltech Touchpad"
In focaltech_report_state() pointer to psmouse->dev is already stored as *dev
Signed-off-by: Dmitry Tunin
---
drivers/input/mouse/focaltech.c | 6 +++---
1 file changed, 3
On 06.10.2016, Linus Walleij wrote:
> Not just desktops, also Android phones.
> So why not have BFQ as a separate scheduling policy upstream,
> alongside CFQ, deadline and noop?
Please, just do it! CFQ and deadline perform horribly on Android, and
the same is true for desktop systems based on
On Sat, 2016-10-08 at 10:12 +0200, Peter Zijlstra wrote:
> On Fri, Oct 07, 2016 at 07:26:36PM -0400, Jeff Layton wrote:
>
> >
> > Well spotted. Yeah, I think you're right. The assertion is this:
> >
> > percpu_rwsem_assert_held(&file_rwsem);
> >
> > I'm guessing this is probably fallout fro
On Fri, Oct 07, 2016 at 02:24:59PM +, Winkler, Tomas wrote:
> So here I'm to say I'm sorry for misleading this, after all the
> doubts I got back to debugging and traces. One thing for a reason
> moving the device_del, had really made the problem go away, but the
> real problem was unbalanc
Hi Arvind,
On 20 September 2016 at 12:39, Arvind Yadav wrote:
> From: Arvind Yadav
>
> Free memory mapping, if lpc18xx_ccu_init is not successful.
>
> Signed-off-by: Arvind Yadav
Acked-by: Joachim Eastwood
One comment below:
> ---
> drivers/clk/nxp/clk-lpc18xx-ccu.c |5 -
> 1 file
On Sat, Oct 01, 2016 at 10:25:24PM +0300, Jarkko Sakkinen wrote:
> From: Nayna Jain
>
> open() method for event log ascii and binary bios measurements file
> operations are very similar. This patch refactors the code into a
> single open() call by passing seq_operations as i_node->private data.
>
On Mon, Oct 03, 2016 at 03:21:35PM +0300, Jarkko Sakkinen wrote:
> On Sun, Oct 02, 2016 at 03:28:01PM -0600, Jason Gunthorpe wrote:
> > On Sat, Oct 01, 2016 at 10:25:25PM +0300, Jarkko Sakkinen wrote:
> >
> > > + for (i = (TPM_NUM_EVENT_LOG_FILES - 1); i >= 0; i--) {
> > > + if (chip->bios
On 2016.10.07 at 07:09 +0200, Markus Trippelsdorf wrote:
> On 2016.10.07 at 06:56 +0200, Markus Trippelsdorf wrote:
> > On 2016.10.07 at 06:32 +0200, Markus Trippelsdorf wrote:
> > > On 2016.10.07 at 13:22 +0900, Namhyung Kim wrote:
> > > > On Fri, Oct 07, 2016 at 05:51:18AM +0200, Markus Trippelsd
On Fri, Oct 07, 2016 at 11:28:13AM -0400, Samuel Morris wrote:
> Even though the core has been told the hardware is on with the boot_on
> constraint, it turns it off anyway during regulator_late_cleanup(). This
All that constraint does is tell the framework what the initial setting
is, nothing mo
On Fri, 7 Oct 2016, Rich Felker wrote:
>
> If I'm not mistaken, the bug is in tick_nohz_restart. According to the
I think you are mistaken. Let's look at CPU0 only:
-0 [000] d... 150.829698: __tick_nohz_idle_enter: can
stop idle tick
-0 [000] d... 150.829774: __t
On 8 October 2016 at 10:39, Ingo Molnar wrote:
>
> * Peter Zijlstra wrote:
>
>> On Fri, Oct 07, 2016 at 03:38:23PM -0400, Joseph Salisbury wrote:
>> > Hello Peter,
>> >
>> > A kernel bug report was opened against Ubuntu [0]. After a kernel
>> > bisect, it was found that reverting the following c
From: Markus Elfring
Date: Fri, 8 Oct 2016 13:41:12 +0200
A few update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Use kmalloc_array()
Add some spaces for better code readability
drivers/media/pci/cx88/cx88-dsp.c | 43 +++---
From: Markus Elfring
Date: Fri, 7 Oct 2016 22:30:40 +0200
Use space characters at some source code places according to
the Linux coding style convention.
Signed-off-by: Markus Elfring
---
drivers/media/pci/cx88/cx88-dsp.c | 40 +++
1 file changed, 20 inserti
On Sat, 2016-10-08 at 13:37 +0200, Vincent Guittot wrote:
> On 8 October 2016 at 10:39, Ingo Molnar wrote:
> >
> > * Peter Zijlstra wrote:
> >
> > > On Fri, Oct 07, 2016 at 03:38:23PM -0400, Joseph Salisbury wrote:
> > > > Hello Peter,
> > > >
> > > > A kernel bug report was opened against Ubu
From: Markus Elfring
Date: Fri, 7 Oct 2016 22:07:27 +0200
* A multiplication for the size determination of a memory allocation
indicated that an array data structure should be processed.
Thus use the corresponding function "kmalloc_array".
This issue was detected by using the Coccinelle so
Am 07.10.2016 21:46, schrieb SF Markus Elfring:
> From: Markus Elfring
> Date: Fri, 7 Oct 2016 21:13:57 +0200
>
> Adjust a jump label according to the Linux coding style convention.
>
> Signed-off-by: Markus Elfring
> ---
> drivers/media/dvb-frontends/tc90522.c | 5 ++---
> 1 file changed, 2
Te overall platform ability to enter a low power state is also
conditioned on the ability of a tpm device to go to idle state.
This series should provide this feature.
Unfortunately, there is a HW bug on Intel PTT devices on Skylake,
Kabylake, and Broxton devices, where certain registers lost rete
On Fri, 7 Oct 2016, Peter Zijlstra wrote:
> On Fri, Oct 07, 2016 at 04:52:44PM +0200, Peter Zijlstra wrote:
> > Poking at lock internals is not cool. Since I'm going to change the
> > implementation this will break, take it out.
>
>
> So something like the below would serve as a replacement for y
From: "Winkler, Tomas"
Utilize runtime_pm for driving tpm crb idle states.
The framework calls cmd_ready from the pm_runtime_resume handler
and go idle from the pm_runtime_suspend handler.
The TPM framework should wake the device before transmit and receive.
In case the runtime_pm framework is no
From: "Winkler, Tomas"
There is a HW bug in Skylake, Kabylake, and Broxton PCH Intel PTT device,
where most of the registers in the control area except START, REQUEST,
CANCEL, and LOC_CTRL lost retention when the device is in the idle state.
Hence we need to bring the device to ready state before
From: "Winkler, Tomas"
The register TPM_CRB_CTRL_REQ_x contains bits goIdle and cmdReady for
SW to indicate that the device can enter or should exit the idle state.
The legacy ACPI-start (SMI + DMA) based devices do not support these
bits and the idle state management is not exposed to the host
From: "Winkler, Tomas"
This is preparation step for implementing tpm crb
runtime pm. We need to have tpm chip allocated
and populated before we access the runtime handlers.
Signed-off-by: Tomas Winkler
Reviewed-by: Jarkko Sakkinen
Signed-off-by: Jarkko Sakkinen
---
V2: new in the series
V3: r
The Linux man-pages maintainer proudly announces:
man-pages-4.08 - man pages for Linux
This release includes input and contributions from
around 40 people. Nearly 200 pages saw changes, ranging
from typo fixes through to page rewrites and 1 new page.
Tarball download:
http://www.kernel.o
Linus,
please pull the latest timers-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-urgent-for-linus
A single fix for a regression introduced in 4.8 which causes the trace/perf
clock to return random nonsense if CONFIG_DEBUG_TIMEKEEPING is se
Linus,
please pull the latest irq-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
irq-urgent-for-linus
Two small kerneldoc fixes from Julia Lawall.
Thanks,
tglx
-->
Julia Lawall (2):
irqchip/vic: Improve function-leve
On Sat, Oct 08, 2016 at 02:59:39PM +0300, Tomas Winkler wrote:
> From: "Winkler, Tomas"
>
> Utilize runtime_pm for driving tpm crb idle states.
> The framework calls cmd_ready from the pm_runtime_resume handler
> and go idle from the pm_runtime_suspend handler.
> The TPM framework should wake the
Linus,
please pull the latest locking-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
locking-urgent-for-linus
A single fix which prevents newer GCCs from spamming the build output with
overly eager warnings about __builtin_return_address() uses whic
This patch adds the slim core rproc driver to the STi section
of the MAINTAINERS file.
Signed-off-by: Peter Griffin
Acked-by: Lee Jones
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index f593300..9924036 100644
--- a/MAINTAINERS
+++ b/MAINTAINE
Hi Vinod and Bjorn,
This patchset adds support for the Flexible Direct Memory Access (FDMA) core
found on STi chipsets from STMicroelectronics. The FDMA is a slim core CPU
with a dedicated firmware. It is a general purpose DMA controller supporting
16 independent channels and data can be moved fro
Make REMOTEPROC core a selectable kconfig option, and update
remoteproc client drivers to 'depends on' the core. This avoids
some nasty Kconfig recursive dependency issues. Also when using
menuconfig client drivers will be hidden until the core has been
enabled.
Documentation/kbuild/kconfig-langua
This patch adds the DT binding documentation for the FDMA constroller
found on STi based chipsets from STMicroelectronics.
Signed-off-by: Ludovic Barre
Signed-off-by: Peter Griffin
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/dma/st_fdma.txt | 87 +++
1 file
This patch adds the FDMA driver files to the STi
section of the maintainers file.
Signed-off-by: Peter Griffin
Acked-by: Lee Jones
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 9924036..f71a1d1 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -
This patch adds support for the Flexible Direct Memory Access (FDMA) core
driver. The FDMA is a slim core CPU with a dedicated firmware.
It is a general purpose DMA controller capable of supporting 16
independent DMA channels. Data moves maybe from memory to memory
or between memory and paced laten
This header file will also be used by the dma xbar driver in the
future.
Signed-off-by: Ludovic Barre
Signed-off-by: Peter Griffin
---
drivers/dma/st_fdma.h | 249 ++
1 file changed, 249 insertions(+)
create mode 100644 drivers/dma/st_fdma.h
dif
slim core is used as a basis for many IPs in the STi
chipsets such as fdma and demux. To avoid duplicating
the elf loading code in each device driver a slim
rproc driver has been created.
This driver is designed to be used by other device drivers
such as fdma, or demux whose IP is based around a s
Now that remoteproc core is selectable it needs to be enabled
in the multi_v7 build.
Signed-off-by: Peter Griffin
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/multi_v7_defconfig
b/arch/arm/configs/multi_v7_defconfig
index 3ca4974..
This DMA controller is found on all STi chipsets.
Signed-off-by: Peter Griffin
Acked-by: Lee Jones
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/multi_v7_defconfig
b/arch/arm/configs/multi_v7_defconfig
index 33f7a8a..46f174e 100644
On Sat, Oct 08, 2016 at 02:59:37PM +0300, Tomas Winkler wrote:
> From: "Winkler, Tomas"
>
> There is a HW bug in Skylake, Kabylake, and Broxton PCH Intel PTT device,
> where most of the registers in the control area except START, REQUEST,
> CANCEL, and LOC_CTRL lost retention when the device is i
The st231 remote coprocessors are found on all STi chipsets.
Signed-off-by: Peter Griffin
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/multi_v7_defconfig
b/arch/arm/configs/multi_v7_defconfig
index c94611c..33f7a8a 100644
--- a/arc
This patch enables the STi ALSA drivers found on STi platforms
as well as the simple-card driver which is a dependency to have
working sound.
Signed-off-by: Peter Griffin
Acked-by: Lee Jones
Cc: arnaud.pouliq...@st.com
Cc: broo...@kernel.org
---
arch/arm/configs/multi_v7_defconfig | 3 +++
1 fi
On Fri, Oct 7, 2016 at 6:54 AM, Aaron Brice wrote:
> - The DMA error interrupt bit is in a different position as
>compared to the sdhci standard. This is accounted for in
>many cases, but not handled in the case of clearing the
>INT_STATUS register by writing a 1 to that location.
>
The if and else are identical and can be consolidated here.
Fixes: commit 91be260faaf8 ("[media] dib8000: Add support for Mygica/Geniatech
S2870")
Signed-off-by: Nicholas Mc Guire
---
Problem found by coccinelle script
Based only on reviewing this driver it seems that the dib0090_config
is no
After backporting commit ee44b4bc054a ("dlm: use sctp 1-to-1 API")
series to a kernel with an older workqueue which didn't use RCU yet, it
was noticed that we are freeing the workqueues in dlm_lowcomms_stop()
too early as free_conn() will try to access that memory for canceling
the queued works if
Linus,
please pull the latest perf-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-urgent-for-linus
This update contains:
- Handle uretprobe placement proper on little endian PPC64
- Fix buffer handling in libtraceevent.
- Add a missing
On Fri, Oct 07, 2016 at 04:09:51PM -0700, Tony Luck wrote:
> On Fri, Oct 7, 2016 at 4:01 PM, Tony Luck wrote:
> > What if there isn't a "next printk" call for hours, or days?
> >
> > That poor little message without a "\n" will sit in the kernel buffers,
> > and the user who might want to see the
Linus,
please pull the latest sched-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
sched-urgent-for-linus
A revert of a commit which pointelessly widened a preempt disabled section
which in turn caused might_sleep() to trigger. The patch intended to
>
> On Sat, Oct 08, 2016 at 02:59:39PM +0300, Tomas Winkler wrote:
> > From: "Winkler, Tomas"
> >
> > Utilize runtime_pm for driving tpm crb idle states.
> > The framework calls cmd_ready from the pm_runtime_resume handler and
> > go idle from the pm_runtime_suspend handler.
> > The TPM framework
Linus,
please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
A pile of regression fixes and updates:
- Address the fallout of the patches which made the cpuid - nodeid
relation permanent: Handling of i
On Fri, Oct 07, 2016 at 03:26:04PM -0700, kernelci.org bot wrote:
> stable-rc boot: 479 boots: 4 failed, 183 passed with 292 offline
> (v4.8-11-ge141008f62ab)
>
> Full Boot Summary:
> https://kernelci.org/boot/all/job/stable-rc/kernel/v4.8-11-ge141008f62ab/
> Full Build Summary:
> https://kerne
Hi Olivier !
in your commit 28fafca78797b ("[media] DiB0090: misc improvements")
with commit message:
This patch adds several performance improvements and prepares the
usage of firmware-based devices.
it seems you changed the logic of an if/else in dib0090_tune() in a way
that I
Hi Enric,
> This patch adds and entry to the sysfs to start firmware upload process
> on the specified device with the requested firmware.
>
> The uploading of the firmware needs only to happen once per firmware
> upgrade, as the firmware is stored in persistent storage. If the
> firmware upload
Linus,
please pull the latest mm-pkeys-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git mm-pkeys-for-linus
This is the final step of Protection Keys support which adds the syscalls
so user space can actually allocate keys and protect memory areas with
them. D
Hi Markus,
> From: Markus Elfring
> Date: Mon, 15 Aug 2016 13:34:47 +0200
>
> The field "owner" is set by core. Thus delete an extra initialisation.
>
> Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
> Signed-off-by: Markus Elfring
This patch was added to linux-watchdog-next
Hi Peter,
> STiH415/6 SoC support is being removed from the kernel
> so update the dt bding document to reflect this.
>
> Signed-off-by: Peter Griffin
> Cc:
> Cc:
> Cc:
> Cc:
> ---
This patch and your st_wdt patch has been added to linux-watchdog-next almost 2
weeks ago.
Kind regards,
Wim
On Sat, 8 Oct 2016, Peter Zijlstra wrote:
> On Sat, Oct 08, 2016 at 01:58:07PM +0200, Thomas Gleixner wrote:
> > Hmm. I'm not a great fan of this, because that requires an conditional
> > unlock mechanism.
> >
> >res = trylock_recursive(lock);
> >if (res == FAILED)
> >
Hi Brian,
> iLO5 will offer the same watchdog timer as previous generations, but the
> PCI subsystem vendor ID will be PCI_VENDOR_ID_HP_3PAR (0x1590) instead of
> PCI_VENDOR_ID_HP (0x103c). Add 0x1590 to the whitelist and be more
> specific when ignoring the 103c,1979 device.
>
> Signed-off-by:
Hi Julia,
> iTCO_wdt_pm, of type struct dev_pm_ops, is never modified, so declare it as
> const.
>
> Done with the help of Coccinelle.
>
> Signed-off-by: Julia Lawall
This patch and your constify watchdog_ops structures were added to
linux-watchdog-next almost 2 weeks ago.
Kind regards,
Wim.
Hi Matt,
> Commit 0254e953537c ("watchdog: Drop pointer to watchdog device from
> struct watchdog_device") removed the dev pointer from struct
> watchdog_device, but this driver was still assigning it, leading to a
> compilation error:
>
> drivers/watchdog/rt2880_wdt.c: In function ‘rt288x_wdt_pr
On Sat, Oct 08, 2016 at 01:58:07PM +0200, Thomas Gleixner wrote:
> Hmm. I'm not a great fan of this, because that requires an conditional
> unlock mechanism.
>
>res = trylock_recursive(lock);
>if (res == FAILED)
> goto out;
>.
>
>if (res ==
>
> On Sat, Oct 08, 2016 at 02:59:37PM +0300, Tomas Winkler wrote:
> > From: "Winkler, Tomas"
> >
> > There is a HW bug in Skylake, Kabylake, and Broxton PCH Intel PTT
> > device, where most of the registers in the control area except START,
> > REQUEST, CANCEL, and LOC_CTRL lost retention when t
Hi Linus,
The following changes since commit 694d0d0bb2030d2e36df73e2d23d5770511dbc8d:
Linux 4.8-rc2 (2016-08-14 19:11:36 -0700)
are available in the git repository at:
https://github.com/ceph/ceph-client.git tags/ceph-for-4.9-rc1
for you to fetch changes up to 64f77566e1c84990d6c448bb3960
> That did not go well - bisect found the following commit but that does
> not seem to be related at all. So probably the reproducibility is not
> 100% but more random.
Now I reproduced the bug even with 4.7-rc1 so it is older than 4.7. Will
test further.
>
>
> 4c5773f9f5462dcb372857813918bb
The ethtool api {get|set}_settings is deprecated.
We move this driver to new api {get|set}_link_ksettings.
Signed-off-by: Philippe Reynes
---
drivers/net/ethernet/ti/cpsw.c | 17 ++---
1 files changed, 10 insertions(+), 7 deletions(-)
diff --git a/drivers/net/ethernet/ti/cpsw.c b/
Report code constructs where the if and else branch are functionally
identical. In cases where this is intended it really should be
documented - most reported cases probably are bugs.
Signed-off-by: Nicholas Mc Guire
---
Tested with spatch version 1.0.5
As of 4.8.0 this reports about 90 cases
On Fri, 7 Oct 2016, Peter Zijlstra wrote:
> Solve all that by:
>
> - using futex specific rt_mutex calls that lack the fastpath, futexes
>have their own fastpath anyway. This makes that
>rt_mutex_futex_unlock() doesn't need to drop rt_mutex::wait_lock
>and the unlock is guaranteed if
On Sat, Oct 08, 2016 at 02:27:06PM +, Winkler, Tomas wrote:
> >
> > On Sat, Oct 08, 2016 at 02:59:37PM +0300, Tomas Winkler wrote:
> > > From: "Winkler, Tomas"
> > >
> > > There is a HW bug in Skylake, Kabylake, and Broxton PCH Intel PTT
> > > device, where most of the registers in the contro
On Sat, Oct 8, 2016 at 10:15 PM, Meelis Roos wrote:
>> That did not go well - bisect found the following commit but that does
>> not seem to be related at all. So probably the reproducibility is not
>> 100% but more random.
>
> Now I reproduced the bug even with 4.7-rc1 so it is older than 4.7. Wi
On Sat, Oct 08, 2016 at 01:37:31PM +, Winkler, Tomas wrote:
> >
> > On Sat, Oct 08, 2016 at 02:59:39PM +0300, Tomas Winkler wrote:
> > > From: "Winkler, Tomas"
> > >
> > > Utilize runtime_pm for driving tpm crb idle states.
> > > The framework calls cmd_ready from the pm_runtime_resume handle
On Fri, Oct 7, 2016 at 10:16 AM, Pantelis Antoniou
wrote:
> From: Guenter Roeck
>
> Add documentation for the Juniper connector driver.
>
> Signed-off-by: Alon Ronen
> Signed-off-by: Guenter Roeck
> [Ported from Juniper kernel]
> Signed-off-by: Pantelis Antoniou
> ---
> .../devicetree/binding
On Fri, Oct 7, 2016 at 10:16 AM, Pantelis Antoniou
wrote:
> Introduce a Juniper PTX router series DT overlay based
> connector driver.
>
> This is submitted as an RFC since some OF infrastructure
> patches (like changeset helpers etc) are not yet mainlined.
Because you haven't sent them out again
Greg Kroah-Hartman writes:
> On Fri, Oct 07, 2016 at 03:26:04PM -0700, kernelci.org bot wrote:
>> stable-rc boot: 479 boots: 4 failed, 183 passed with 292 offline
>> (v4.8-11-ge141008f62ab)
>>
>> Full Boot Summary:
>> https://kernelci.org/boot/all/job/stable-rc/kernel/v4.8-11-ge141008f62ab/
>>
Hi Rob,
> On Oct 8, 2016, at 19:10 , Rob Herring wrote:
>
> On Fri, Oct 7, 2016 at 10:16 AM, Pantelis Antoniou
> wrote:
>> Introduce a Juniper PTX router series DT overlay based
>> connector driver.
>>
>> This is submitted as an RFC since some OF infrastructure
>> patches (like changeset helpe
On Sat, Oct 08, 2016 at 01:32:06PM +0200, Thomas Gleixner wrote:
> On Fri, 7 Oct 2016, Rich Felker wrote:
> >
> > If I'm not mistaken, the bug is in tick_nohz_restart. According to the
>
> I think you are mistaken. Let's look at CPU0 only:
OK.
> -0 [000] d... 150.829698: __tick_
On Sat, Oct 08, 2016 at 02:59:36PM +0300, Tomas Winkler wrote:
> From: "Winkler, Tomas"
>
> The register TPM_CRB_CTRL_REQ_x contains bits goIdle and cmdReady for
> SW to indicate that the device can enter or should exit the idle state.
>
> The legacy ACPI-start (SMI + DMA) based devices do not s
On Sat, Oct 08, 2016 at 07:00:06PM +0300, Jarkko Sakkinen wrote:
> Rather you it would be better not to use cmdReady/goIdle at all if
> kernel is not compiled with CONFIG_PM.
It would be best practice to ensure the tpm is powered up no matter
how the kernel is compiled.. The firmware may have lef
1 - 100 of 207 matches
Mail list logo
