> -Original Message-
> From: linux-fsdevel-ow...@vger.kernel.org
> [mailto:linux-fsdevel-ow...@vger.kernel.org] On Behalf Of Waiman Long
> Sent: Wednesday, August 16, 2017 1:15 AM
> To: Alexander Viro; Jonathan Corbet
> Cc: linux-ker...@vger.kernel.org; linux-doc@vger.kernel.org;
> linux-fs
On 08/16/2017 06:33 AM, Wangkai (Kevin,C) wrote:
>> -Original Message-
>> From: linux-fsdevel-ow...@vger.kernel.org
>> [mailto:linux-fsdevel-ow...@vger.kernel.org] On Behalf Of Waiman Long
>> Sent: Wednesday, August 16, 2017 1:15 AM
>> To: Alexander Viro; Jonathan Corbet
>> Cc: linux-ker...
Hello, Waiman.
On Tue, Aug 15, 2017 at 01:27:20PM -0400, Waiman Long wrote:
> + cpuset_v2_mode= [KNL] Enable cpuset v2 behavior in cpuset v1 cgroups.
> + In v2 mode, the cpus and mems can be restored to
> + their original values after a removal-addition
On 08/16/2017 10:29 AM, Tejun Heo wrote:
> Hello, Waiman.
>
> On Tue, Aug 15, 2017 at 01:27:20PM -0400, Waiman Long wrote:
>> +cpuset_v2_mode= [KNL] Enable cpuset v2 behavior in cpuset v1 cgroups.
>> +In v2 mode, the cpus and mems can be restored to
>> +t
Hello,
On Wed, Aug 16, 2017 at 10:34:05AM -0400, Waiman Long wrote:
> > It feels weird to make this a kernel boot param when all other options
> > are specified on mount time. Is there a reason why this can't be a
> > mount option too?
> >
> Yes, we can certainly make this a mount option instead
On 08/16/2017 10:36 AM, Tejun Heo wrote:
> Hello,
>
> On Wed, Aug 16, 2017 at 10:34:05AM -0400, Waiman Long wrote:
>>> It feels weird to make this a kernel boot param when all other options
>>> are specified on mount time. Is there a reason why this can't be a
>>> mount option too?
>>>
>> Yes, we
This is a minor patch that fixes the following typo in the NVMEM documentation:
When a consumers no longer needs the NVMEM
to,
When a consumer no longer needs the NVMEM
Signed-off-by: Naren
---
Documentation/nvmem/nvmem.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/D
On Tue, Aug 15, 2017 at 01:56:24PM -0700, David Rientjes wrote:
> On Tue, 15 Aug 2017, Roman Gushchin wrote:
>
> > > > diff --git a/Documentation/cgroup-v2.txt b/Documentation/cgroup-v2.txt
> > > > index dec5afdaa36d..22108f31e09d 100644
> > > > --- a/Documentation/cgroup-v2.txt
> > > > +++ b/Docu
On Mon, 14 Aug 2017, Bartosz Golaszewski wrote:
> Some frameworks (e.g. iio, gpiolib) use irq_work to implement simulated
> interrupts that can be 'fired' from process context when needed and
> requested just like normal interrupts. This is useful for testing and
> development purposes.
>
> Curre
On 08/15/2017 10:58 PM, David Miller wrote:
From: Khalid Aziz
Date: Wed, 9 Aug 2017 15:26:02 -0600
+void adi_restore_tags(struct mm_struct *mm, struct vm_area_struct *vma,
+ unsigned long addr, pte_t pte)
+{
...
+ tag = tag_start(addr, tag_desc);
+ paddr =
printk.time=1/CONFIG_PRINTK_TIME=1 adds a unmodified local hardware clock
timestamp to printk messages. The local hardware clock loses time each
day making it difficult to determine exactly when an issue has occurred in
the kernel log, and making it difficult to determine how kernel and
hardware i
printk.time=1/CONFIG_PRINTK_TIME=1 adds a unmodified local hardware clock
timestamp to printk messages. The local hardware clock loses time each
day making it difficult to determine exactly when an issue has occurred in
the kernel log, and making it difficult to determine how kernel and
hardware i
On 08/16/2017 08:17 AM, Prarit Bhargava wrote:
. . .
diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
index fc47863f629c..f627a9bb97d1 100644
--- a/kernel/printk/printk.c
+++ b/kernel/printk/printk.c
@@ -576,6 +576,9 @@ static u32 truncate_msg(u16 *text_len, u16 *trunc_msg_len,
On Tue, Aug 15, 2017 at 02:47:10PM -0700, David Rientjes wrote:
> On Tue, 15 Aug 2017, Roman Gushchin wrote:
>
> > > I'm curious about the decision made in this conditional and how
> > > oom_kill_memcg_member() ignores task->signal->oom_score_adj. It means
> > > that memory.oom_kill_all_tasks o
On Tue, Aug 1, 2017 at 5:01 PM, Wolfram Sang wrote:
>> I'm perfectly fine with the I3C / I2C framework separation. The only
>> minor problem I had with that was the inaccuracy of the
>> sysfs/device-model representation: we don't have one i2c and one i3c
>> bus, we just have one i3c bus with a mix
This is a minor patch that fixes the following typo in the NVMEM documentation:
When a consumers no longer needs the NVMEM
to,
When a consumer no longer needs the NVMEM
Signed-off-by: Narendran Sankaran
---
Documentation/nvmem/nvmem.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
d
Hi Mark,
Thanks for your comments.
On 2017/8/15 17:50, Mark Rutland wrote:
> Hi,
>
> On Tue, Jul 25, 2017 at 08:10:37PM +0800, Shaokun Zhang wrote:
>> This patch adds documentation for the uncore PMUs on HiSilicon SoC.
>>
>> Reviewed-by: Jonathan Cameron
>> Signed-off-by: Shaokun Zhang
>> Sign
Hi Mark,
On 2017/8/15 18:16, Mark Rutland wrote:
> Hi,
>
> On Tue, Jul 25, 2017 at 08:10:38PM +0800, Shaokun Zhang wrote:
>> +/* Read Super CPU cluster and CPU cluster ID from MPIDR_EL1 */
>> +void hisi_read_sccl_and_ccl_id(u32 *sccl_id, u32 *ccl_id)
>> +{
>> +u64 mpidr;
>> +
>> +mpidr =
Hi Mark,
On 2017/8/15 18:41, Mark Rutland wrote:
> On Tue, Jul 25, 2017 at 08:10:39PM +0800, Shaokun Zhang wrote:
>> This patch adds support for L3C PMU driver in HiSilicon SoC chip, Each
>> L3C has own control, counter and interrupt registers and is an separate
>> PMU. For each L3C PMU, it has 8-
Hi Mark,
On 2017/8/15 19:05, Mark Rutland wrote:
> On Tue, Jul 25, 2017 at 08:10:40PM +0800, Shaokun Zhang wrote:
>> +/* HHA register definition */
>> +#define HHA_INT_MASK0x0804
>> +#define HHA_INT_STATUS 0x0808
>> +#define HHA_INT_CLEAR 0x080C
>> +#defi
Hi Mark,
On 2017/8/15 21:02, Mark Rutland wrote:
> On Tue, Jul 25, 2017 at 08:10:41PM +0800, Shaokun Zhang wrote:
>> This patch adds support for DDRC PMU driver in HiSilicon SoC chip, Each
>> DDRC has own control, counter and interrupt registers and is an separate
>> PMU. For each DDRC PMU, it has
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index 98fe715522e8..c303b235a0b1 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -1,19 +1,61 @@
> menu "printk and dmesg options"
>
> +choice
> + prompt "printk default clock timestamp"
> +
> +config PRINTK_TIME_DISABLE
>
On Thu, 17 Aug 2017 10:30:23 +0800
Zhangshaokun wrote:
> Hi Mark,
>
> Thanks for your comments.
>
> On 2017/8/15 17:50, Mark Rutland wrote:
> > Hi,
> >
> > On Tue, Jul 25, 2017 at 08:10:37PM +0800, Shaokun Zhang wrote:
> >> This patch adds documentation for the uncore PMUs on HiSilicon SoC.
> -Original Message-
> From: Waiman Long [mailto:long...@redhat.com]
> Sent: Wednesday, August 16, 2017 9:29 PM
> To: Wangkai (Kevin,C); Alexander Viro; Jonathan Corbet
> Cc: linux-ker...@vger.kernel.org; linux-doc@vger.kernel.org;
> linux-fsde...@vger.kernel.org; Paul E. McKenney; Andrew
From: Prarit Bhargava
Prarit,
So I took my own shot at cleaning up the Kconfig settings to make
it a bit more sane in my opinion. This should allow the legacy
defconfigs to just work, and avoids all the defconfig churn in the
patch.
I almost went through to try to simplify the code and make
P
On Wed, Aug 16, 2017 at 9:46 PM, John Stultz wrote:
> From: Prarit Bhargava
>
>
> Prarit,
> So I took my own shot at cleaning up the Kconfig settings to make
> it a bit more sane in my opinion. This should allow the legacy
> defconfigs to just work, and avoids all the defconfig churn in the
> p
On Thu, Aug 10, 2017 at 10:44:58AM -0400, Weiwei Jia wrote:
hi, Anyone can help me to improve this translation ?
rfkill - RF kill 开关的支持
===
1. 介绍
2. 实现细节
3. 内核 API
4. 用户态支持
1. 介绍
rfkill 子系统提供一个通用接口来禁用系统中的任意射频发射器。当发射器被禁用时，将
不再消耗系统电力。
这个子系统还提供通过按钮的操作来禁用特定种类射频发射器（或全部
27 matches
Mail list logo
