On Fri, Apr 01, 2016 at 08:38:23AM -0600, Jens Axboe wrote:
> On 04/01/2016 08:34 AM, Sudip Mukherjee wrote:
> >We were checking for iter to be NULL after dereferencing it. There is
> >actually no need to check for iter to be NULL as all the callers of
> >blk_rq_map_user_iov() does call it with a v
Signed-off-by: Luca Abeni
---
include/uapi/linux/sched.h | 1 +
kernel/sched/core.c| 3 ++-
kernel/sched/deadline.c| 3 ++-
3 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/include/uapi/linux/sched.h b/include/uapi/linux/sched.h
index cc89dde..9279562 100644
--- a/includ
On Fri, Apr 1, 2016 at 9:30 AM, Neil Armstrong wrote:
> On 03/31/2016 03:36 PM, Rob Herring wrote:
>> On Thu, Mar 31, 2016 at 3:58 AM, Linus Walleij
>> wrote:
>>> On Fri, Mar 25, 2016 at 3:48 PM, Rob Herring wrote:
On Thu, Mar 24, 2016 at 05:50:09PM +0100, Neil Armstrong wrote:
> Add p
Now that the inactive timer can be armed to fire at the 0-lag time,
it is possible to use inactive_task_timer() to update the total
-deadline utilization (dl_b->total_bw) at the correct time, fixing
dl_overflow() and __setparam_dl().
Signed-off-by: Luca Abeni
---
kernel/sched/core.c | 36 +++
The active utilisation here is defined as the total utilisation of the
active (TASK_RUNNING) tasks queued on a runqueue. Hence, it is increased
when a task wakes up and is decreased when a task blocks.
This might need to be fixed / improved by decreasing the active
utilisation at the so-called "0-l
On 2016.04.01 05:40 Rafael J. Wysocki wrote:
> On Friday, April 01, 2016 11:20:42 AM Jörg Otte wrote:
>> 2016-03-31 17:43 GMT+02:00 Rafael J. Wysocki :
>>> On Thursday, March 31, 2016 05:25:18 PM Jörg Otte wrote:
2016-03-31 13:42 GMT+02:00 Rafael J. Wysocki :
> On Thursday, March 31, 2016
This patch implements a more theoretically sound algorithm for
thracking the active utilisation: instead of decreasing it when a
task blocks, use a timer (the "inactive timer", named after the
"Inactive" task state of the GRUB algorithm) to decrease the
active utilisaation at the so called "0-lag t
Hi all,
this patchset implements CPU reclaiming (using the GRUB algorithm[1])
for SCHED_DEADLINE: basically, this feature allows SCHED_DEADLINE tasks
to consume more than their reserved runtime, up to a maximum fraction
of the CPU time (so that other tasks are left some spare CPU time to
execute),
On Fri, Apr 1, 2016 at 1:57 AM, Krzysztof Kozlowski
wrote:
> Fix following DTC warnings in cros-adc-thermistors:
> Warning (unit_address_vs_reg): Node /adc@12D1/ncp15wb473@3 has a unit
> name, but no reg property
> Warning (unit_address_vs_reg): Node /adc@12D1/ncp15wb473@4 has a unit
> n
Hi Vivek,
[auto build test ERROR on rockchip/for-next]
[also build test ERROR on v4.6-rc1 next-20160401]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Vivek-Gautam/phy-Group-vendor-specific
On 1 April 2016 at 08:22, Neil Armstrong wrote:
> In order to support the Dual-Timer on the Oxford Semiconductor OX810SE SoC,
> implement variable counter width, keeping 32bit as default width.
> Add new compatible string oxsemi,ox810se-rps-timer in order to select
> the 24bit counter width.
>
> S
I am trying to clean up the documentation of the NBD protocol. NBD's
support for Force Unit Access (FUA) was modelled on the linux kernel
block layer. When I added support a few years ago, I omitted to find
out exactly what types of request it applies to. Obviously it applies
to write requests, but
On Fri, 1 Apr 2016 22:13:43 +0800
kbuild test robot wrote:
> Hi Boris,
>
> [auto build test WARNING on next-20160401]
> [cannot apply to v4.6-rc1 v4.5-rc7 v4.5-rc6 v4.6-rc1]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improving th
Hi,
* Tony Lindgren [160331 10:04]:
> * Keerthy [160331 02:26]:
> >
> >
> > On Thursday 31 March 2016 12:00 PM, Tero Kristo wrote:
> > >On 03/31/2016 12:32 AM, Tony Lindgren wrote:
> > >>* Tony Lindgren [160330 14:19]:
> > >>>* Keerthy [160314 05:04]:
> > This is w.r.t J6/J6eco: 32clk is
On Fri 2016-04-01 15:39:44, Petr Mladek wrote:
> On Fri 2016-03-25 14:34:47, Josh Poimboeuf wrote:
> > These patches are still a work in progress, but Jiri asked that I share
> > them before I go on vacation next week. Based on origin/master because
> > it has CONFIG_STACK_VALIDATION.
>
> I have
Hello Minchan,
On (03/31/16 15:34), Sergey Senozhatsky wrote:
> > I tested with you suggested parameter.
> > In my side, win is better compared to my previous test but it seems
> > your test is so fast. IOW, filesize is small and loops is just 1.
> > Please test filesize=500m loops=10 or 20.
fio
On Fri, 1 Apr 2016, Jiri Kosina wrote:
> On Tue, 29 Mar 2016, Jiri Kosina wrote:
>
> > Agreed; I think we should be safe applying all the alternatives (with
> > paravirt being really just a special case of those) to the coming module
> > at the very last phase; they really are required only dur
On Fri, Apr 01, 2016 at 03:30:17PM +0300, Vladimir Davydov wrote:
> When we call __kmem_cache_shrink on memory cgroup removal, we need to
> synchronize kmem_cache->cpu_partial update with put_cpu_partial that
> might be running on other cpus. Currently, we achieve that by using
> kick_all_cpus_sync
Stephen Warren writes:
> On 03/31/2016 06:28 PM, Eric Anholt wrote:
>> This approximately triples write performance for the SD card. My card
>> is too full of important data to collect very reliable numbers, but I
>> see 271.361% +/- 166.742% improvement (n=3 before, 6 after), for 'dd
>> if=/dev
On 04/01/2016 05:19 PM, Rob Herring wrote:
> On Fri, Apr 1, 2016 at 9:30 AM, Neil Armstrong
> wrote:
>>>
>>> Rob
>>>
>>
>> Hi,
>>
>> What should I use ?
>
> Maybe gpio-ranges as you asked. Not really sure as I haven't used it.
If I use gpio-ranges I can get rid of gpio-bank and ngpios propertie
Make xen_xlate_map_ballooned_pages work with 64K pages. In that case
Kernel pages are 64K in size but Xen pages remain 4K in size. Xen pfns
refer to 4K pages.
Signed-off-by: Shannon Zhao
Reviewed-by: Stefano Stabellini
---
drivers/xen/xlate_mmu.c | 38 +++---
1 f
This patch set adds ACPI support for Xen Dom0 on ARM64. The relevant Xen
ACPI on ARM64 design document could be found from [1].
This patch set adds a new FDT node "uefi" under /hypervisor to pass UEFI
information. Introduce a bus notifier of AMBA and Platform bus to map
the new added device's MMIO
Add a new type of Xen map space for Dom0 to map device's MMIO region.
Signed-off-by: Shannon Zhao
---
include/xen/interface/memory.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/xen/interface/memory.h b/include/xen/interface/memory.h
index 2ecfe4f..9aa8988 100644
--- a/include/xen
Add a bus_notifier for platform bus device in order to map the device
mmio regions when DOM0 booting with ACPI.
Signed-off-by: Shannon Zhao
Acked-by: Stefano Stabellini
---
drivers/xen/Makefile | 1 +
drivers/xen/arm-device.c | 141 +++
2 files
Sadly, hardware turbo mode buttons are few and far between in these
degenerate times. Add a software control at /proc/sys/turbo_mode.
Unfortunately, Linux graphical environments have become very
heavy-weight and are essentially unusable on non-Turbo systems. The
VT console works very well, thoug
Use xen_xlate_map_ballooned_pages to setup grant table. Then it doesn't
rely on DT or ACPI to pass the start address and size of grant table.
Signed-off-by: Shannon Zhao
Acked-by: Stefano Stabellini
---
arch/arm/xen/enlighten.c | 13 -
1 file changed, 4 insertions(+), 9 deletions(-)
ACPI 6.0 introduces a new table STAO to list the devices which are used
by Xen and can't be used by Dom0. On Xen virtual platforms, the physical
UART is used by Xen. So here it hides UART from Dom0.
CC: "Rafael J. Wysocki" (supporter:ACPI)
CC: Len Brown (supporter:ACPI)
CC: linux-a...@vger.kerne
Sync the changes of HVM_PARAM_CALLBACK_VIA ABI introduced by
Xen commit (public/hvm: export the HVM_PARAM_CALLBACK_VIA
ABI in the API).
Signed-off-by: Shannon Zhao
Acked-by: Stefano Stabellini
---
include/xen/interface/hvm/params.h | 27 +--
1 file changed, 21 insertion
When running on Xen hypervisor, runtime services are supported through
hypercall. Add a Xen specific function to initialize runtime services.
Signed-off-by: Shannon Zhao
Reviewed-by: Stefano Stabellini
---
arch/arm/include/asm/xen/xen-ops.h | 6 ++
arch/arm/xen/Makefile|
When it's a Xen domain0 booting with ACPI, it will supply a /chosen and
a /hypervisor node in DT. So check if it needs to enable ACPI.
Signed-off-by: Shannon Zhao
Reviewed-by: Stefano Stabellini
Acked-by: Hanjun Guo
---
arch/arm64/kernel/acpi.c | 14 ++
1 file changed, 10 insertion
This new delivery type which is for ARM shares the same value with
HVM_PARAM_CALLBACK_TYPE_VECTOR which is for x86.
val[15:8] is flag: val[7:0] is a PPI.
To the flag, bit 8 stands the interrupt mode is edge(1) or level(0) and
bit 9 stands the interrupt polarity is active low(1) or high(0).
Signed
Add a "uefi" node under /hypervisor node in FDT, then Linux kernel could
scan this to get the UEFI information.
CC: Rob Herring
Signed-off-by: Shannon Zhao
Acked-by: Rob Herring
Reviewed-by: Stefano Stabellini
---
Documentation/devicetree/bindings/arm/xen.txt | 35 +++
The kernel will get the event-channel IRQ through
HVM_PARAM_CALLBACK_IRQ.
Signed-off-by: Shannon Zhao
Reviewed-by: Stefano Stabellini
---
arch/arm/xen/enlighten.c | 36 +++-
1 file changed, 35 insertions(+), 1 deletion(-)
diff --git a/arch/arm/xen/enlighten.c b/
Move xen_early_init() before efi_init(), then when calling efi_init()
could initialize Xen specific UEFI.
Check if it runs on Xen hypervisor through the flat dts.
Cc: Russell King
Signed-off-by: Shannon Zhao
Reviewed-by: Stefano Stabellini
---
arch/arm/kernel/setup.c | 2 +-
arch/arm/xen/e
Add a new function to parse DT parameters for Xen specific UEFI just
like the way for normal UEFI. Then it could reuse the existing codes.
If Xen supports EFI, initialize runtime services.
CC: Matt Fleming
Signed-off-by: Shannon Zhao
Reviewed-by: Matt Fleming
Reviewed-by: Stefano Stabellini
-
Move x86 specific codes to architecture directory and export those EFI
runtime service functions. This will be useful for initializing runtime
service on ARM later.
Signed-off-by: Shannon Zhao
Reviewed-by: Stefano Stabellini
---
arch/x86/xen/efi.c| 112
driv
Sometimes it needs to check if there is a subnode of given node in FDT
by given name. Introduce this helper to get the subnode if it exists.
CC: Rob Herring
Signed-off-by: Shannon Zhao
Acked-by: Stefano Stabellini
Acked-by: Rob Herring
---
drivers/of/fdt.c | 13 +
include/li
Move xlated_setup_gnttab_pages to common place, so it can be reused by
ARM to setup grant table.
Rename it to xen_xlate_map_ballooned_pages.
Signed-off-by: Shannon Zhao
Reviewed-by: Stefano Stabellini
---
arch/x86/xen/grant-table.c | 57 +--
drivers/xen/
Add a bus_notifier for AMBA bus device in order to map the device
mmio regions when DOM0 booting with ACPI.
Signed-off-by: Shannon Zhao
Reviewed-by: Stefano Stabellini
---
drivers/xen/arm-device.c | 43 +++
1 file changed, 43 insertions(+)
diff --git a/d
Kirill Marinushkin wrote:
> For details see
> Documentation/security/keys-derived.txt
Please include at least a summary in the patch description, not just a pointer
to the documentation file.
> + Derived Keys
> +
> +Derived is a keytype of the kernel keyring facility.
> +The
>Question about removing lustre typedefs.
>
>Various bits of lustre code use a mix of struct foo and foo_t.
>
>When would be an appropriate time to submit patches similar to
>below that individually remove various typedefs from lustre code?
>
>These are pretty trivial to produce and verify so there
On Fri, Apr 01, 2016 at 05:46:52PM +0200, Miroslav Benes wrote:
> On Fri, 1 Apr 2016, Jiri Kosina wrote:
>
> > On Tue, 29 Mar 2016, Jiri Kosina wrote:
> >
> > > Agreed; I think we should be safe applying all the alternatives (with
> > > paravirt being really just a special case of those) to the
On 04/01/2016 09:45 AM, Bin Liu wrote:
+EXPORT_SYMBOL_GPL(da8xx_usb20_phy_set_mode);
Don't prefer export symbols from PHY driver. That'll create unnecessary
dependencies between the controller and the PHY.
Agreed.
I think it'll be better to create a new attribute and use it?
Another simp
Alex Bligh writes:
> I am trying to clean up the documentation of the NBD protocol. NBD's
> support for Force Unit Access (FUA) was modelled on the linux kernel
> block layer. When I added support a few years ago, I omitted to find
> out exactly what types of request it applies to. Obviously it a
On Fri, Apr 01, 2016 at 08:49:53AM -0700, Andy Lutomirski wrote:
> Sadly, hardware turbo mode buttons are few and far between in these
> degenerate times. Add a software control at /proc/sys/turbo_mode.
>
> Unfortunately, Linux graphical environments have become very
> heavy-weight and are essent
Hi Andy,
[auto build test WARNING on tip/x86/core]
[also build test WARNING on v4.6-rc1 next-20160401]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Andy-Lutomirski/x86-Add-a-turbo-mode
On Fri, 1 Apr 2016, Andy Lutomirski wrote:
> +static void update_local_turbo_mode(void *dummy)
> +{
> + unsigned long cr0 = read_cr0();
> +
> + /*
> + * KVM doesn't properly handle CD.
> + *
> + * XXX: this may interact poorly with CPU hotplug.
Please cc these crazy folks wh
On Fri, Apr 01, 2016 at 12:45:21PM +0530, Laxman Dewangan wrote:
> On Friday 01 April 2016 02:09 AM, Mark Brown wrote:
> >Is the error in the observed values a function of the capacitance that
> >we can calcuate here?
> As per datasheet, There is no direct equation for ramp time deviation when
>
On Friday 01 April 2016 08:47:53 Casey Schaufler wrote:
> On 4/1/2016 1:47 AM, Pali Rohár wrote:
> > This patch helps NSA agents, so they will know easily which part of Linux
> > kernel code and also which config options must be enabled for their
> > "customer" kernel builds.
> >
> > Patch also pro
Hi Elaine,
Am Freitag, 1. April 2016, 10:33:45 schrieb Elaine Zhang:
> I agree with most of your modifications.
> Except, the u32 *qos_save_regs below
you're right. I didn't take that into account when my open-coding my idea.
A bit more below:
> On 04/01/2016 12:31 AM, Heiko Stuebner wrote:
> >
On Fri, Apr 01, 2016 at 08:16:37PM +0800, Xunlei Pang wrote:
> On 2016/04/01 at 19:29, Peter Zijlstra wrote:
> > On Fri, Apr 01, 2016 at 07:13:18PM +0800, Xunlei Pang wrote:
> >> Unlike rt tasks, we (should) have no deadline tasks in
> >> booting phase before the mask is allocated, so we can
> >> s
Hi,
On Fri, Apr 01, 2016 at 11:02:23AM -0500, David Lechner wrote:
> On 04/01/2016 09:45 AM, Bin Liu wrote:
> >>>+EXPORT_SYMBOL_GPL(da8xx_usb20_phy_set_mode);
> >>
> >>Don't prefer export symbols from PHY driver. That'll create unnecessary
> >>dependencies between the controller and the PHY.
> >
>
Hello,
Here is the public first version of the driver for the Mali Display Processors.
Currently, the driver supports the Display Engine found in Mali DP500, DP550
and DP650, with up to 3 planes that can be rotated by the hardware. There are
features that the hardware supports that are not current
Add support for the new family of Display Processors from ARM Ltd.
This commit adds basic support for Mali DP500, DP550 and DP650
parts, with only the display engine being supported at the moment.
Cc: David Brown
Cc: Brian Starkey
Signed-off-by: Liviu Dudau
---
drivers/gpu/drm/arm/Kconfig
Add DT bindings documentation for the Mali Display Processor. The bindings
describe the Mali DP500, DP550 and DP650 processors from ARM Ltd.
Cc: Rob Herring
Cc: Pawel Moll
Cc: Mark Rutland
Cc: Ian Campbell
Cc: Kumar Gala
Signed-off-by: Liviu Dudau
---
.../devicetree/bindings/display/arm,ma
On 03/29/2016 10:14 AM, Dominique van den Broeck wrote:
> Removing two "!= NULL" from fwserial.c as suggested by checkpatch.pl.
> Note that the associated expression "port->port.console" is a 1-bit-field
> that is already assumed as an implicit boolean (that is: without comparison)
Similarly, plea
Some versions of Intel PT do not support tracing across VMXON, more
specifically, VMXON will clear TraceEn control bit and any attempt to
set it before VMXOFF will throw a #GP, which in the current state of
things will crash the kernel. Namely,
$ perf record -e intel_pt// kvm -nographic
on such a
On 03/29/2016 10:14 AM, Dominique van den Broeck wrote:
> Coding-style-only modifications to remove every warning saying:
> WARNING: Prefer 'unsigned int' to bare use of 'unsigned'
>
> Compiled against revision "next-20160327".
>
> (checkpatch.pl was updated to treat "UNSPECIFIED_INT" warnings
>
Kirill Marinushkin wrote:
> +enum {
> + ENC,
> + DEC,
> +};
"enum big_key_mode" and use it as a parameter type to big_key_crypt().
Also BIG_KEY_ENC, BIG_KEY_DEC. Please use prefixes consistently.
> +static const char *rng_name = "stdrng";
> +
> +/*
> + * Algorithm name for big_key dat
Hello,
On (04/01/16 22:33), kbuild test robot wrote:
> Hi Jan,
>
>
> >> kernel/printk/printk.c:1938:28: warning: 'printk_kthread' defined but not
> >> used [-Wunused-variable]
> static struct task_struct *printk_kthread;
>^
yeah.
thanks. please find the upd
Hello Xunlei,
This patch can has potential to create some funny side effects.
Especially the change from memblock_remove() to memblock_reserve()
and the later call of reserve_crashkernel().
Give me some time. I will look into this next week.
Michael
On Wed, 30 Mar 2016 19:47:21 +0800
Xunlei Pan
Hi Dominique,
On 03/29/2016 10:14 AM, Dominique van den Broeck wrote:
> Fixing a lone row exceeding 80 columns so the only remaining warnings
> emitted by checkpatch.pl are missing comments on spinlocks and memory
> barriers.
>
> Signed-off-by: Dominique van den Broeck
> ---
> drivers/staging/f
When task is migrated from CPU_A to CPU_B, scheduler will decrease
the task's load/util from the task's cfs_rq and also add them into
migrated cfs_rq. But if kernel enables CONFIG_FAIR_GROUP_SCHED then this
cfs_rq is not the same one with cpu's cfs_rq. As a result, after task is
migrated to CPU_B,
On 2016-03-30 09:15, Boris Brezillon wrote:
> Implementing the mtd_ooblayout_ops interface is the new way of exposing
> ECC/OOB layout to MTD users.
I think I sent this already in the last revision:
Tested-by: Stefan Agner
Acked-by: Stefan Agner
--
Stefan
>
> Signed-off-by: Boris Brezillon
On (04/01/16 17:00), Petr Mladek wrote:
> You need to move this assigment right above the
> console_lock()/console_unlock()
> calls. Otherwise, there is a race:
>
> CPU0: CPU1
>
> printk_kthread_func()
>
> console_unlock()
>
> printk()
>
2016-04-01 17:20 GMT+02:00 Doug Smythies :
> On 2016.04.01 05:40 Rafael J. Wysocki wrote:
>> On Friday, April 01, 2016 11:20:42 AM Jörg Otte wrote:
>>> 2016-03-31 17:43 GMT+02:00 Rafael J. Wysocki :
On Thursday, March 31, 2016 05:25:18 PM Jörg Otte wrote:
> 2016-03-31 13:42 GMT+02:00 Rafae
On Fri, Apr 01, 2016 at 05:21:51PM +0100, Liviu Dudau wrote:
> Add DT bindings documentation for the Mali Display Processor. The bindings
> describe the Mali DP500, DP550 and DP650 processors from ARM Ltd.
>
> Cc: Rob Herring
> Cc: Pawel Moll
> Cc: Mark Rutland
> Cc: Ian Campbell
> Cc: Kumar G
On Fri, Apr 01, 2016 at 01:43:03PM +0200, Peter Zijlstra wrote:
> > Ah, yes, I forgot about that. Lemme go find that discussions and see
> > what I can do there.
>
> Completely untested..
>
> ---
> include/linux/compiler.h | 20 ++--
> kernel/locking/qspinlock.c | 12 ++--
On Fri, 2016-04-01 at 15:33 +0100, David Howells wrote:
> Mimi Zohar wrote:
>
> > The only place where "KEY_ALLOC_BYPASS_RESTRICTION" is specified is in
> > load_system_certificate_list(), when adding keys to
> > the .builtin_trusted_keys keyring. There is no other set of keys
> > builtin and a
Two instances are moved to the new claim/release API:
In the first instance, the driver was using mlock followed by
iio_buffer_enabled(). Replace that code with the new API to guarantee
the device stays in direct mode. There is no change in driver behavior.
In the second instance, the driver was
On Tue, Mar 29, 2016 at 09:28:23PM +0200, Paul Kocialkowski wrote:
> This adds the amazon vendor prefix for Amazon.com, Inc.
>
> Signed-off-by: Paul Kocialkowski
> ---
> Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
> 1 file changed, 1 insertion(+)
Acked-by: Rob Herring
On Wed, Mar 30, 2016 at 10:27:45AM -0500, ttha...@opensource.altera.com wrote:
> From: Thor Thayer
>
> Add the device tree bindings needed to support the Altera On-Chip
> RAM ECC on the Arria10 chip.
>
> Signed-off-by: Thor Thayer
> ---
> .../bindings/arm/altera/socfpga-eccmgr.txt |
On Wed, Mar 30, 2016 at 06:22:23PM +0200, Enric Balletbo i Serra wrote:
> The ANX7814 is an ultra-low power Full-HD (1080p60) SlimPort transmitter
> designed for portable devices.
>
> Cc: Rob Herring
> Signed-off-by: Enric Balletbo i Serra
> ---
>
> Changes since v1:
> - Rob Herring:
>- Re
On 04/01/16 03:01, Dave Chinner wrote:
> Can you go back to your original kernel, and lower nr_requests to 8?
Sure, did that and as expected it didn't help much. Under prolonged stress
it was actually even a bit worse than writeback throttling. IMHO that's not
really surprising either, since small
On Thu, Mar 31, 2016 at 10:55:27AM -0700, Mark Brown wrote:
> On Thu, Mar 31, 2016 at 03:27:58PM +0100, Jon Hunter wrote:
> > On 30/03/16 18:32, Mark Brown wrote:
>
> > > + if (bypassed) {
> > > + if (rdev->supply) {
> > > + ret =
> > > _regulator_g
On 03/31/2016 06:30 PM, Eric Anholt wrote:
This approximately triples write performance for the SD card. My card
is too full of important data to collect very reliable numbers, but I
see 271.361% +/- 166.742% improvement (n=3 before, 6 after), for 'dd
if=/dev/zero of=/boot/asdf bs=1M count=3 ofl
On 03/31/2016 08:01 PM, Stephen Warren wrote:
On 03/31/2016 06:28 PM, Eric Anholt wrote:
This approximately triples write performance for the SD card. My card
is too full of important data to collect very reliable numbers, but I
see 271.361% +/- 166.742% improvement (n=3 before, 6 after), for '
On Fri, 2016-04-01 at 15:06 +0100, David Howells wrote:
> David Howells wrote:
>
> > The three choice options I implemented don't exactly provide new features.
> > Firstly:
> >
> > config IMA_LOAD_X509
> >
> > allow keys to be loaded in at compile time,
>
> Ah - I think I'm labouring under
Hi Jose,
Thank you for the patch.
On Monday 28 Mar 2016 15:36:09 Jose Abreu wrote:
> This patch adds audio support for the ADV7511 HDMI transmitter
> using ALSA SoC.
>
> The code was ported from Analog Devices linux tree from
> commit 1770c4a1e32b ("Merge remote-tracking branch
> 'xilinx/master'
On Wed, Mar 30, 2016 at 07:35:18PM +0200, Gregory CLEMENT wrote:
> From: Marcin Wojtas
>
> Armada 3700 SoC comprise a single XOR engine compliant with the ones used
> in older Marvell SoC's like Armada XP or 38x. The only thing that neededs
s/neededs/needs/
> modification is the Mbus configurat
On Wed, Mar 30, 2016 at 05:24:44PM -0700, Simran Rai wrote:
> From: Simran Rai
>
> Add bindings for audio driver in Broadcom Cygnus.
>
> Signed-off-by: Lori Hikichi
> Signed-off-by: Simran Rai
> Reviewed-by: Ray Jui
> Reviewed-by: Scott Branden
> ---
> .../bindings/sound/brcm,cygnus-audio.t
On Thu, Mar 31, 2016 at 02:45:00PM +0800, Yuan Yao wrote:
> From: Yuan Yao
>
> new compatible string: "fsl,ls1043a-qspi".
>
> Signed-off-by: Yuan Yao
> ---
> Documentation/devicetree/bindings/mtd/fsl-quadspi.txt | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
There's a typo in the c
Hello Krzysztof,
Patch looks good to me, I have just one question below:
On 04/01/2016 02:57 AM, Krzysztof Kozlowski wrote:
> Fix following DTC warnings in all Exynos5250 boards:
>
> Warning (unit_address_vs_reg): Node
> /dp-controller@145B/display-timings/timing@0 has a unit name, but no r
Hello Krzysztof,
On 04/01/2016 02:57 AM, Krzysztof Kozlowski wrote:
> Fix following DTC warnings in all Exynos542x/5800 boards:
>
> Warning (unit_address_vs_reg): Node /video-phy@10040728 has a unit name, but
> no reg property
> Warning (unit_address_vs_reg): Node /video-phy@10040714 has a unit
Hello Krzysztof,
On 04/01/2016 02:57 AM, Krzysztof Kozlowski wrote:
> Fix following DTC warnings in Exynos5420 Peach Pit:
>
> Warning (unit_address_vs_reg): Node /dp-controller@145B/ports/port@0 has
> a unit name, but no reg property
> Warning (unit_address_vs_reg): Node /i2c@12CD/lvds-b
Hello Krzysztof,
On 04/01/2016 02:57 AM, Krzysztof Kozlowski wrote:
> Fix following DTC warnings in Exynos5420 SMDK5420:
>
> Warning (unit_address_vs_reg): Node
> /dp-controller@145B/display-timings/timing@0 has a unit name, but no reg
> property
>
> Signed-off-by: Krzysztof Kozlowski
> -
2016-04-01 18:46 GMT+02:00 Jörg Otte :
> 2016-04-01 17:20 GMT+02:00 Doug Smythies :
>> On 2016.04.01 05:40 Rafael J. Wysocki wrote:
>>> On Friday, April 01, 2016 11:20:42 AM Jörg Otte wrote:
2016-03-31 17:43 GMT+02:00 Rafael J. Wysocki :
> On Thursday, March 31, 2016 05:25:18 PM Jörg Otte
On Fri, Apr 01, 2016 at 05:02:04PM +0200, Takashi Iwai wrote:
> Currently, iov_iter_advance() just calls iterate_and_advance() macro
> as is, even if size=0 is passed. Usually it is OK to pass size=0 to
> the macro. However, when the iov_iter has been already advanced to
> the end of the array, i
Hello Xunlei again,
Some initial comments below...
On Wed, 30 Mar 2016 19:47:21 +0800
Xunlei Pang wrote:
> Commit 3f625002581b ("kexec: introduce a protection mechanism
> for the crashkernel reserved memory") is a similar mechanism
> for protecting the crash kernel reserved memory to previous
>
On Fri, 2016-04-01 at 16:06 +0200, Jörg Otte wrote:
> 2016-04-01 14:40 GMT+02:00 Rafael J. Wysocki :
> >
> > On Friday, April 01, 2016 11:20:42 AM Jörg Otte wrote:
> > >
> > > 2016-03-31 17:43 GMT+02:00 Rafael J. Wysocki :
> > > >
> > > > On Thursday, March 31, 2016 05:25:18 PM Jörg Otte wrote:
Hello Krzysztof,
On 04/01/2016 02:57 AM, Krzysztof Kozlowski wrote:
> Fix following DTC warnings in Exynos5440 boards:
>
> Warning (unit_address_vs_reg): Node /memory has a reg or ranges property, but
> no unit name
> Warning (unit_address_vs_reg): Node /pinctrl has a reg or ranges property,
>
On 03/29/2016 07:00 PM, Rafael J. Wysocki wrote:
...
> +config CPU_FREQ_GOV_SCHEDUTIL
> + tristate "'schedutil' cpufreq policy governor"
> + depends on CPU_FREQ
> + select CPU_FREQ_GOV_ATTR_SET
> + select IRQ_WORK
> + help
> + This governor makes decisions based on the uti
Hello Krzysztof,
On 04/01/2016 02:57 AM, Krzysztof Kozlowski wrote:
> Fix following DTC warnings in S5Pv210 boards:
>
> Warning (unit_address_vs_reg): Node /memory has a reg or ranges property, but
> no unit name
> Warning (unit_address_vs_reg): Node
> /soc/fimd@f800/display-timings/timing@
On 4/1/16 7:37 AM, Naveen N. Rao wrote:
On 2016/03/31 08:19PM, Daniel Borkmann wrote:
On 03/31/2016 07:46 PM, Alexei Starovoitov wrote:
On 3/31/16 4:25 AM, Naveen N. Rao wrote:
clang $(NOSTDINC_FLAGS) $(LINUXINCLUDE) $(EXTRA_CFLAGS) \
-D__KERNEL__ -D__ASM_SYSREG_H -Wno-unused-v
On 4/1/16 7:41 AM, Naveen N. Rao wrote:
On 2016/03/31 10:52AM, Alexei Starovoitov wrote:
On 3/31/16 4:25 AM, Naveen N. Rao wrote:
...
+
+#ifdef __powerpc__
+#define BPF_KPROBE_READ_RET_IP(ip, ctx){ (ip) = (ctx)->link; }
+#define BPF_KRETPROBE_READ_RET_IP(ip, ctx) BPF_KPROBE_
On 04/01/2016 05:10 PM, Peter Zijlstra wrote:
On Fri, Apr 01, 2016 at 03:46:48PM +0200, Daniel Lezcano wrote:
Remove the duplicate test by directly calling sched_clock_cpu() and let the
static key act in this function instead. We can assume gcc is smart enough to
inline cpu_clock()/local_clock(
Hi Daniel,
[auto build test WARNING on iio/togreg]
[also build test WARNING on v4.6-rc1 next-20160401]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Daniel-Baluta/iio-imu-Add-initial-support
On 4/1/16 2:58 AM, Naveen N. Rao wrote:
PPC64 eBPF JIT compiler. Works for both ABIv1 and ABIv2.
Enable with:
echo 1 > /proc/sys/net/core/bpf_jit_enable
or
echo 2 > /proc/sys/net/core/bpf_jit_enable
... to see the generated JIT code. This can further be processed with
tools/net/bpf_jit_disasm.
On Sun, Mar 27, 2016 at 09:14:00PM -0400, Dave Jones wrote:
> > WARNING: CPU: 2 PID: 32570 at fs/btrfs/inode.c:9261
> btrfs_destroy_inode+0x389/0x3f0 [btrfs]
> > CPU: 2 PID: 32570 Comm: rm Not tainted 4.5.0-think+ #14
> > c039baf9 ef721ef0 88025966fc08 8957bcd
On 03/31/2016 05:32 AM, Rafael J. Wysocki wrote:
> On Thu, Mar 31, 2016 at 2:24 PM, Peter Zijlstra wrote:
>> On Mon, Mar 28, 2016 at 11:17:44AM -0700, Steve Muckle wrote:
>>> The scenario I'm contemplating is that while a CPU-intensive task is
>>> running a thermal interrupt goes off. The driver f
401 - 500 of 890 matches
Mail list logo
