Hello, Robert.
My research system are based on virtual machine and Intel NUC machine,
and they are still working despite of ACPI subsystem shutdown.
So, I can find the acpi memory leaks by using "dmesg" command.
Best regards.
2017-06-16 4:52 GMT+09:00 Moore, Robert :
> This might be a dumb quest
On Mon, 12 Jun 2017 06:17:20 +0530 Sahitya Tummala
wrote:
> __list_lru_walk_one() can hold the spin lock for longer duration
> if there are more number of entries to be isolated.
>
> This results in "BUG: spinlock lockup suspected" in the below path -
>
> [] spin_bug+0x90
> [] do_raw_spin_lock
On Thu, Jun 08, 2017 at 10:07:42AM +0200, Quentin Schulz wrote:
> Some boards might require to control a regulator to power the PCIe port.
>
> This adds support for an optional regulator defined in Device Tree
> linked in the PCIe controller under `vpcie-supply`. If present, the
> regulator will b
Hi Jesse,
Quoting Jesse Brandeburg :
On Wed, 14 Jun 2017 21:38:26 -0500
"Gustavo A. R. Silva" wrote:
Fix incorrect variable assignment.
Based on line 1511: aq_ret = I40_ERR_PARAM; the correct variable to be
used in this instance is aq_ret instead of ret. Also, variable ret is
updated at line
On Mon, Jun 05, 2017 at 02:27:58PM +0800, Ryder Lee wrote:
> The 'linkup' variable would always increment by one whether the link
> status is true or not. Therefore, this patch fixes the return value in
> mtk_pcie_parse_and_add_res() and removes unnecessary 'linkup' variable.
>
> Signed-off-by: Ry
From: Vivien Didelot
Date: Thu, 15 Jun 2017 15:06:54 -0400
> The current code only assigns the default cpu_dp to all user ports of
> the switch to which the CPU port belongs. The user ports of the other
> switches of the fabric thus don't have a default CPU port.
>
> This patch fixes this by ass
On Thu, 15 Jun 2017, Michal Hocko wrote:
> > If mm->mm_users is not incremented because it is already zero by the oom
> > reaper, meaning the final refcount has been dropped, do not set
> > MMF_OOM_SKIP prematurely.
> >
> > __mmput() may not have had a chance to do exit_mmap() yet, so memory from
On Wed, Jun 14, 2017 at 01:56:48PM -0700, Joe Perches wrote:
> On Wed, 2017-06-14 at 15:30 -0500, Rob Herring wrote:
> > From: Pantelis Antoniou
>
> I think the commit subject is wrong.
> It adds an "of" specific bit to vsprintf.c.
> The subject should be
> 'vsprintf: Add %p extension "%pO" for
From: "Gustavo A. R. Silva"
Date: Thu, 15 Jun 2017 14:56:21 -0500
> Value assigned to variable _data32_ at lines 1254 and 1257 is
> overwritten at line 1260 before it can be used. This makes
> such variable assignments useless.
>
> Addresses-Coverity-ID: 1227049
> Signed-off-by: Gustavo A. R. Si
On Mon, Jun 12, 2017 at 3:25 PM, Toshi Kani wrote:
> Sysfs "badblocks" information may be updated during run-time that:
> - MCE, SCI, and sysfs "scrub" may add new bad blocks
> - Writes and ioctl() may clear bad blocks
>
> Add support to send sysfs notifications to sysfs "badblocks" file
> under
On Thu, 15 Jun 2017, Tetsuo Handa wrote:
> David is trying to avoid setting MMF_OOM_SKIP when the OOM reaper found that
> mm->users == 0.
Yes, because MMF_OOM_SKIP enables the oom killer to select another process
to kill and will do so without the original victim's mm being able to
undergo exit
On Thu, Jun 15, 2017 at 1:33 PM, Bjorn Andersson
wrote:
> On Thu 15 Jun 09:26 PDT 2017, Sebastian Reichel wrote:
>
>> Hi,
>>
>> On Mon, Jun 12, 2017 at 04:32:03PM -0700, Bjorn Andersson wrote:
> [..]
>> > As such if we split the non-input related handling into another driver
>> > we would need to
On Thu, Jun 15, 2017 at 07:54:57AM +1000, NeilBrown wrote:
> On Wed, Jun 14 2017, J. Bruce Fields wrote:
>
> > On Wed, Jun 14, 2017 at 12:30:02PM +0300, Dan Carpenter wrote:
> >> I found this bug by reviewing places where we do ERR_PTR(0) (which is
> >> NULL).
> >>
> >> We used to return an error
On Thu 15-06-17 14:26:26, David Rientjes wrote:
> On Thu, 15 Jun 2017, Michal Hocko wrote:
>
> > > If mm->mm_users is not incremented because it is already zero by the oom
> > > reaper, meaning the final refcount has been dropped, do not set
> > > MMF_OOM_SKIP prematurely.
> > >
> > > __mmput() m
Michal Hocko wrote:
> On Thu 15-06-17 22:01:33, Tetsuo Handa wrote:
> > Michal Hocko wrote:
> > > On Thu 15-06-17 14:03:35, Michal Hocko wrote:
> > > > On Thu 15-06-17 20:32:39, Tetsuo Handa wrote:
> > > > > @@ -556,25 +553,21 @@ static void oom_reap_task(struct task_struct
> > > > > *tsk)
> > > >
Hi David,
Quoting David Miller :
From: "Gustavo A. R. Silva"
Date: Thu, 15 Jun 2017 14:56:21 -0500
Value assigned to variable _data32_ at lines 1254 and 1257 is
overwritten at line 1260 before it can be used. This makes
such variable assignments useless.
Addresses-Coverity-ID: 1227049
Signe
On Thu, Jun 8, 2017 at 11:36 AM, Toshi Kani wrote:
> ACPI 6.2 defines a new ACPI notification value to NVDIMM Root Device
> in Table 5-169.
>
> 0x81 Unconsumed Uncorrectable Memory Error Detected
> Used to pro-actively notify OSPM of uncorrectable memory errors
> detected (for example
On Tue, May 30, 2017 at 9:05 AM, Paolo Bonzini wrote:
>
>
> On 30/05/2017 17:58, Roman Penyaev wrote:
>> Indeed, what is left is eventually take it from SS.RPL. J.
>
> Ahah! :) But I only suggested that in specific cases.
>
>> But jokes aside, with your last patch you seems fixed a race problem
Hi Andy,
On 06/15/2017 02:19 AM, Andy Shevchenko wrote:
On Thu, Jun 15, 2017 at 2:21 AM,
wrote:
From: Kuppuswamy Sathyanarayanan
Commit 9a752b4c9ab9 ("gpio: crystalcove: Do not write regular gpio
registers for virtual GPIOs") added support to skip GPIO register
update for virtual GPIOs, but
On Thu, Jun 01, 2017 at 03:51:45PM +0530, Arvind Yadav wrote:
> clk_prepare_enable() can fail here and we must check its return value.
>
> Signed-off-by: Arvind Yadav
Applied with ack/reviewed-by from Shawn and Heiko to pci/host-rockchip for
v4.13, thanks!
I had to apply it manually because of
On Thu, 2017-06-15 at 16:26 -0500, Rob Herring wrote:
> On Wed, Jun 14, 2017 at 01:56:48PM -0700, Joe Perches wrote:
> > On Wed, 2017-06-14 at 15:30 -0500, Rob Herring wrote:
> > > From: Pantelis Antoniou
[]
> > > diff --git a/lib/vsprintf.c b/lib/vsprintf.c
> > > []
> > > @@ -1470,6 +1471,123 @@
On Wed, 2017-06-07 at 18:28 +0200, Borislav Petkov wrote:
> On Fri, May 05, 2017 at 11:17:16AM -0700, Ricardo Neri wrote:
> > Tasks running in virtual-8086 mode or in protected mode with code
> > segment descriptors that specify 16-bit default address sizes via the
> > D bit will use 16-bit address
On Thu, 2017-06-15 at 19:14 +0100, Michael J Dilmore wrote:
> Multiple netdev_info messages clutter kernel output. Also add netdev_dbg for
> packets per slave.
[]
> diff --git a/drivers/net/bonding/bond_options.c
> b/drivers/net/bonding/bond_options.c
[]
> @@ -9,6 +9,8 @@
> * (at your option) a
Hi Kirill,
[auto build test ERROR on mmotm/master]
[also build test ERROR on v4.12-rc5 next-20170615]
[cannot apply to tip/x86/core]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Kirill-A
On Thu, Jun 15, 2017 at 11:48:18AM -0700, Luis R. Rodriguez wrote:
> While reviewing RCU's interruptible swaits I noticed signals were actually
> not expected. Paul explained that the reason signals are not expected is
> we use kthreads, which don't get signals, furthermore the code avoided the
> u
On Thu, 15 Jun 2017, Michal Hocko wrote:
> > Yes, quite a bit in testing.
> >
> > One oom kill shows the system to be oom:
> >
> > [22999.488705] Node 0 Normal free:90484kB min:90500kB ...
> > [22999.488711] Node 1 Normal free:91536kB min:91948kB ...
> >
> > followed up by one or more unnecessa
Thanks for this. I think it's going in the right direction, but one
comment below.
On Thu, Jun 8, 2017 at 11:36 AM, Toshi Kani wrote:
> ACPI 6.2 defines in section 9.20.7.2 that the OSPM may call a Start
> ARS with Flags Bit [1] set upon receiving the 0x81 notification.
>
> Upon receiving the n
On Wed, Jun 14, 2017 at 09:41:29PM +0200, Pavel Machek wrote:
> diff --git a/drivers/media/platform/omap3isp/isp.c
> b/drivers/media/platform/omap3isp/isp.c
> index 4ca3fc9..b80debf 100644
> --- a/drivers/media/platform/omap3isp/isp.c
> +++ b/drivers/media/platform/omap3isp/isp.c
> @@ -2026,7 +202
Hi,
On 15.06.2017 22:56, Mark Rutland wrote:
Hi,
On Thu, Jun 15, 2017 at 08:41:42PM +0300, Alexey Budankov wrote:
This series of patches continues v2 and addresses captured comments.
As a general note, please keep any change log stuff out of the commit
message, and mvoe that just before the
Boris Brezillon writes:
> Hi Eric,
>
> On Wed, 7 Jun 2017 17:13:36 -0700
> Eric Anholt wrote:
>
>> This allows mesa to set the tiling format for a BO and have that
>> tiling format be respected by mesa on the other side of an
>> import/export (and by vc4 scanout in the kernel), without defining
On Thu 15-06-17 15:03:17, David Rientjes wrote:
> On Thu, 15 Jun 2017, Michal Hocko wrote:
>
> > > Yes, quite a bit in testing.
> > >
> > > One oom kill shows the system to be oom:
> > >
> > > [22999.488705] Node 0 Normal free:90484kB min:90500kB ...
> > > [22999.488711] Node 1 Normal free:91536
On Thu, Jun 15, 2017 at 7:33 AM, Dave Hansen wrote:
> On 06/14/2017 10:18 PM, Andy Lutomirski wrote:
>> Dave, why is XINUSE exposed at all to userspace?
>
> You need it for XSAVEOPT when it is using the init optimization to be
> able to tell which state was written and which state in the XSAVE buf
Hi!
Ok, so I played a bit, and now I have working camera in v4.12-rc3.
https://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-n900.git/
camera-fw5-3 is recommended branch to play with.
Sakari, should I attempt to clean/send you patches, or would it be
better to wait till ccp2 branch is merge
On 06/15/2017 11:52 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.33 release.
> There are 108 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses s
Fix compilation of isp.c
Signed-off-by: Pavel Machek
diff --git a/drivers/media/platform/omap3isp/isp.c
b/drivers/media/platform/omap3isp/isp.c
index 4ca3fc9..b80debf 100644
--- a/drivers/media/platform/omap3isp/isp.c
+++ b/drivers/media/platform/omap3isp/isp.c
@@ -2026,7 +2026,7 @@ static
On 06/15/2017 11:52 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.73 release.
> There are 46 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses sh
On 06/15/2017 11:54 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.11.6 release.
> There are 13 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses sh
Hi all,
After merging the wireless-drivers tree, today's linux-next build
(x86_64 allmodconfig) produced this warning:
drivers/net/wireless/broadcom/brcm80211/brcmfmac/usb.c: In function
'brcmf_usb_probe_phase2':
drivers/net/wireless/broadcom/brcm80211/brcmfmac/usb.c:1198:2: warning:
'devinfo'
Hi Srinath,
On Tue, May 30, 2017 at 02:38:17PM +0530, Srinath Mannam wrote:
> We found a concurrency issue in NVMe Init when we initialize
> multiple NVMe connected over PCIe switch.
>
> Setup details:
> - SMP system with 8 ARMv8 cores running Linux kernel(4.11).
> - Two NVMe cards are connecte
On Thu, Jun 15, 2017 at 1:20 PM, Stephane Eranian wrote:
> On Thu, Jun 15, 2017 at 1:02 PM, Andi Kleen wrote:
>> On Thu, Jun 15, 2017 at 12:35:39PM -0700, Stephane Eranian wrote:
>>> On Thu, Jun 15, 2017 at 10:23 AM, Andi Kleen wrote:
>>> > On Thu, Jun 15, 2017 at 09:44:07AM -0700, Stephane Eran
On Thu, Jun 15 2017, J. Bruce Fields wrote:
> On Thu, Jun 15, 2017 at 07:54:57AM +1000, NeilBrown wrote:
>> On Wed, Jun 14 2017, J. Bruce Fields wrote:
>>
>> > On Wed, Jun 14, 2017 at 12:30:02PM +0300, Dan Carpenter wrote:
>> >> I found this bug by reviewing places where we do ERR_PTR(0) (which i
360Controller [0] is an OpenSource driver for Xbox/Xbox360/XboxOne controllers
on macOS.
It contains a couple device IDs unknown to the Linux driver, so I wrote a small
Python script [1]
to extract them and feed them into my previous script [2] to compare them with
the IDs known to
Linux.
For
XBCD [0][1] is an OpenSource driver for Xbox controllers on Windows.
Later it also started supporting Xbox360 controllers (presumably before
the official Windows driver was released).
It contains a couple device IDs unknown to the Linux driver, so I extracted
those from xbcd.inf and added them to
When building for the eBPF target archecture. Inline asm cannot be
used as MIPS instructions are fundamentally incompatible with eBPF
bytecode. The preprocessor symbol __EMITTING_BPF__ is used to gate
the inclusion of inline asm in constructs used the by the BPF
programs.
Also make the Makefile s
Hi Kirill,
[auto build test ERROR on mmotm/master]
[also build test ERROR on v4.12-rc5 next-20170615]
[cannot apply to tip/x86/core]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Kirill-A
To build samples/bpf on MIPS we need to avoid some inline asm that
causes llvm to fail.
Looking at the code, it seems that arm64 had the same problem and
avoided it by defining the header guard symbol. This approach does
not scale, so I invented a preprocessor define to identify the case of
build
... this allows gating of inline assembly code that causes llvm to
fail when emitting BPF.
Signed-off-by: David Daney
---
samples/bpf/Makefile | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/samples/bpf/Makefile b/samples/bpf/Makefile
index a0561dc762fe..4979e6b56662
Compilation to eBPF chokes on the inline asm in asm/sysreg.h, so don't
include it when compiling to a BPF target.
Signed-off-by: David Daney
---
arch/arm64/include/asm/sysreg.h | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/arm64/include/asm/sysreg.h b/arch/arm64/inc
Remove unnecessary variable smc_result and simplify the logic related.
Variable smc_result is only being used to store the return value of function
si_send_msg_to_smc() and then compare this value against constant
PPSMC_Result_OK. In other cases this variable is not even used after
storing a value
Yeah, this is basically mostly copy-pasted from the sboot code,
would need some cleaning up.
I've been playing more a little with other bits of the hardware,
writing some test fw from scratch, mostly without using the builtin
rom (except for interrupts).
Oleksij Rempel wrote:
> Am 08.06.2017 um 00
On Thu, Jun 15, 2017 at 3:18 PM, Andy Lutomirski wrote:
> On Thu, Jun 15, 2017 at 7:33 AM, Dave Hansen wrote:
>> On 06/14/2017 10:18 PM, Andy Lutomirski wrote:
>>> Dave, why is XINUSE exposed at all to userspace?
>>
>> You need it for XSAVEOPT when it is using the init optimization to be
>> able
On 2017-06-15 11:37, Boris Brezillon wrote:
> On Thu, 15 Jun 2017 11:24:13 +0200
> Peter Rosin wrote:
>
>> From: Peter Rosin
>>
>> Remove the layer.
>
> Duh. It was present in the datasheet I had. Just downloaded last
> version of the datasheet and it's no longer there.
Heh.
> Nicolas, there'
On Fri, 16 Jun 2017, Michal Hocko wrote:
> I am sorry but I have really hard to make the oom reaper a reliable way
> to stop all the potential oom lockups go away. I do not want to
> reintroduce another potential lockup now.
Please show where this "potential lockup" ever existed in a bug report o
On Thu, Jun 15, 2017 at 3:40 PM, H.J. Lu wrote:
> On Thu, Jun 15, 2017 at 3:18 PM, Andy Lutomirski wrote:
>> On Thu, Jun 15, 2017 at 7:33 AM, Dave Hansen wrote:
>>> On 06/14/2017 10:18 PM, Andy Lutomirski wrote:
Dave, why is XINUSE exposed at all to userspace?
>>>
>>> You need it for XSAVEO
perf/core: use rb trees for pinned/flexible groups
By default, the userspace perf tool opens per-cpu task-bound events
when sampling, so for N logical events requested by the user, the tool
will open N * NR_CPUS events.
In the kernel, we mux events with a hrtimer, periodically rotating the
flexi
Hi Kirill,
[auto build test ERROR on mmotm/master]
[also build test ERROR on v4.12-rc5 next-20170615]
[cannot apply to tip/x86/core]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Kirill-A
On Thu, Jun 15, 2017 at 11:26:53PM +0530, Sumit Semwal wrote:
>
> 4. bpf tests: These seem to have build failures in mainline as well -
> I also tried to build kselftest-next, but a simple 'make -C
> tools/testing/selftests/bpf' seems to error out. Are there any special
> instructions to build the
On Thu, Jun 15, 2017 at 3:45 PM, Andy Lutomirski wrote:
> On Thu, Jun 15, 2017 at 3:40 PM, H.J. Lu wrote:
>> On Thu, Jun 15, 2017 at 3:18 PM, Andy Lutomirski wrote:
>>> On Thu, Jun 15, 2017 at 7:33 AM, Dave Hansen wrote:
On 06/14/2017 10:18 PM, Andy Lutomirski wrote:
> Dave, why is XIN
On 6/15/2017 11:48 AM, Suman Anna wrote:
Hi Sarangdhar,
Hi Suman,
Thanks for reviewing the patch.
On 06/14/2017 01:06 PM, Sarangdhar Joshi wrote:
The remoteproc framework shuts down and immediately restarts the
remote processor after fatal events (such as when remote crashes)
during the re
Hi all,
Today's linux-next merge of the clk tree got a conflict in:
MAINTAINERS
between commits:
18a006203b88 ("dt-bindings: reset: Add TI SCI reset binding")
28df169b9afa ("reset: Add the TI SCI reset driver")
from the reset tree and commits:
8f306cfe4383 ("Documentation: dt: Add TI
> Looking at this approach, the user interface is straightforward,
> implementation in the x86 code is a bit more hairy because of the way
> the branch_stack is captured, via the cpuc->lbr_entries. If you assume
> that SKID_IP cannot be used with any other branch stack mode, then it
> is easy. It b
Hi all,
This patch series relocates ARM's fncpy to asm-generic in order for us to
be able to use SRAM_EXEC on ARM64 platforms.
Florian Fainelli (3):
ARM: Generalize fncpy implementation
arm64: Provide a fncpy implenentation
misc: sram: Allow ARM64 to select SRAM_EXEC
arch/arm/include/asm/
ARM's fncpy implementation is actually suitable for a large number of
platforms since the only assumption it makes is just the function's
alignment (8 bytes) which also happens to fulfil other architectures,
including but not limited to ARM64.
Signed-off-by: Florian Fainelli
---
arch/arm/include
Utilize the asm-generic/fncpy.h implementation for ARM64 to allow the
use of drivers/misc/sram*.c on these platforms as well.
Signed-off-by: Florian Fainelli
---
arch/arm64/include/asm/fncpy.h | 6 ++
1 file changed, 6 insertions(+)
create mode 100644 arch/arm64/include/asm/fncpy.h
diff --
Now that ARM64 also has a fncpy() implementation, allow selection
SRAM_EXEC for ARM64 as well.
Signed-off-by: Florian Fainelli
---
drivers/misc/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
index 07bbd4cc1852..ac8779278c0c
On 06/15/2017 04:21 PM, Florian Fainelli wrote:
> ARM's fncpy implementation is actually suitable for a large number of
> platforms since the only assumption it makes is just the function's
> alignment (8 bytes) which also happens to fulfil other architectures,
> including but not limited to ARM64.
On Thu, Jun 15, 2017 at 02:57:17PM -0700, Paul E. McKenney wrote:
> On Thu, Jun 15, 2017 at 11:48:18AM -0700, Luis R. Rodriguez wrote:
> > While reviewing RCU's interruptible swaits I noticed signals were actually
> > not expected. Paul explained that the reason signals are not expected is
> > we u
With this squashed in, the vc4 patch is:
Reviewed-by: Eric Anholt
Signed-off-by: Eric Anholt
---
Without this, the cursor never moved :)
drivers/gpu/drm/vc4/vc4_plane.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/vc4/vc4_plane.c b/drivers/gpu/drm/vc4/vc4_plane.c
ind
On Thu, Jun 15, 2017 at 4:11 PM, H.J. Lu wrote:
> On Thu, Jun 15, 2017 at 3:45 PM, Andy Lutomirski wrote:
>> On Thu, Jun 15, 2017 at 3:40 PM, H.J. Lu wrote:
>>> On Thu, Jun 15, 2017 at 3:18 PM, Andy Lutomirski wrote:
On Thu, Jun 15, 2017 at 7:33 AM, Dave Hansen wrote:
> On 06/14/2017
On Wed, 07 Jun 2017 12:08:38 +1000 NeilBrown wrote:
>
> If a positive status is passed with the AUTOFS_DEV_IOCTL_FAIL
> ioctl, autofs4_d_automount() will return
>ERR_PTR(status)
> with that status to follow_automount(), which will then
> dereference an invalid pointer.
>
> So treat a positi
On 06/15/2017 03:18 PM, Andy Lutomirski wrote:
>> As you pointed out, if you are using XSAVEC's compaction features by
>> leaving bits unset in the requested feature bitmap registers, you have
>> no idea how much data XSAVEC will write, unless you read XINUSE with
>> XGETBV. But, you can get aroun
On Sun, Jun 4, 2017 at 10:02 PM, Andrew Jeffery wrote:
> On Fri, 2017-06-02 at 18:29 -0700, Brendan Higgins wrote:
>> Added initial master support for Aspeed I2C controller. Supports
>> fourteen busses present in AST24XX and AST25XX BMC SoCs by Aspeed.
>>
>> Signed-off-by: Brendan Higgins
>
> I e
On Fri, Jun 16, 2017 at 01:26:19AM +0200, Luis R. Rodriguez wrote:
> On Thu, Jun 15, 2017 at 02:57:17PM -0700, Paul E. McKenney wrote:
> > On Thu, Jun 15, 2017 at 11:48:18AM -0700, Luis R. Rodriguez wrote:
> > > While reviewing RCU's interruptible swaits I noticed signals were actually
> > > not ex
On Thu, Jun 15, 2017 at 12:12 PM, Andrew Morton
wrote:
> On Wed, 14 Jun 2017 18:56:30 -0700 Kees Cook wrote:
>
>> >> Caused by commit
>> >>
>> >> 088a5ecf7581 ("include/linux/string.h: add the option of fortified
>> >> string.h functions")
>> >>
>> >> We really need to fix all the known proble
The functions _queue_empty(), _emit_ADDH(), _emit_NOP(), _emit_STZ()
and _emit_WFE() are not used. Delete them.
Signed-off-by: Matthias Kaehlcke
---
drivers/dma/pl330.c | 67 -
1 file changed, 67 deletions(-)
diff --git a/drivers/dma/pl330.c b
On Thu, Jun 15, 2017 at 09:00:58PM +0100, Wei Xu wrote:
[...]
> Since the dts part is not depended on the driver and Guodong has put this
> into another
> patch set[1], I will pick up that one.
> Thanks!
>
> [1]: https://lkml.org/lkml/2017/6/14/1049
Yeah, thanks for picking up from Guodong's p
On 06/15/2017 1:15 PM, Vivien Didelot wrote:
> Similarly to how cross-chip VLAN works, define a bitmap of multicast group
> members for a switch, now including its DSA ports, so that multicast traffic
> can be sent to all switches of the fabric.
>
> A switch may drop the frames if no user port is
On Thu, 2017-06-15 at 17:06 +, Rowand, Frank wrote:
> On Thursday, June 15, 2017 2:25 AM, Abdul Haleem
> [mailto:abdha...@linux.vnet.ibm.com] wrote:
> >
> > On Thu, 2017-06-15 at 11:30 +0530, Abdul Haleem wrote:
> > > Hi,
> > >
> > > linux-next fails to boot on powerpc Bare-metal with these
On Thu, 2017-06-15 at 16:46 -0700, Kees Cook wrote:
> On Thu, Jun 15, 2017 at 12:12 PM, Andrew Morton
> wrote:
> > On Wed, 14 Jun 2017 18:56:30 -0700 Kees Cook
> > wrote:
> >
> > > > > Caused by commit
> > > > >
> > > > > 088a5ecf7581 ("include/linux/string.h: add the option of
> > > > > fort
On Fri, 2017-06-09 at 22:47 -0700, frowand.l...@gmail.com wrote:
> From: Frank Rowand
>
> Remove "phandle" and "linux,phandle" properties from the internal
> device tree. The phandle will still be in the struct device_node
> phandle field.
>
> This is to resolve the issue found by Stephen Boyd
On Thu, Jun 08, 2017 at 03:25:42PM +0200, Christoph Hellwig wrote:
> Signed-off-by: Christoph Hellwig
> ---
> arch/hexagon/include/asm/dma-mapping.h | 2 --
> arch/hexagon/kernel/dma.c | 12 +---
> arch/hexagon/kernel/hexagon_ksyms.c| 1 -
> 3 files changed, 9 insertion
On Thu, Jun 08, 2017 at 03:25:56PM +0200, Christoph Hellwig wrote:
> This implementation is simply bogus - hexagon only has a simple
> direct mapped DMA implementation and thus doesn't care about the
> address.
>
> Signed-off-by: Christoph Hellwig
> ---
> arch/hexagon/include/asm/dma-mapping.h |
On Thu, Jun 08, 2017 at 06:10:22PM +0200, Krzysztof Kozlowski wrote:
> Remove old, dead Kconfig options (in order appearing in this commit):
> - EXPERIMENTAL is gone since v3.9;
> - NETDEV_1000 and NETDEV_1: commit f860b0522f65 ("drivers/net:
>Kconfig and Makefile cleanup"); NET_ETHERNET
From: Masaki Ota
- Support PTP Stick and Touchpad device.
- This Touchpad is Precision Touchpad(PTP),
and Stick Pointer data is the same as Mouse.
- Stick Pointer works as Mouse.
Signed-off-by: Masaki Ota
---
drivers/hid/hid-ids.h| 2 ++
drivers/hid/hid-multitouch.c | 23 +
Hi Alexey,
2017-06-14 22:11 GMT+09:00 Alexey Brodkin :
> Hi Michal,
>
> On Wed, 2017-06-14 at 15:02 +0200, Michal Marek wrote:
>> Dne 14.6.2017 v 14:40 Alexey Brodkin napsal(a):
>> >
>> > In those cases when we parse output of standard utilities like readelf
>> > etc we rely on a particular sente
On 06/15/2017 01:14 PM, Vivien Didelot wrote:
> Similarly to how cross-chip VLAN works, define a bitmap of multicast
> group members for a switch, now including its DSA ports, so that
> multicast traffic can be sent to all switches of the fabric.
>
> A switch may drop the frames if no user port is
On Thu, Jun 15, 2017 at 5:05 PM, Daniel Micay wrote:
> On Thu, 2017-06-15 at 16:46 -0700, Kees Cook wrote:
>> On Thu, Jun 15, 2017 at 12:12 PM, Andrew Morton
>> wrote:
>> > On Wed, 14 Jun 2017 18:56:30 -0700 Kees Cook
>> > wrote:
>> >
>> > > > > Caused by commit
>> > > > >
>> > > > > 088a5ecf7
On 06/15/2017 10:52 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.9.33 release.
There are 108 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be m
On 06/15/2017 10:52 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.4.73 release.
There are 46 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be ma
On 06/15/2017 10:54 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.11.6 release.
There are 13 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be ma
On Thu, Jun 15, 2017 at 11:48:19AM -0700, Luis R. Rodriguez wrote:
> There are cases where folks are using an interruptible swait when
> using kthreads. This is rather confusing given you'd expect
> interruptible waits to be -- interruptible, but kthreads are not
> interruptible ! The reason for su
2017-06-16 2:37 GMT+09:00 Matthias Kaehlcke :
> cc-option uses KBUILD_CFLAGS and KBUILD_CPPFLAGS when it determines
> whether an option is supported or not. This is fine for options used to
> build the kernel itself, however some components like the x86 boot code
> use a different set of flags.
>
>
> -Original Message-
> From: Bjorn Helgaas [mailto:helg...@kernel.org]
> Sent: Friday, June 16, 2017 5:06 AM
> To: Quentin Schulz
> Cc: Richard Zhu ; l.st...@pengutronix.de;
> bhelg...@google.com; robh...@kernel.org; mark.rutl...@arm.com;
> thomas.petazz...@free-electrons.com; devicet...@
Michal Hocko wrote:
> On Thu 15-06-17 15:03:17, David Rientjes wrote:
> > On Thu, 15 Jun 2017, Michal Hocko wrote:
> >
> > > > Yes, quite a bit in testing.
> > > >
> > > > One oom kill shows the system to be oom:
> > > >
> > > > [22999.488705] Node 0 Normal free:90484kB min:90500kB ...
> > > > [
"Rowand, Frank" writes:
> On Thursday, June 15, 2017 2:25 AM, Abdul Haleem
> [mailto:abdha...@linux.vnet.ibm.com] wrote:
>>
>> On Thu, 2017-06-15 at 11:30 +0530, Abdul Haleem wrote:
>>> Hi,
>>>
>>> linux-next fails to boot on powerpc Bare-metal with these warnings.
>>>
>>> machine booted fine o
On Thu, Jun 15, 2017 at 10:56:29AM -0700, Paul E. McKenney wrote:
[...]
> > >
> > > FWLIW, I agree. There was a smb_mb() in RT-linux's equivalent of
> > > swait_activate().
> > >
> > > https://www.spinics.net/lists/linux-rt-users/msg10340.html
> > >
> > > If the barrier goes in swait_active() t
Replace first padding in the tcp_md5sig structure with a new flag field
and address prefix length so it can be specified when configuring a new
key for TCP MD5 signature. The tcpm_flags field will only be used if the
socket option is TCP_MD5SIG_EXT to avoid breaking existing programs, and
tcpm_pref
This allows the keys used for TCP MD5 signature to be used for whole
range of addresses, specified with a prefix length, instead of only one
address as it currently is.
Signed-off-by: Bob Gilligan
Signed-off-by: Eric Mowat
Signed-off-by: Ivan Delalande
---
include/net/tcp.h | 6 +++--
net/i
Hi Thierry,
Today's linux-next merge of the drm-tegra tree got a conflict in:
Documentation/gpu/index.rst
between commit:
bed41005e617 ("drm/pl111: Initial drm/kms driver for pl111")
from the drm tree and commit:
fa6d095eb23a ("drm/tegra: Add driver documentation")
from the drm-tegra t
801 - 900 of 999 matches
Mail list logo
