From: Vincent Guittot
rt_avg monitors the average load of rt tasks, deadline tasks and
interruptions, when enabled. It's used to calculate the remaining
capacity for CFS tasks. We split rt_avg in 2 metrics, one for rt and
interruptions that keeps the name rt_avg and another one for deadline
From: Vincent Guittot
RT tasks don't provide any running constraints like deadline ones
except their running priority. The only current usable input to
estimate the capacity needed by RT tasks is the rt_avg metric. We use
it to estimate the CPU capacity needed for the RT scheduler class.
In
From: Juri Lelli
As we don't trigger freq changes from {en,de}queue_task_fair() during load
balancing, we need to do explicitly so on load balancing paths.
[smuc...@linaro.org: move update_capacity_of calls so rq lock is held]
cc: Ingo Molnar
cc: Peter Zijlstra
Signed-off-by: Juri Lelli
From: Juri Lelli
Each time a task is {en,de}queued we might need to adapt the current
frequency to the new usage. Add triggers on {en,de}queue_task_fair() for
this purpose. Only trigger a freq request if we are effectively waking up
or going to sleep. Filter out load balancing related calls to
From: Vincent Guittot
rt_avg is only used to scale the available CPU's capacity for CFS
tasks. As the update of this scaling is done during periodic load
balance, we only have to ensure that sched_avg_update has been called
before any periodic load balancing. This
Since the true utilization of a long running task is not detectable
while it is running and might be bigger than the current cpu capacity,
create the maximum cpu capacity head room by requesting the maximum
cpu capacity once the cpu usage plus the capacity margin exceeds the
current capacity. This
Since the true utilization of a long running task is not detectable
while it is running and might be bigger than the current cpu capacity,
create the maximum cpu capacity head room by requesting the maximum
cpu capacity once the cpu usage plus the capacity margin exceeds the
current capacity. This
From: Vincent Guittot
rt_avg is only used to scale the available CPU's capacity for CFS
tasks. As the update of this scaling is done during periodic load
balance, we only have to ensure that sched_avg_update has been called
before any periodic load balancing. This requirement is already
This patch add smi binding document and smi local arbiter header file.
Signed-off-by: Yong Wu
Acked-by: Rob Herring
---
.../memory-controllers/mediatek,smi-common.txt | 24 +
.../memory-controllers/mediatek,smi-larb.txt | 25 +
Scheduler-driven CPU frequency selection hopes to exploit both
per-task and global information in the scheduler to improve frequency
selection policy and achieve lower power consumption, improved
responsiveness/performance, and less reliance on heuristics and
tunables. For further discussion of
This patch add smi binding document and smi local arbiter header file.
Signed-off-by: Yong Wu
Acked-by: Rob Herring
---
.../memory-controllers/mediatek,smi-common.txt | 24 +
.../memory-controllers/mediatek,smi-larb.txt | 25 +
include/dt-bindings/memory/mt8173-larb-port.h
Scheduler-driven CPU frequency selection hopes to exploit both
per-task and global information in the scheduler to improve frequency
selection policy and achieve lower power consumption, improved
responsiveness/performance, and less reliance on heuristics and
tunables. For further discussion of
From: Michael Turquette
Some architectures and platforms perform CPU frequency transitions
through a non-blocking method, while some might block or sleep. Even
when frequency transitions do not block or sleep they may be very slow.
This distinction is important when
From: Michael Turquette
Some architectures and platforms perform CPU frequency transitions
through a non-blocking method, while some might block or sleep. Even
when frequency transitions do not block or sleep they may be very slow.
This distinction is important when trying to change frequency
This patch adds support for mediatek m4u (MultiMedia Memory Management
Unit).
Signed-off-by: Yong Wu
Reviewed-by: Robin Murphy
---
drivers/iommu/Kconfig | 16 +
drivers/iommu/Makefile| 1 +
drivers/iommu/mtk_iommu.c | 737
This patch add the iommu/larbs nodes for mt8173
Signed-off-by: Yong Wu
Reviewed-by: Daniel Kurtz
---
arch/arm64/boot/dts/mediatek/mt8173.dtsi | 81
1 file changed, 81 insertions(+)
diff --git
This patch add SMI(Smart Multimedia Interface) driver. This driver
is responsible to enable/disable iommu and control the power domain
and clocks of each local arbiter.
Signed-off-by: Yong Wu
Tested-by: Philipp Zabel
Reviewed-by: Daniel Kurtz
This patch adds support for mediatek m4u (MultiMedia Memory Management
Unit).
Signed-off-by: Yong Wu
Reviewed-by: Robin Murphy
---
drivers/iommu/Kconfig | 16 +
drivers/iommu/Makefile| 1 +
drivers/iommu/mtk_iommu.c | 737 ++
3 files
This patch add the iommu/larbs nodes for mt8173
Signed-off-by: Yong Wu
Reviewed-by: Daniel Kurtz
---
arch/arm64/boot/dts/mediatek/mt8173.dtsi | 81
1 file changed, 81 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
This patch add SMI(Smart Multimedia Interface) driver. This driver
is responsible to enable/disable iommu and control the power domain
and clocks of each local arbiter.
Signed-off-by: Yong Wu
Tested-by: Philipp Zabel
Reviewed-by: Daniel Kurtz
Tested-by: Daniel Kurtz
Signed-off-by: Matthias
This patch add mediatek iommu dts binding document.
Signed-off-by: Yong Wu
Acked-by: Rob Herring
---
.../devicetree/bindings/iommu/mediatek,iommu.txt | 68 ++
1 file changed, 68 insertions(+)
create mode 100644
This patch add mediatek iommu dts binding document.
Signed-off-by: Yong Wu
Acked-by: Rob Herring
---
.../devicetree/bindings/iommu/mediatek,iommu.txt | 68 ++
1 file changed, 68 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iommu/mediatek,iommu.txt
This patch set adds support for m4u(Multimedia Memory Management Unit),
Currently it only support the m4u with 2 levels of pagetable on mt8173.
It's based on Robin Murphy's Short-descriptor v3[1].
Please check the hardware block diagram of Mediatek IOMMU.
m4u (Multimedia
This patch set adds support for m4u(Multimedia Memory Management Unit),
Currently it only support the m4u with 2 levels of pagetable on mt8173.
It's based on Robin Murphy's Short-descriptor v3[1].
Please check the hardware block diagram of Mediatek IOMMU.
m4u (Multimedia
The event_data passed from pem_fini was not cleared upon initialization.
This caused NULL checks to pass and cast_const_phw_tonga_power_state to
attempt to dereference an invalid pointer. Clear the event_data in
pem_init and pem_fini before calling pem_handle_event.
Signed-off-by: Bradley Pankow
The event_data passed from pem_fini was not cleared upon initialization.
This caused NULL checks to pass and cast_const_phw_tonga_power_state to
attempt to dereference an invalid pointer. Clear the event_data in
pem_init and pem_fini before calling pem_handle_event.
Signed-off-by: Bradley Pankow
From: Dave Hansen
Today, mprotect() takes 4 bits of data: PROT_READ/WRITE/EXEC/NONE.
Three of those bits: READ/WRITE/EXEC get translated directly in to
vma->vm_flags by calc_vm_prot_bits(). If a bit is unset in
mprotect()'s 'prot' argument then it must be cleared
From: Dave Hansen
This is all that we need to get the new system call itself
working on x86.
Signed-off-by: Dave Hansen
Cc: linux-...@vger.kernel.org
Cc: linux...@kvack.org
Cc: x...@kernel.org
Cc: torva...@linux-foundation.org
Cc:
From: Dave Hansen
This is all that we need to get the new system call itself
working on x86.
Signed-off-by: Dave Hansen
Cc: linux-...@vger.kernel.org
Cc: linux...@kvack.org
Cc: x...@kernel.org
Cc: torva...@linux-foundation.org
Cc: a...@linux-foundation.org
---
From: Dave Hansen
Today, mprotect() takes 4 bits of data: PROT_READ/WRITE/EXEC/NONE.
Three of those bits: READ/WRITE/EXEC get translated directly in to
vma->vm_flags by calc_vm_prot_bits(). If a bit is unset in
mprotect()'s 'prot' argument then it must be cleared in vma->vm_flags
during the
From: Dave Hansen
This establishes two more system calls for protection key management:
unsigned long pkey_get(int pkey);
int pkey_set(int pkey, unsigned long access_rights);
The return value from pkey_get() and the 'access_rights' passed
to
From: Dave Hansen
This establishes two more system calls for protection key management:
unsigned long pkey_get(int pkey);
int pkey_set(int pkey, unsigned long access_rights);
The return value from pkey_get() and the 'access_rights' passed
to pkey_set() are the same format: a
From: Dave Hansen
Give a high-level overview of Protection Keys from a hardware
perspective, as well as some description since we referred to
this from the Kconfig text.
Signed-off-by: Dave Hansen
---
From: Dave Hansen
This spells out all of the pkey-related system calls that we have
and provides some example code fragments to demonstrate how we
expect them to be used.
Signed-off-by: Dave Hansen
Cc: linux-...@vger.kernel.org
Cc:
From: Dave Hansen
Give a high-level overview of Protection Keys from a hardware
perspective, as well as some description since we referred to
this from the Kconfig text.
Signed-off-by: Dave Hansen
---
b/Documentation/x86/protection-keys.txt | 28
1 file
From: Dave Hansen
This spells out all of the pkey-related system calls that we have
and provides some example code fragments to demonstrate how we
expect them to be used.
Signed-off-by: Dave Hansen
Cc: linux-...@vger.kernel.org
Cc: linux...@kvack.org
Cc: x...@kernel.org
Cc:
From: Dave Hansen
This patch adds two new system calls:
int pkey_alloc(unsigned long flags, unsigned long init_access_rights)
int pkey_free(int pkey);
These implement an "allocator" for the protection keys
themselves, which can be thought of as
From: Dave Hansen
This patch adds two new system calls:
int pkey_alloc(unsigned long flags, unsigned long init_access_rights)
int pkey_free(int pkey);
These implement an "allocator" for the protection keys
themselves, which can be thought of as analogous to the allocator
that
As promised, here are the proposed new Memory Protection Keys
interfaces. These interfaces make it possible to do something
with pkeys other than execute-only support.
There are 5 syscalls here. I'm hoping for reviews of this set
which can help nail down what the final interfaces will be.
You
As promised, here are the proposed new Memory Protection Keys
interfaces. These interfaces make it possible to do something
with pkeys other than execute-only support.
There are 5 syscalls here. I'm hoping for reviews of this set
which can help nail down what the final interfaces will be.
You
From: Dave Hansen
pkey_mprotect() is just like mprotect, except it also takes a
protection key as an argument. On systems that do not support
protection keys, it still works, but requires that key=0.
Otherwise it does exactly what mprotect does.
I expect it to get
From: Dave Hansen
pkey_mprotect() is just like mprotect, except it also takes a
protection key as an argument. On systems that do not support
protection keys, it still works, but requires that key=0.
Otherwise it does exactly what mprotect does.
I expect it to get used like this, if you want
On Tue, Feb 23, 2016 at 08:55:04AM +0800, Geliang Tang wrote:
> On Sun, Feb 07, 2016 at 07:55:09PM -0800, Greg Kroah-Hartman wrote:
> > On Sun, Nov 08, 2015 at 10:17:54PM +0800, Geliang Tang wrote:
> > > Use kmalloc_array instead of kmalloc to allocate memory for an array.
> > >
> > >
On Tue, Feb 23, 2016 at 08:55:04AM +0800, Geliang Tang wrote:
> On Sun, Feb 07, 2016 at 07:55:09PM -0800, Greg Kroah-Hartman wrote:
> > On Sun, Nov 08, 2015 at 10:17:54PM +0800, Geliang Tang wrote:
> > > Use kmalloc_array instead of kmalloc to allocate memory for an array.
> > >
> > >
On Thu, 18 Feb 2016, Michal Hocko wrote:
> > Anyway, this is NACK'd since task->signal->oom_score_adj is checked under
> > task_lock() for threads with memory attached, that's the purpose of
> > finding the correct thread in oom_badness() and taking task_lock(). We
> > aren't going to
On Thu, 18 Feb 2016, Michal Hocko wrote:
> > Anyway, this is NACK'd since task->signal->oom_score_adj is checked under
> > task_lock() for threads with memory attached, that's the purpose of
> > finding the correct thread in oom_badness() and taking task_lock(). We
> > aren't going to
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs dev-test
commit 7b51bf49f4825da09206c6d89e4aad5b4faa0a14 ("f2fs: set flush_merge by
default")
=
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs dev-test
commit 7b51bf49f4825da09206c6d89e4aad5b4faa0a14 ("f2fs: set flush_merge by
default")
=
在 2/22/2016 19:04, Mark Brown 写道:
On Mon, Feb 22, 2016 at 03:56:53PM +0800, Sugar Zhang wrote:
Sugar Zhang (2):
ASoC: rockchip: i2s: add default values for registers
ASoC: rt5640: add master clock handling for rt5640
These appear to be commpletly unrelated patches so should each be
在 2/22/2016 19:04, Mark Brown 写道:
On Mon, Feb 22, 2016 at 03:56:53PM +0800, Sugar Zhang wrote:
Sugar Zhang (2):
ASoC: rockchip: i2s: add default values for registers
ASoC: rt5640: add master clock handling for rt5640
These appear to be commpletly unrelated patches so should each be
Hi all,
I've hit the following warning while fuzzing with trinity inside a kvmtool guest
running the latest -next kernel:
[ 3196.268106] WARNING: CPU: 3 PID: 660 at
net/ipv4/netfilter/nf_nat_l3proto_ipv4.c:275 nf_nat_ipv4_fn+0x65d/0xab0()
[ 3196.268120] Modules linked in:
[ 3196.268142] CPU:
Hi all,
I've hit the following warning while fuzzing with trinity inside a kvmtool guest
running the latest -next kernel:
[ 3196.268106] WARNING: CPU: 3 PID: 660 at
net/ipv4/netfilter/nf_nat_l3proto_ipv4.c:275 nf_nat_ipv4_fn+0x65d/0xab0()
[ 3196.268120] Modules linked in:
[ 3196.268142] CPU:
On Sun, Feb 07, 2016 at 07:55:09PM -0800, Greg Kroah-Hartman wrote:
> On Sun, Nov 08, 2015 at 10:17:54PM +0800, Geliang Tang wrote:
> > Use kmalloc_array instead of kmalloc to allocate memory for an array.
> >
> > Signed-off-by: Geliang Tang
> > ---
> >
On Sun, Feb 07, 2016 at 07:55:09PM -0800, Greg Kroah-Hartman wrote:
> On Sun, Nov 08, 2015 at 10:17:54PM +0800, Geliang Tang wrote:
> > Use kmalloc_array instead of kmalloc to allocate memory for an array.
> >
> > Signed-off-by: Geliang Tang
> > ---
> > drivers/staging/rtl8192u/r8192U_core.c |
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
commit 34578dc67f38c02ccbe696e4099967884caa8e15 ("printk: set may_schedule for
some of console_trylock() callers")
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
commit 34578dc67f38c02ccbe696e4099967884caa8e15 ("printk: set may_schedule for
some of console_trylock() callers")
On Thu, 18 Feb 2016, Xishi Qiu wrote:
> Does somebody do the work of re-implementation of the lowmem killer entirely
> now? Could you give me some details? e.g. when and how?
>
I don't know of any plans or anybody working on reimplementing it to be
correct, I simply don't think we should pile
On Thu, 18 Feb 2016, Xishi Qiu wrote:
> Does somebody do the work of re-implementation of the lowmem killer entirely
> now? Could you give me some details? e.g. when and how?
>
I don't know of any plans or anybody working on reimplementing it to be
correct, I simply don't think we should pile
On Mon, Feb 22, 2016 at 01:34:05AM +, 平松雅巳 / HIRAMATU,MASAMI wrote:
> >From: Luis R. Rodriguez [mailto:mcg...@kernel.org]
> >
> >kprobe makes use of two custom sections:
> >
> >type name beginend
> >init.data _kprobe_blacklist __start_kprobe_blacklist
On Mon, Feb 22, 2016 at 01:34:05AM +, 平松雅巳 / HIRAMATU,MASAMI wrote:
> >From: Luis R. Rodriguez [mailto:mcg...@kernel.org]
> >
> >kprobe makes use of two custom sections:
> >
> >type name beginend
> >init.data _kprobe_blacklist __start_kprobe_blacklist
On Thu, 18 Feb 2016, Xishi Qiu wrote:
> How about kill more processes at one time?
>
> Usually loading camera will alloc 300-500M memory immediately, so call lmk
> repeatedly is a waste of time.
>
> And can we reclaim memory at one time instead of
> reclaim-alloc-reclaim-alloc...
> in this
On Thu, 18 Feb 2016, Xishi Qiu wrote:
> How about kill more processes at one time?
>
> Usually loading camera will alloc 300-500M memory immediately, so call lmk
> repeatedly is a waste of time.
>
> And can we reclaim memory at one time instead of
> reclaim-alloc-reclaim-alloc...
> in this
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git features
commit 420ce36f0515c0fe8b5fda9420bb64cfbea75841 ("crypto/xor: skip speed test
if the xor function is selected automatically")
[4.830567] done.
[
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git features
commit 420ce36f0515c0fe8b5fda9420bb64cfbea75841 ("crypto/xor: skip speed test
if the xor function is selected automatically")
[4.830567] done.
[
Kishon,
On 02/22/2016 07:15 PM, Kishon Vijay Abraham I wrote:
Hi,
On Monday 15 February 2016 04:31 PM, Yakir Yang wrote:
Hi Kison,
This series is splited from Analogix DP DRM thread [0], and Heiko suggest this
should be an independent thread which may be easy for you to apply.
Indeed.
Kishon,
On 02/22/2016 07:15 PM, Kishon Vijay Abraham I wrote:
Hi,
On Monday 15 February 2016 04:31 PM, Yakir Yang wrote:
Hi Kison,
This series is splited from Analogix DP DRM thread [0], and Heiko suggest this
should be an independent thread which may be easy for you to apply.
Indeed.
On Sun, 21 Feb 2016, Tetsuo Handa wrote:
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index ae8b81c..390ec2c 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -1253,16 +1253,6 @@ static void mem_cgroup_out_of_memory(struct mem_cgroup
> *memcg, gfp_t gfp_mask,
>
>
On Sun, 21 Feb 2016, Tetsuo Handa wrote:
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index ae8b81c..390ec2c 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -1253,16 +1253,6 @@ static void mem_cgroup_out_of_memory(struct mem_cgroup
> *memcg, gfp_t gfp_mask,
>
>
Use list_first_entry*() instead of container_of() to simplify the code.
Signed-off-by: Geliang Tang
---
drivers/staging/rtl8723au/core/rtw_recv.c | 49 +--
drivers/staging/rtl8723au/core/rtw_xmit.c | 26 +---
2 files changed, 22
Use list_first_entry*() instead of container_of() to simplify the code.
Signed-off-by: Geliang Tang
---
drivers/staging/rtl8723au/core/rtw_recv.c | 49 +--
drivers/staging/rtl8723au/core/rtw_xmit.c | 26 +---
2 files changed, 22 insertions(+), 53
On Mon, Feb 22, 2016 at 4:20 PM, Pavel Machek wrote:
> On Mon 2016-02-22 15:59:48, Diego Viola wrote:
>> On Mon, Feb 22, 2016 at 7:09 AM, Pavel Machek wrote:
>> > Hi!
>> >
>> >> Every time I initiate a suspend (systemctl suspend) the machine hangs
>> >> at
On Mon, Feb 22, 2016 at 4:20 PM, Pavel Machek wrote:
> On Mon 2016-02-22 15:59:48, Diego Viola wrote:
>> On Mon, Feb 22, 2016 at 7:09 AM, Pavel Machek wrote:
>> > Hi!
>> >
>> >> Every time I initiate a suspend (systemctl suspend) the machine hangs
>> >> at resume unless I unload the
On Tue, 2016-02-23 at 00:38 +0100, Philippe Loctaux wrote:
> Added spaces around | and *, fixing 2 checkpatch checks.
[]
> diff --git a/drivers/staging/comedi/drivers/mite.c
> b/drivers/staging/comedi/drivers/mite.c
[]
> @@ -51,7 +51,7 @@
>
> #include "mite.h"
>
> -#define TOP_OF_PAGE(x)
On Tue, 2016-02-23 at 00:38 +0100, Philippe Loctaux wrote:
> Added spaces around | and *, fixing 2 checkpatch checks.
[]
> diff --git a/drivers/staging/comedi/drivers/mite.c
> b/drivers/staging/comedi/drivers/mite.c
[]
> @@ -51,7 +51,7 @@
>
> #include "mite.h"
>
> -#define TOP_OF_PAGE(x)
On 21.02.2016 22:30, Joe Perches wrote:
On Sun, 2016-02-21 at 22:38 +0100, Andrej Krpic wrote:
Minor formatting changes to remove errors and reduce number of
warnings produced by checkpatch.pl script.
[]
diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c
[]
@@ -489,7 +490,8 @@ static
On 21.02.2016 22:30, Joe Perches wrote:
On Sun, 2016-02-21 at 22:38 +0100, Andrej Krpic wrote:
Minor formatting changes to remove errors and reduce number of
warnings produced by checkpatch.pl script.
[]
diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c
[]
@@ -489,7 +490,8 @@ static
Signed-off-by: Diego Viola
---
drivers/net/ethernet/jme.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/jme.c b/drivers/net/ethernet/jme.c
index b1de7af..8adbe8f 100644
--- a/drivers/net/ethernet/jme.c
+++
Signed-off-by: Diego Viola
---
drivers/net/ethernet/jme.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/jme.c b/drivers/net/ethernet/jme.c
index b1de7af..8adbe8f 100644
--- a/drivers/net/ethernet/jme.c
+++ b/drivers/net/ethernet/jme.c
@@ -3312,13
Eddie Huang writes:
> MT8173 E1 chip has one bug that if turn off USB power domain, vcore
> power will also be off, thus cause modules using vcore power domain
> fail, like MMC. The E1 chip only found on MT8173-evb board and this
> board only has E1 chip, so implement
Eddie Huang writes:
> MT8173 E1 chip has one bug that if turn off USB power domain, vcore
> power will also be off, thus cause modules using vcore power domain
> fail, like MMC. The E1 chip only found on MT8173-evb board and this
> board only has E1 chip, so implement this as a board specific
>
On 21.02.2016 23:42, One Thousand Gnomes wrote:
On Sun, 21 Feb 2016 22:38:29 +0100
Andrej Krpic wrote:
When using n_gsm you have to explicitly set it to work as a
initiator
station. This led me to believe that it can also work as a
responder.
snip
This looks reasonable to
On 21.02.2016 23:42, One Thousand Gnomes wrote:
On Sun, 21 Feb 2016 22:38:29 +0100
Andrej Krpic wrote:
When using n_gsm you have to explicitly set it to work as a
initiator
station. This led me to believe that it can also work as a
responder.
snip
This looks reasonable to me. It was never
Hi Stephen,
On Tue, Feb 23, 2016 at 10:09:51AM +1100, Stephen Rothwell wrote:
> Hi Jaegeuk,
>
> Today's linux-next merge of the f2fs tree got conflicts in:
>
> fs/ext4/crypto.c
> fs/ext4/ext4.h
> fs/ext4/namei.c
>
> between commits:
>
> 28b4c263961c ("ext4 crypto: revalidate dentry
Hi Stephen,
On Tue, Feb 23, 2016 at 10:09:51AM +1100, Stephen Rothwell wrote:
> Hi Jaegeuk,
>
> Today's linux-next merge of the f2fs tree got conflicts in:
>
> fs/ext4/crypto.c
> fs/ext4/ext4.h
> fs/ext4/namei.c
>
> between commits:
>
> 28b4c263961c ("ext4 crypto: revalidate dentry
Hi,
> From: Aleksey Makarov [mailto:aleksey.maka...@linaro.org]
> Subject: Re: [PATCH v3 1/5] ACPI: change __init to __ref for
> early_acpi_os_unmap_memory()
>
> Hi,
>
> On 02/22/2016 05:24 AM, Zheng, Lv wrote:
> > Hi,
> >
> >> From: Aleksey Makarov [mailto:aleksey.maka...@linaro.org]
> >>
Hi,
> From: Aleksey Makarov [mailto:aleksey.maka...@linaro.org]
> Subject: Re: [PATCH v3 1/5] ACPI: change __init to __ref for
> early_acpi_os_unmap_memory()
>
> Hi,
>
> On 02/22/2016 05:24 AM, Zheng, Lv wrote:
> > Hi,
> >
> >> From: Aleksey Makarov [mailto:aleksey.maka...@linaro.org]
> >>
On 17.02.2016 11:23, Javier Martinez Canillas wrote:
> Hello Krzysztof,
>
> On 02/16/2016 11:13 PM, Krzysztof Kozlowski wrote:
>
> [snip]
>
>>> diff --git a/arch/arm/boot/dts/exynos-syscon-restart.dtsi
>>> b/arch/arm/boot/dts/exynos-syscon-restart.dtsi
>>> new file mode 100644
>>> index
On 17.02.2016 11:23, Javier Martinez Canillas wrote:
> Hello Krzysztof,
>
> On 02/16/2016 11:13 PM, Krzysztof Kozlowski wrote:
>
> [snip]
>
>>> diff --git a/arch/arm/boot/dts/exynos-syscon-restart.dtsi
>>> b/arch/arm/boot/dts/exynos-syscon-restart.dtsi
>>> new file mode 100644
>>> index
On 23.02.2016 03:26, Michael Turquette wrote:
> Quoting Sylwester Nawrocki (2016-02-17 02:03:36)
>> On 16/02/16 07:20, Krzysztof Kozlowski wrote:
>>> Currently the Exynos5433 (ARMv8 SoC) clock driver depends on ARCH_EXYNOS
>>> so it is built also on ARMv7. This does not bring any kind of benefit.
On 23.02.2016 03:26, Michael Turquette wrote:
> Quoting Sylwester Nawrocki (2016-02-17 02:03:36)
>> On 16/02/16 07:20, Krzysztof Kozlowski wrote:
>>> Currently the Exynos5433 (ARMv8 SoC) clock driver depends on ARCH_EXYNOS
>>> so it is built also on ARMv7. This does not bring any kind of benefit.
On Mon, Feb 22, 2016 at 12:16:26PM -0800, Linus Torvalds wrote:
> Hi Guenter,
>
> Please don't do things like this to me:
>
> On Sun, Feb 21, 2016 at 10:22 AM, Guenter Roeck wrote:
> >
> > Please pull hwmon fixes for Linux v4.5-rc6 from signed tag:
> >
> >
On Mon, Feb 22, 2016 at 12:16:26PM -0800, Linus Torvalds wrote:
> Hi Guenter,
>
> Please don't do things like this to me:
>
> On Sun, Feb 21, 2016 at 10:22 AM, Guenter Roeck wrote:
> >
> > Please pull hwmon fixes for Linux v4.5-rc6 from signed tag:
> >
> >
On Mon, 2016-02-22 at 22:29 +, David Howells wrote:
> Mimi Zohar wrote:
>
> > > (1) - (3) These are Tadeusz's RSA akcipher conversion.
> >
> > Up to here, IMA-appraisal works properly.
>
> I don't have IMA set up anywhere.
I know. With the "vfs: support for a
On 22/02/16 10:09, Paul Burton wrote:
> Index-based cache operations may be arbitrarily reordered by out of
> order CPUs. Thus code which writes back the dcache & then invalidates
> the icache using indexed cache ops must include a barrier between
> operating on the 2 caches in order to prevent
On 22/02/16 10:09, Paul Burton wrote:
> Index-based cache operations may be arbitrarily reordered by out of
> order CPUs. Thus code which writes back the dcache & then invalidates
> the icache using indexed cache ops must include a barrier between
> operating on the 2 caches in order to prevent
On Mon, 2016-02-22 at 22:29 +, David Howells wrote:
> Mimi Zohar wrote:
>
> > > (1) - (3) These are Tadeusz's RSA akcipher conversion.
> >
> > Up to here, IMA-appraisal works properly.
>
> I don't have IMA set up anywhere.
I know. With the "vfs: support for a common kernel file loader"
Am Sonntag, 21. Februar 2016, 10:45:11 schrieb Caesar Wang:
> Heiko,
>
> 在 2016年02月21日 10:26, Heiko Stuebner 写道:
> > Hi Caesar, Xing,
> >
> > Am Dienstag, 2. Februar 2016, 11:48:19 schrieb Caesar Wang:
> >> From: zhengxing
> >>
> >> In the emac driver, we need to
Am Sonntag, 21. Februar 2016, 10:45:11 schrieb Caesar Wang:
> Heiko,
>
> 在 2016年02月21日 10:26, Heiko Stuebner 写道:
> > Hi Caesar, Xing,
> >
> > Am Dienstag, 2. Februar 2016, 11:48:19 schrieb Caesar Wang:
> >> From: zhengxing
> >>
> >> In the emac driver, we need to refer HCLK_MAC since there are
Hi,
On 22 February 2016 at 23:28, David Howells wrote:
> Tadeusz Struk wrote:
>
>> I wonder if this should be merged with the crypto/rsa-pkcs1pad.c template
>> that we already have. Looks like the two do the same padding now.
I think that'd be a
Hi,
On 22 February 2016 at 23:28, David Howells wrote:
> Tadeusz Struk wrote:
>
>> I wonder if this should be merged with the crypto/rsa-pkcs1pad.c template
>> that we already have. Looks like the two do the same padding now.
I think that'd be a good thing to do.
>> Should we merge then and
501 - 600 of 2460 matches
Mail list logo