On Thu, Dec 22, 2016 at 08:07:11AM +0800, Icenowy Zheng wrote:
>
>
> 22.12.2016, 06:42, "Maxime Ripard" :
> > On Thu, Dec 22, 2016 at 04:02:35AM +0800, Icenowy Zheng wrote:
> >> Lichee Pi One is a low-cost Allwinner A13-based development board, with
> >> an
On 12/22/2016 at 11:22 AM, Baoquan He wrote:
> On 12/15/16 at 11:30am, Xunlei Pang wrote:
>> CRASH_KERNEL_ADDR_MAX was missing for a long time, update it
>> with more detailed explanation.
>>
>> Cc: Robert LeBlanc
>> Cc: Baoquan He
>> Signed-off-by: Xunlei
> > > diff --git a/kernel/livepatch/patch.c b/kernel/livepatch/patch.c
> > > index 5efa262..e79ebb5 100644
> > > --- a/kernel/livepatch/patch.c
> > > +++ b/kernel/livepatch/patch.c
> > > @@ -29,6 +29,7 @@
> > > #include
> > > #include
> > > #include "patch.h"
> > > +#include "transition.h"
>
On 12/22/2016 11:02 AM, Heinrich Schuchardt wrote:
> On 12/14/2016 10:52 AM, Neil Armstrong wrote:
>
>> Hi Heinrich,
>>
>> Thanks for testing and for the report,
>> we are still struggling into finding what are these zones and how to label
>> them correctly.
>>
>> We need to identify the zones
On Fri, Dec 23, 2016 at 02:32:41AM -0500, Johannes Weiner wrote:
> On Thu, Dec 22, 2016 at 12:22:27PM -0800, Hugh Dickins wrote:
> > On Wed, 21 Dec 2016, Linus Torvalds wrote:
> > > On Wed, Dec 21, 2016 at 9:13 PM, Dave Chinner wrote:
> > > > I unmounted the fs, mkfs'd it
Image Sensor Controller has an internal image processor.
It can convert raw format to the other formats, like
RGB565, YUV420P. A module parameter 'sensor_preferred'
is used to enable or disable the pipeline function.
Some v4l2 controls are added to tuning the image when
the pipeline function is
On Fri 2016-12-23 10:46:43, Sergey Senozhatsky wrote:
> not every switch to printk_safe is "dictated" by logbuf_lock.
> down_trylock_console_sem(), for instance, takes semaphore spin_lock
> which already may be locked on the same CPU (*), so we need to be
> in safe mode:
>
> vprintk_emit()
>
Currently the notifier of pvclock_gtod_notify() get invoked
frequently due to the periodic update_wall_time(). This might
slow down the system a little bit as there might be redundant
execution code path and unnecessary lock contention
in update_pvclock_gtod(), which was found when I was doing
Hello,
On Thu, Dec 22, 2016 at 02:35:01PM +0100, M'boumba Cedric Madianga wrote:
> This patch adds support for the STM32F4 I2C controller.
>
> Signed-off-by: M'boumba Cedric Madianga
> ---
> drivers/i2c/busses/Kconfig | 10 +
> drivers/i2c/busses/Makefile
Hello!
On 12/23/2016 9:52 AM, Lu Baolu wrote:
If xhci host fails to response to a command, the command
s/response/respond/.
watchdog timer will be fired. The callback function will
abort and clear current command and restart the command
execution. If driver fails to restart command
This patch removes unnecessary return statement using spatch tool
Signed-off-by: Rahul Krishnan
---
drivers/staging/xgifb/vb_init.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/staging/xgifb/vb_init.c b/drivers/staging/xgifb/vb_init.c
(localversion-next is next-20161223)
arch/x86/boot/string.c | 1 +
arch/x86/boot/string.h | 9 +
2 files changed, 10 insertions(+)
diff --git a/arch/x86/boot/string.c b/arch/x86/boot/string.c
index cc3bd58..9e240fc 100644
--- a/arch/x86/boot/string.c
+++ b/arch/x86/boot/string.c
@@ -14,6 +
On Thu, 22 Dec 2016, Sebastian Andrzej Siewior wrote:
> The current CPU hotplug is outdated. During the update to what we
> currently have I rewrote it partly and moved to sphinx format.
>
> Cc: Jonathan Corbet
> Cc: Mauro Carvalho Chehab
All LED-setting functions in fujitsu-laptop are currently assigned to
the brightness_set callback, which is incorrect because they can sleep
(due to their use of call_fext_func(), which in turn issues ACPI calls)
and the documentation (in include/linux/leds.h) clearly states they must
not. Assign
I would like to write code that discovers the nmaespace setup on a live
system. The NS_GET_PARENT and NS_GET_USERNS ioctl() operations added in
Linux 4.9 provide much of what I want, but there are still a couple of
small pieces missing. Those pieces are added with this patch series.
Here's an
I'd like to write code that discovers the user namespace hierarchy on
a running system, and also shows who owns the various user namespaces.
Currently, there is no way of getting the owner UID of a user
namespace. Therefore, this patch adds an NS_GET_CREATOR_UID ioctl()
that fetches the (munged)
Linux 4.9 added two ioctl() operations that can be used to discover:
* the parental relationships for hierarchical namespaces (user and PID)
[NS_GET_PARENT]
* the user namespaces that owns a specified non-user-namespace
[NS_GET_USERNS]
For no good reason that I can glean, NS_GET_USERNS was
When VDMA is configured for more than one frame in the h/w
for example h/w is configured for n number of frames and user
Submits n number of frames and triggered the DMA using issue_pending API.
In the current driver flow we are submitting one frame at a time
but we should submit all the n number
When driver is handling AXI DMA SoftIP
When user submits multiple descriptors back to back on the S2MM(recv)
side with the current driver flow the last buffer descriptor next bd
points to a invalid location resulting the invalid data or errors in the
DMA engine.
This patch fixes this issue by
On Thu, Dec 15, 2016 at 4:05 PM, Rob Herring wrote:
> On Wed, Dec 14, 2016 at 10:58 AM, Bartosz Golaszewski
> wrote:
>> 2016-12-13 20:27 GMT+01:00 Rob Herring :
>>> On Sun, Dec 11, 2016 at 11:21:44PM +0100, Bartosz Golaszewski wrote:
Hi Laurent Pinchart,
Sorry for the delay in the reply.
Thanks for the review...
>
> Hi Kedar,
>
> On Monday 19 Dec 2016 15:39:43 Appana Durga Kedareswara Rao wrote:
> > Hi Laurent Pinchart,
> >
> > Thanks for the review...
> >
> > > > + if (!chan->idle)
> > > > +
.uk>
Acked-by: Marek Vasut <ma...@denx.de>
> ---
>
> Build log of next-20161223 is at:
> https://travis-ci.org/sudipm-mukherjee/parport/jobs/186246753
>
> This error will be fixed but it will now uncover the next error as the
> build goes on.
>
> drivers/mtd/nand/xwa
Hi Lars,
On Mon, Dec 12, 2016 at 6:15 PM, Lars-Peter Clausen wrote:
> On 12/06/2016 12:12 PM, Bartosz Golaszewski wrote:
>> We're already using libiio to read the measured data from the power
>> monitor, that's why we'd like to use the iio framework for
>> power-cycling the
On Thu, Dec 22, 2016 at 04:03:56PM -0800, Chris Leech wrote:
> Of course, looks like I've screwed up my bisect run on this so I'm still
> taking a look. It triggers for me with 'hdparm -B /dev/vda' but may
> also depend on kernel configuration.
>
> I started with the fedora rawhide config with a
On Fri, 23 Dec 2016, Michal Hocko wrote:
> > The offering of defer breaks backwards compatibility with previous
> > settings of defrag=madvise, where we could set madvise(MADV_HUGEPAGE) on
> > .text segment remap and try to force thp backing if available but not
> > directly reclaim for non
Dear Maintainers
I'd like to ask for the status of this patch since we hit the
issue too during our testing on md raid1.
Split remainder bio_A was queued ahead, following by bio_B for
lower device, at this moment raid start freezing, the loop take
out bio_A firstly and deliver it, which will
Hi Shawn,
Do you think, below change should be fine?
I am still checking on what we discussed on Patch2.
why I am asking is because - for HS400 in SDHC-MSM, we do the DLL
re-calibration as per the HW sequence. So it is done in both the cases,
for HS400 mode without and with enhanced strobe
' in declaration of 'MODULE_DEVICE_TABLE'
[-Werror=implicit-int]
It missed to include the header file.
Signed-off-by: Sudip Mukherjee <sudip.mukher...@codethink.co.uk>
---
Build log of next-20161223 is at:
https://travis-ci.org/sudipm-mukherjee/parport/jobs/186246753
This
On Thu 22-12-16 13:05:27, David Rientjes wrote:
> On Thu, 22 Dec 2016, Michal Hocko wrote:
>
> > > Currently, when defrag is set to "madvise", thp allocations will direct
> > > reclaim. However, when defrag is set to "defer", all thp allocations do
> > > not attempt reclaim regardless of
This patch series fixes below bugs in DMA and VDMA IP's
---> Do not start VDMA until frame buffer is processed by the h/w Fix
---> bug in Multi frame sotres handling in VDMA Fix issues w.r.to multi
---> frame descriptors submit with AXI DMA S2MM(recv) Side.
Kedareswara rao Appana (3):
Add channel idle state to ensure that dma descriptor is not
submitted when VDMA engine is in progress.
Reviewed-by: Jose Abreu
Signed-off-by: Kedareswara rao Appana
---
Changes fro v2:
---> Add idle check in the reset as suggested by Jose Abreu
--->
ocalversion-next is next-20161223)
arch/x86/include/asm/kexec-bzimage64.h | 16
arch/x86/purgatory/purgatory.c | 8 ++--
2 files changed, 18 insertions(+), 6 deletions(-)
diff --git a/arch/x86/include/asm/kexec-bzimage64.h
b/arch/x86/include/asm/kexec-bzimage64.h
index
> Il giorno 22 dic 2016, alle ore 10:59, Paolo Valente
> ha scritto:
>
>>
>> Il giorno 17 dic 2016, alle ore 01:12, Jens Axboe ha scritto:
>>
>> This adds a set of hooks that intercepts the blk-mq path of
>> allocating/inserting/issuing/completing
Release IO memory mapping, if i2c_dw_pci_probe is not successful.
Signed-off-by: Arvind Yadav
---
drivers/i2c/busses/i2c-designware-pcidrv.c | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/drivers/i2c/busses/i2c-designware-pcidrv.c
Unmap and release PCI BARs, if dw_mci_pci_probe is not successful.
Signed-off-by: Arvind Yadav
---
drivers/mmc/host/dw_mmc-pci.c |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/mmc/host/dw_mmc-pci.c b/drivers/mmc/host/dw_mmc-pci.c
Am Donnerstag, 22. Dezember 2016, 17:38:00 CET schrieb Cyrille Pitchen:
Hi Cyrille,
> This patchs allows to combine the AES and SHA hardware accelerators on
> some Atmel SoCs. Doing so, AES blocks are only written to/read from the
> AES hardware. Those blocks are also transferred from the AES to
it the initialization of sha_regions to {{0,0}} was added.
Patch was compile tested with: x86_64_defconfig (implies CONFIG_KEXEC=y)
Patch is against 4.9.0 (localversion-next is next-20161223)
arch/x86/include/asm/kexec-bzimage64.h | 16
arch/x86/purgatory/purgatory.c
On 12/23/2016 10:07 AM, Geert Uytterhoeven wrote:
> BTW, I'm not an IIO expert, but from my limited knowledge, it looks like "O"
> support in IIO is limited to DACs?
Depends on what you categorize as DACs. There are also
potentiometer/rheostat drivers. They are kind of like DACs but the unit you
On Fri, Dec 23, 2016 at 09:49:53AM +0100, Michael Wang wrote:
> Dear Maintainers
>
> I'd like to ask for the status of this patch since we hit the
> issue too during our testing on md raid1.
>
> Split remainder bio_A was queued ahead, following by bio_B for
> lower device, at this moment raid
On Fri, 2016-12-23 at 15:41 +0530, Arvind Yadav wrote:
> Release IO memory mapping, if i2c_dw_pci_probe is not successful.
>
Second NAK, and seems (due to kbot message) you didn't even bother to
compile test.
What are you doing?
> Signed-off-by: Arvind Yadav
> ---
>
On Thu, 2016-12-22 at 19:07 -0500, George Spelvin wrote:
> Hannes Frederic Sowa wrote:
> > A lockdep test should still be done. ;)
>
> Adding might_lock() annotations will improve coverage a lot.
Might be hard to find the correct lock we take later down the code
path, but if that is possible,
On Thu, 8 Dec 2016, Josh Poimboeuf wrote:
> klp_patch_object()'s callers already ensure that the object is loaded,
> so its call to klp_is_object_loaded() is unnecessary.
>
> This will also make it possible to move the patching code into a
> separate file.
>
> Signed-off-by: Josh Poimboeuf
On Thu, Dec 22, 2016 at 6:04 PM, Vitaly Wool wrote:
> On Thu, Dec 22, 2016 at 10:55 PM, Dan Streetman wrote:
>> On Sun, Dec 18, 2016 at 3:15 AM, Vitaly Wool wrote:
>>> On Tue, Nov 29, 2016 at 11:39 PM, Andrew Morton
>>>
This patch contains the following minor fixup:
* Fixed overflow handling since u64 delta would lose the MSB sign bit.
* Remove unnecessary local64_set().
* Coding style and make use of GENMASK_ULL macro.
Cc: Peter Zijlstra
Cc: Borislav Petkov
We drop csumed packet when do XDP for packets. This breaks
XDP_PASS when GUEST_CSUM is supported. Fix this by allowing csum flag
to be set. With this patch, simple TCP works for XDP_PASS.
Cc: John Fastabend
Signed-off-by: Jason Wang
---
Since we use EWMA to estimate the size of rx buffer. When rx buffer
size is underestimated, it's usual to have a packet with more than one
buffers. Consider this is not a bug, remove the warning and correct
the comment before XDP linearizing.
Cc: John Fastabend
Hi Ivan,
[auto build test WARNING on linus/master]
[also build test WARNING on v4.9 next-20161223]
[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/ivan-stoyanov-amk-drives-bg/dmaengine-ipu
Commit f600b6905015 ("virtio_net: Add XDP support") leaves the case of
small receive buffer untouched. This will confuse the user who want to
set XDP but use small buffers. Other than forbid XDP in small buffer
mode, let's make it work. XDP then can only work at skb->data since
virtio-net create
We don't update ewma rx buf size in the case of XDP. This will lead
underestimation of rx buf size which causes host to produce more than
one buffers. This will greatly increase the possibility of XDP page
linearization.
Cc: John Fastabend
Signed-off-by: Jason Wang
When VIRTIO_NET_F_GUEST_UFO is negotiated, host could still send UFO
packet that exceeds a single page which could not be handled
correctly by XDP. So this patch forbids setting XDP when GUEST_UFO is
supported. While at it, forbid XDP for ECN (which comes only from GRO)
too to prevent user from
Now we in fact don't allow XDP for big packets, remove its codes.
Cc: John Fastabend
Signed-off-by: Jason Wang
---
drivers/net/virtio_net.c | 44 +++-
1 file changed, 3 insertions(+), 41 deletions(-)
diff
Hi Linus,
Due to time constraints and personal issues Guenter and I decided that this
window will be a pull from another location.
So please pull from 'watchdog-for-linus-v4.10' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git
It contains the following
On Monday 19 December 2016 10:07 PM, Rob Herring wrote:
On Wed, Dec 07, 2016 at 11:55:59AM -0500, Anurup M wrote:
1) Device tree bindings for Hisilicon SoC PMU.
2) Add example for Hisilicon L3 cache and MN PMU.
3) Add child nodes of L3C and MN in djtag bindings example.
Signed-off-by: Anurup
On Fri 2016-12-23 10:24:35, Miroslav Benes wrote:
> > > > diff --git a/kernel/livepatch/patch.c b/kernel/livepatch/patch.c
> > > > index 5efa262..e79ebb5 100644
> > > > --- a/kernel/livepatch/patch.c
> > > > +++ b/kernel/livepatch/patch.c
> > > > @@ -29,6 +29,7 @@
> > > > #include
> > > >
On Monday 19 December 2016 10:01 PM, Rob Herring wrote:
On Wed, Dec 07, 2016 at 11:55:19AM -0500, Anurup M wrote:
From: Tan Xiaojun
Add Hisilicon HiP05/06/07 Djtag dts bindings for CPU and IO Die
Signed-off-by: Tan Xiaojun
Signed-off-by:
On Thu, Dec 22, 2016 at 06:48:01PM -0600, Bjorn Helgaas wrote:
> If we didn't want to use pcibios_resource_to_bus() here for some
> reason, we should at least add a comment about why we think it's OK to
> use a CPU physical address as an IOVA.
Even if there are no such x86 systems out there, I
On Wed, Dec 21, 2016 at 07:46:33PM +0100, Nicolai Hähnle wrote:
> diff --git a/include/linux/ww_mutex.h b/include/linux/ww_mutex.h
> index a5960e5..b2eaaab 100644
> --- a/include/linux/ww_mutex.h
> +++ b/include/linux/ww_mutex.h
> @@ -186,11 +186,6 @@ static inline void ww_acquire_fini(struct
On Fri, 2016-12-23 at 11:04 +0100, Daniel Borkmann wrote:
> On 12/22/2016 05:59 PM, Hannes Frederic Sowa wrote:
> > On Thu, 2016-12-22 at 08:07 -0800, Andy Lutomirski wrote:
> > > On Thu, Dec 22, 2016 at 7:51 AM, Hannes Frederic Sowa
> > > wrote:
> > > > On Thu,
Adding a resource managed method to obtain nvmem cell
using cell index.
Signed-off-by: Vivek Gautam
---
drivers/nvmem/core.c | 33 +
include/linux/nvmem-consumer.h | 8
2 files changed, 41 insertions(+)
diff --git
On Fri, Dec 23, 2016 at 01:46:42PM +0900, Masahiro Yamada wrote:
> The top-level Makefile defines:
>
> CPP = $(CC) -E
hum, so that'd work for running from top level, but I guess
it fails for compiling from other places..? like tools/perf
jirka
>
> So, $(CC) -E can be replaced
Fork out a method to get nvmem cell using cell index
in the phandle for the cell.
This helps in getting the lone cell given in the phandle,
without mentioning the cell name in device tree.
Signed-off-by: Vivek Gautam
---
drivers/nvmem/core.c | 35
branch.
- Tested with next-20161223 tag and a revert to patch [1], to fix
build issue on arm64, on db410c target. Able to read temperatures
from thermal sensors.
Vivek Gautam (2):
nvmem: core: Allow getting cell by index in phandle
nvmem: core: Add a resource managed API to get cell
Hi Laurent,
Am Freitag, den 23.12.2016, 13:23 +0200 schrieb Laurent Pinchart:
> Hello,
>
> On Friday 23 Dec 2016 11:58:57 Philipp Zabel wrote:
> > Am Donnerstag, den 15.12.2016, 18:05 + schrieb Ramiro Oliveira:
> > > Up until now optional functions in the reset API were similar to the non
>
On 19/12/2016 10:47, Paolo Bonzini wrote:
> On EOI, there is no need to set KVM_REQ_EVENT unconditionally. The PPR
> update is already setting it if resetting the ISR bit causes PPR to
> decrease. Even a level-triggered IOAPIC interrupt will set KVM_REQ_EVENT
> on a reinjection (ioapic_service
On 23.12.2016 08:46, Lu Baolu wrote:
In command timer function, xhci_handle_command_timeout(), xhci->lock
is unlocked before call into xhci_abort_cmd_ring(). This might cause
race between the timer function and the event handler.
The xhci_abort_cmd_ring() function sets the CMD_RING_ABORT bit in
>> Thus recommended dma_set_mask_and_coherent() call, instead of checking
>> if platform supports 64-bit DMA addressing, unconditionally enables
>> 64-bit DMA addressing. In case of device actually can't do DMA to 64-bit
>> addresses (e.g. because of limitations in PCIe controller), this breaks
>>
Hi,
2016-12-22 20:11 GMT+01:00 Uwe Kleine-König :
> Hello,
>
> On Thu, Dec 22, 2016 at 02:35:02PM +0100, M'boumba Cedric Madianga wrote:
>> @@ -337,6 +350,16 @@
>> slew-rate = <2>;
>> };
>>
Hello Phil,
Às 1:09 AM de 12/23/2016, Phil Reid escreveu:
> G'day Joao,
> On 23/12/2016 01:06, Joao Pinto wrote:
>> Às 4:57 PM de 12/22/2016, Phil Reid escreveu:
>>> On 22/12/2016 23:47, Joao Pinto wrote:
Hello Phil,
Às 3:42 PM de 12/22/2016, Phil Reid escreveu:
> G'day
On 12/22/2016 06:25 PM, Andy Lutomirski wrote:
On Thu, Dec 22, 2016 at 8:59 AM, Hannes Frederic Sowa
[...]
I wondered if bpf program loading should have used the module loading
infrastructure from the beginning...
That would be way too complicated and would be nasty for the unprivileged
TL;DR
drop the last patch, check whether memory cgroup is enabled and retest
with cgroup_disable=memory to see whether this is memcg related and if
it is _not_ then try to test with the patch below
On Thu 22-12-16 22:46:11, Nils Holland wrote:
> On Thu, Dec 22, 2016 at 08:17:19PM +0100, Michal
Hi Ramiro,
Am Donnerstag, den 15.12.2016, 18:05 + schrieb Ramiro Oliveira:
> Up until now optional functions in the reset API were similar to the non
> optional.
>
> This patch corrects that, while maintaining compatibility with existing
> drivers.
>
> As suggested here:
We are happy to announce the release of ipvsadm v1.29.
ipvsadm is a utility to administer the kernels IPVS/LVS load-balancer service
It has been far too long since the last ipvsadm release. Even-though
only two changes to the ipvsadm tool happened since last release, a
release must be made as
and thread in [1] and [2]. Missed them
earlier. The patches 1/2 and 2/2 remain unchanged.
- Based on torvald's master branch.
- Tested with next-20161223 tag and a revert to patch [1], to fix
build issue on arm64 (as indicated in the thread [2]), on
db410c target. Able to read temperatures
Hi Arvind,
[auto build test WARNING on wsa/i2c/for-next]
[also build test WARNING on v4.9 next-20161223]
[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/Arvind-Yadav/i2c-busses-i2c-designware
On 23.12.2016 11:48, Peter Zijlstra wrote:
On Wed, Dec 21, 2016 at 07:46:33PM +0100, Nicolai Hähnle wrote:
diff --git a/include/linux/ww_mutex.h b/include/linux/ww_mutex.h
index a5960e5..b2eaaab 100644
--- a/include/linux/ww_mutex.h
+++ b/include/linux/ww_mutex.h
@@ -186,11 +186,6 @@ static
On 12/23/2016 11:00 AM, Geert Uytterhoeven wrote:
> Hi Lars,
>
> On Mon, Dec 12, 2016 at 6:15 PM, Lars-Peter Clausen wrote:
>> On 12/06/2016 12:12 PM, Bartosz Golaszewski wrote:
>>> We're already using libiio to read the measured data from the power
>>> monitor, that's why we'd
On 12/23/2016 11:59 AM, Hannes Frederic Sowa wrote:
On Fri, 2016-12-23 at 11:04 +0100, Daniel Borkmann wrote:
On 12/22/2016 05:59 PM, Hannes Frederic Sowa wrote:
On Thu, 2016-12-22 at 08:07 -0800, Andy Lutomirski wrote:
[...]
The hashing is not a proper sha1 neither, unfortunately. I think
On Fri, Dec 23, 2016 at 4:19 AM, Nick Desaulniers
wrote:
> On Tue, Dec 13, 2016 at 08:00:01PM +0100, Pavel Machek wrote:
>> Actually.. the ACPI cleanup is fine. You did well :-).
>> Pavel
>
> Cool,
Hi Uwe,
Thanks for your comments.
Please see below my answers and one question regarding duty cycle:
2016-12-23 10:00 GMT+01:00 Uwe Kleine-König :
> Hello,
>
> On Thu, Dec 22, 2016 at 02:35:01PM +0100, M'boumba Cedric Madianga wrote:
>> This patch adds support for
Hi Lars,
On Fri, Dec 23, 2016 at 12:35 PM, Lars-Peter Clausen wrote:
> On 12/23/2016 11:00 AM, Geert Uytterhoeven wrote:
>> On Mon, Dec 12, 2016 at 6:15 PM, Lars-Peter Clausen wrote:
>>> On 12/06/2016 12:12 PM, Bartosz Golaszewski wrote:
We're already
On Fri 23-12-16 13:18:51, Nils Holland wrote:
> On Fri, Dec 23, 2016 at 11:51:57AM +0100, Michal Hocko wrote:
> > TL;DR
> > drop the last patch, check whether memory cgroup is enabled and retest
> > with cgroup_disable=memory to see whether this is memcg related and if
> > it is _not_ then try to
On Fri, 16 Dec 2016, Josh Poimboeuf wrote:
> On Fri, Dec 16, 2016 at 05:55:55PM +0100, Petr Mladek wrote:
> > On Thu 2016-12-08 12:08:36, Josh Poimboeuf wrote:
> > > The sysfs enabled value is a boolean, so kstrtobool() is a better fit
> > > for parsing the input string since it does the range
On Thu, 8 Dec 2016, Josh Poimboeuf wrote:
> Once we have a consistency model, patches and their objects will be
> enabled and disabled at different times. For example, when a patch is
> disabled, its loaded objects' funcs can remain registered with ftrace
> indefinitely until the unpatching
Hello,
On Friday 23 Dec 2016 11:58:57 Philipp Zabel wrote:
> Am Donnerstag, den 15.12.2016, 18:05 + schrieb Ramiro Oliveira:
> > Up until now optional functions in the reset API were similar to the non
> > optional.
> >
> > This patch corrects that, while maintaining compatibility with
On Fri, Dec 23, 2016 at 12:03:21AM +, Al Viro wrote:
> Assorted cleanups and fixes all over the place.
Fix for aio compat in !CONFIG_AIO builds folded in, commit message on
seq_file patch unmangled. Other than that, identical to the previous.
The following changes since commit
Hi!
> > [...]
> >
> > static int isp_subdev_notifier_bound(struct v4l2_async_notifier *async,
> > diff --git a/drivers/media/platform/video-bus-switch.c
> > b/drivers/media/platform/video-bus-switch.c
> > index 1a5d944..3a2d442 100644
> > --- a/drivers/media/platform/video-bus-switch.c
> > +++
On Fri, Dec 16, 2016 at 3:13 PM, Vikas Shivappa
wrote:
> To provide reliable output to the user, cqm throws error when it does
> not have enough RMIDs to monitor depending upon the mode user choses.
> This also takes care to not overuse RMIDs. Default is LAZY mode.
On Thu 2016-12-22 13:56:38, Valdis Kletnieks wrote:
> commit 7fd8329ba502ef76dd91db561c7aed696b2c7720
> Author: Petr Mladek
> Date: Wed Sep 21 13:47:22 2016 +0200
>
> taint/module: Clean up global and module taint flags handling
>
> Contains this chunk:
Information
On Fri, Dec 16, 2016 at 03:12:55PM -0800, Vikas Shivappa wrote:
> +Continuous monitoring
> +-
> +A new file cont_monitoring is added to perf_cgroup which helps to enable
> +cqm continuous monitoring. Enabling this field would start monitoring of
> +the cgroup without perf being
From: Ivan Stoyanov
In commit 3d8cc00073d6750ffe883685e49b2e4a0f596370 are consolidate functions
ipu_irq_err and ipu_irq_fn considered for duplicated.
Since this patch ipu driver does not work properly and cause kernel freeze
during booting.
[1.018314]
dw8250_acpi_match is used only when ACPI is enabled. Fix the following
gcc warning when W=1 is set:
drivers/tty/serial/8250/8250_dw.c:640:36: warning: 'dw8250_acpi_match'
defined but not used [-Wunused-const-variable=]
Signed-off-by: Jisheng Zhang
---
On Thu, 8 Dec 2016, Josh Poimboeuf wrote:
> Move functions related to the actual patching of functions and objects
> into a new patch.c file.
>
> Signed-off-by: Josh Poimboeuf
Acked-by: Miroslav Benes
Miroslav
On Fri, Dec 23, 2016 at 10:00:08AM +0100, Micha?? K??pie?? wrote:
> All LED-setting functions in fujitsu-laptop are currently assigned to
> the brightness_set callback, which is incorrect because they can sleep
> (due to their use of call_fext_func(), which in turn issues ACPI calls)
> and the
On Fri, Dec 23, 2016 at 02:02:14AM +, Dashi DS1 Cao wrote:
> The kernel version is "RELEASE: 3.10.0-327.36.3.el7.x86_64". It was the
> latest kernel release of CentOS 7.2 at that time, or maybe still now.
This would be the point where we ask you to run a recent upstream kernel
and try and
After we linearize page, we should xmit this page instead of the page
of first buffer which may lead unexpected result. With this patch, we
can see correct packet during XDP_TX.
Cc: John Fastabend
Signed-off-by: Jason Wang
---
We don't put page during linearizing, the would cause leaking when
xmit through XDP_TX or the packet exceeds PAGE_SIZE. Fix them by
put page accordingly. Also decrease the number of buffers during
linearizing to make sure caller can free buffers correctly when packet
exceeds PAGE_SIZE. With this
When XDP_PASS were determined for linearized packets, we try to get
new buffers in the virtqueue and build skbs from them. This is wrong,
we should create skbs based on existed buffers instead. Fixing them by
creating skb based on xdp_page.
With this patch "ping 192.168.100.4 -s 3900 -M do" works
On 12/22/2016 05:59 PM, Hannes Frederic Sowa wrote:
On Thu, 2016-12-22 at 08:07 -0800, Andy Lutomirski wrote:
On Thu, Dec 22, 2016 at 7:51 AM, Hannes Frederic Sowa
wrote:
On Thu, 2016-12-22 at 16:41 +0100, Jason A. Donenfeld wrote:
On Thu, Dec 22, 2016 at 4:33 PM,
On Fri, Dec 23, 2016 at 03:41:33PM +0530, Arvind Yadav wrote:
> Release IO memory mapping, if i2c_dw_pci_probe is not successful.
Point of pcim_iomap_regions() is that the regions are released
automatically. So there is no need for explicit release.
On Fri, Dec 23, 2016 at 11:51:57AM +0100, Michal Hocko wrote:
> TL;DR
> drop the last patch, check whether memory cgroup is enabled and retest
> with cgroup_disable=memory to see whether this is memcg related and if
> it is _not_ then try to test with the patch below
Right, it seems we might be
1 - 100 of 560 matches
Mail list logo