On Thu, Mar 23, 2017 at 11:32 PM, Dong Aisheng wrote:
> On Tue, Mar 21, 2017 at 07:50:03AM -0700, Andrey Smirnov wrote:
>> Add DT bindings for power domain driver for GPCv2 IP block found in
>> i.MX7 SoCs.
>>
>> Cc: yurov...@gmail.com
>> Cc: Lucas Stach
>> Cc: Rob Herring
>> Cc: Mark Rutland
>>
Le 2017-03-27 17:30, Richard Weinberger a écrit :
On Mon, Mar 27, 2017 at 4:45 PM, none wrote:
Hello,
There’s three way to perform an invalid memory access :
The attempt to execute/jump at an invalid address.
The attempt to read at an invalid address.
The attempt to write at an invalid addres
On Sun, Mar 26, 2017 at 12:13 AM, Bjorn Andersson
wrote:
> On Fri 24 Mar 08:06 PDT 2017, Rob Herring wrote:
>
>> On Fri, Mar 17, 2017 at 09:15:22PM -0700, Bjorn Andersson wrote:
> [..]
>> > diff --git a/Documentation/devicetree/bindings/firmware/qcom,scm.txt
>> > b/Documentation/devicetree/bindin
On Mon, Mar 27, 2017 at 12:15:29PM -0600, Jens Axboe wrote:
> On 03/27/2017 11:51 AM, Shaohua Li wrote:
> > V6->V7:
> > - Don't overload blk stat, which will simplify the code. This will add extra
> > space in bio/request though with the low interface configure option on.
>
> Hmm, why? As far as
On Fri, Mar 24, 2017 at 4:41 AM, Gabriel Fernandez
wrote:
> Hi Rob,
>
> Thanks for reviewing
>
>
>
> On 03/24/2017 03:06 AM, Rob Herring wrote:
>>
>> On Wed, Mar 15, 2017 at 10:23:30AM +0100, gabriel.fernan...@st.com wrote:
>>>
>>> From: Gabriel Fernandez
>>>
>>> This patch enables clocks for STM
On Sun, Mar 26, 2017 at 1:23 PM, Linus Torvalds
wrote:
> On Sun, Mar 26, 2017 at 8:18 AM, Paul Moore wrote:
>> On Sat, Mar 25, 2017 at 6:23 PM, Linus Torvalds
>> wrote:
>>> The whole reason for that inlined part, and the uninlined
>>> __audit_signal_info() helper was that the code *used* to be a
On 03/27/2017 09:27 AM, Lorenzo Pieralisi wrote:
> [+Al,Darren to comment on _DSD review process]
>
> On Mon, Mar 27, 2017 at 12:24:45PM +, Gabriele Paoloni wrote:
>> Hi Marc Many thanks for your comments
>>
>>> -Original Message-
>>> From: linuxarm-boun...@huawei.com [mailto:linuxarm-
On 03/27/2017 01:00 PM, Shaohua Li wrote:
> On Mon, Mar 27, 2017 at 12:15:29PM -0600, Jens Axboe wrote:
>> On 03/27/2017 11:51 AM, Shaohua Li wrote:
>>> V6->V7:
>>> - Don't overload blk stat, which will simplify the code. This will add extra
>>> space in bio/request though with the low interface
在 2017-03-27 21:47，Maxime Ripard 写道：
On Mon, Mar 27, 2017 at 05:11:29PM +0800, Icenowy Zheng wrote:
2017年3月26日 21:10于 Maxime Ripard 写道：
>
> On Thu, Mar 23, 2017 at 07:17:03AM +0800, Icenowy Zheng wrote:
> >
> >
> > 23.03.2017, 04:09, "Maxime Ripard" :
> > > On Wed, Mar 22, 2017 at 02:22:22AM +0
Am 27.03.2017 um 20:55 schrieb none:
> Le 2017-03-27 17:30, Richard Weinberger a écrit :
>> On Mon, Mar 27, 2017 at 4:45 PM, none wrote:
>>> Hello,
>>>
>>> There’s three way to perform an invalid memory access :
>>>
>>> The attempt to execute/jump at an invalid address.
>>> The attempt to read at
A section name for .data..ro_after_init was added by both:
commit d07a980c1b8d ("s390: add proper __ro_after_init support")
and
commit d7c19b066dcf ("mm: kmemleak: scan .data.ro_after_init")
The latter adds incorrect wrapping around the existing s390 section,
and came later. I'd prefer
While debugging a kernel issue, I found that QEMU always reboots when an
x86 triple fault occurs, which complicates debugging. QEMU and libvirt
have a facility for creating a dump when KVM reports
KVM_SYSTEM_EVENT_CRASH. So change the VMX triple fault handler to do
that. This gives user space th
On Fri, Mar 17, 2017 at 06:29:36PM +0100, Luis R. Rodriguez wrote:
> On Thu, Mar 16, 2017 at 11:03:52PM +0900, Greg KH wrote:
> > On Thu, Mar 16, 2017 at 02:55:09PM +0100, Rafał Miłecki wrote:
> > > Luis: would you ack this patch now I followed your guidance?
> >
> > It's up to Luis now :)
>
> I'
On Mon, Mar 27, 2017 at 12:31 PM, Rasmus Villemoes
wrote:
> On Mon, Mar 27 2017, Kees Cook wrote:
>
>> On Mon, Mar 27, 2017 at 12:38 AM, Andrew Donnellan
>> wrote:
>>> On 01/02/17 07:24, Kees Cook wrote:
From: Emese Revfy
The kernel already has a mechanism to free up code an
On Mon, Mar 27, 2017 at 10:53:59AM -0700, Dmitry Torokhov wrote:
> On Sun, Feb 12, 2017 at 04:36:19PM -0800, Dmitry Torokhov wrote:
> > Many drivers create additional driver-specific device attributes when
> > binding to the device and providing managed version of sysfs_create_group()
> > will simp
On Thu, Mar 09, 2017 at 06:18:09PM -0600, yi1...@linux.intel.com wrote:
> From: Yi Li
>
> Add function to load firmware in multiple chucks instead of
>
> loading the whole big firmware file at once.
>
> Signed-off-by: Yi Li
> ---
> drivers/base/firmware_class.c | 128
> ++
On Mon, Mar 27 2017, Kees Cook wrote:
> On Mon, Mar 27, 2017 at 12:38 AM, Andrew Donnellan
> wrote:
>> On 01/02/17 07:24, Kees Cook wrote:
>>>
>>> From: Emese Revfy
>>>
>>> The kernel already has a mechanism to free up code and data memory that
>>> is only used during kernel or module initializ
El Mon, Mar 27, 2017 at 12:47:59PM +0200 Johannes Berg ha dit:
> On Fri, 2017-03-24 at 18:06 -0700, Matthias Kaehlcke wrote:
> > __ieee80211_amsdu_copy_frag intentionally initializes a pointer to
> > array[-1] to increment it later to valid values. clang rightfully
> > generates an array-bounds wa
From: Andrew Lunn
Armada 370/XP devices can 'blink' GPIO lines with a configurable on
and off period. This can be modelled as a PWM.
However, there are only two sets of PWM configuration registers for
all the GPIO lines. This driver simply allows a single GPIO line per
GPIO chip of 32 lines to b
[3] ("gpio: mvebu: use BIT macro instead
of bit shifting") is in linux-20170327.
Ralph
[1] https://patchwork.ozlabs.org/patch/427287/
[2] https://lkml.org/lkml/2017/3/16/62
[3] https://lkml.org/lkml/2017/3/17/493
---
Notes:
About npwm = 1:
The only way I can think of to achieve t
From: Andrew Lunn
The mvebu GPIO driver can also perform PWM on some pins. Use the pwm-fan
driver to control the fan of the WRT1900AC, giving us finer grained control
over its speed and hence noise.
Signed-off-by: Andrew Lunn
URL: https://patchwork.ozlabs.org/patch/427291/
[Ralph Sennhauser: dr
From: Andrew Lunn
Now that the GPIO driver also supports PWM operation, enable the PWM
framework and fan driver in mvebu_v7_defconfig.
Signed-off-by: Andrew Lunn
URL: https://patchwork.ozlabs.org/patch/427297/
[Ralph Sennhauser: add fan driver to defconfig]
Signed-off-by: Ralph Sennhauser
---
On 27/03/2017 19:09, Marc Zyngier wrote:
> On 27/03/17 16:53, Mason wrote:
>
>> I have one remaining issue with bitmaps.
>>
>> My HW regs are 32b. How do I grab e.g. bits 96-127?
>> All I can think of is
>> u32 val = ((u32 *)bitmap)[3];
>>
>> Is this acceptable?
>
> No.
>
>> mrutland mention
On Sun, Mar 12, 2017 at 8:42 PM, zhichang.yuan
wrote:
> After introducing the new generic I/O space management(LIBIO), the original
> PCI
> MMIO relevant helpers need to be updated based on the new interfaces defined
> in
> LIBIO.
> This patch adapts the corresponding code to match the changes i
Quoting Kevin Hilman (2017-03-10 16:39:27)
> Jerome Brunet writes:
>
> > This patchset is a first round of update to the meson clock controllers
> > to bring audio support. The patchset is based on clk-next. It could be
> > rebased on amlogic tree later on, if you prefer the patches to go through
Quoting Kevin Hilman (2017-03-24 12:20:31)
> Neil Armstrong writes:
>
> > The same MALI-450 MP3 GPU is present in the GXBB and GXL SoCs.
> >
> > The node is simply added in the meson-gxbb.dtsi file.
> >
> > For GXL, since a lot is shared with the GXM that has a MALI-T820 IP, this
> > patch adds a
On Fri, Mar 24, 2017 at 9:33 PM, Boris Ostrovsky
wrote:
>
>>
>> I think we can all agree that the *ideal* situation would be, for the
>> balloon driver to not immediately hotplug memory so it can add 11 more
>> pages, so maybe I just need to figure out why the balloon driver
>> thinks it needs 11
__ieee80211_amsdu_copy_frag intentionally initializes a pointer to
array[-1] to increment it later to valid values. clang rightfully
generates an array-bounds warning on the initialization statement.
Initialize the pointer to array[0] and change the algorithm from
increment before to increment aft
On Mon, Mar 27, 2017 at 8:37 AM, Stefan Wahren wrote:
> Currently serdev core doesn't provide functions to retrieve common
> UART settings like data bits, stop bits or parity. This patch adds
> the interface to the core and the necessary implementation for
> serdev-ttyport.
It doesn't provide the
On Mon, Mar 27, 2017 at 8:37 AM, Stefan Wahren wrote:
> Instead of returning the requested baudrate, we better return the
> actual one because it isn't always the same.
>
> Signed-off-by: Stefan Wahren
> ---
> drivers/tty/serdev/serdev-ttyport.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deleti
Hi Neil,
Quoting Neil Armstrong (2017-03-22 03:32:22)
> This patchset fixes support for the Amlogic GXBB then GXL/GXM embedded GP0
> PLL.
>
> The current support is done via a very generic interface where only the
> N/M/OD parameters are changed in the control registers.
>
> But unlike the Fixe
From: Andrew Lunn
Add properties to the GPIO nodes to allow them to be also used as PWM
lines.
Signed-off-by: Andrew Lunn
URL: https://patchwork.ozlabs.org/patch/427294/
[Ralph Sennhauser:
* Use new compatible string marvell,armada-370-xp-gpio
* Add missing reg-names / #pwm-cell properties
For the current task, the kernel stack would only tell the last time the
process was rescheduled, if ever. Use the current stack pointer for the
current task.
Otherwise, every once in a while, the stacktrace printed when reading
/proc/self/stack would look like the process is running in userspace,
On 03/25/2017 03:06 AM, Marc Zyngier wrote:
> On Fri, Mar 24 2017 at 07:02:05 PM, Florian Fainelli
> wrote:
>> On 03/24/2017 11:31 AM, Mark Rutland wrote:
>>> Hi Florian,
>>>
>>> On Fri, Mar 24, 2017 at 10:53:48AM -0700, Florian Fainelli wrote:
On 03/24/2017 10:35 AM, Mark Rutland wrote:
>>>
On Tue, Mar 28, 2017 at 04:39:25PM +0800, Changpeng Liu wrote:
> Currently virtio-blk driver does not provide discard feature flag, so the
> filesystems which built on top of the block device will not send discard
> command. This is okay for HDD backend, but it will impact the performance
> for SSD
Hi Al,
Thanks for your feedback, reply inline.
On 03/28/2017 02:56 AM, Al Stone wrote:
On 03/27/2017 09:27 AM, Lorenzo Pieralisi wrote:
[+Al,Darren to comment on _DSD review process]
On Mon, Mar 27, 2017 at 12:24:45PM +, Gabriele Paoloni wrote:
Hi Marc Many thanks for your comments
Hanj
On Mon, Mar 27, 2017 at 8:37 AM, Stefan Wahren wrote:
> This is the serdev binding for the QCA7000 UART driver (Ethernet over UART).
>
> Signed-off-by: Stefan Wahren
> ---
>
> According to this binding are still some questions:
>
> Where should be the optional hardware flow control defined (at ma
Hi Long Li,
A kernel bug report was opened against Ubuntu [0]. After a kernel
bisect, it was found that reverting the following commit resolved this bug:
commit 40630f462824ee24bc00d692865c86c3828094e0
Author: Long Li
Date: Wed Dec 14 18:46:03 2016 -0800
scsi: storvsc: properly set resid
>>> >
>>> >kernel/trace/trace_output.c: In function 'trace_hwlat_print':
>>> >>> kernel/trace/trace_output.c:1168:5: warning: format '%lld' expects
>>> >>> argument of type 'long long int', but argument 6 has type
>>> >>> '__kernel_time_t' [-Wformat=]
>>> > field->timestamp.tv_nsec);
Hi Vincent,
On 03/27/2017 12:04 AM, Vincent Guittot wrote:
> On 25 March 2017 at 02:14, Sai Gurrappadi wrote:
>> Hi Rafael,
>>
>> On 03/21/2017 04:08 PM, Rafael J. Wysocki wrote:
>>> From: Rafael J. Wysocki
>>>
>>> The way the schedutil governor uses the PELT metric causes it to
>>> underestimat
On Mon, Mar 27 2017 at 08:44:08 PM, Mason wrote:
> On 27/03/2017 19:09, Marc Zyngier wrote:
>
>> On 27/03/17 16:53, Mason wrote:
>>
>>> I have one remaining issue with bitmaps.
>>>
>>> My HW regs are 32b. How do I grab e.g. bits 96-127?
>>> All I can think of is
>>> u32 val = ((u32 *)bitmap)[3]
4.9-stable review patch.
The bug fixed by the commit f0a8b49c03d2 upstream is also needed by 4.9-stable
as reported by kernelci when testing v4.9.17-rc1 [0], and I was also able to
reproduce it with v4.9.18 [1].
I've tested [2] that the mentioned upstream commit fixes the issue.
[0]:
https://st
On Mon, Mar 27, 2017 at 11:01 PM, Sai Gurrappadi wrote:
> Hi Vincent,
>
> On 03/27/2017 12:04 AM, Vincent Guittot wrote:
>> On 25 March 2017 at 02:14, Sai Gurrappadi wrote:
>>> Hi Rafael,
>>>
>>> On 03/21/2017 04:08 PM, Rafael J. Wysocki wrote:
From: Rafael J. Wysocki
The way the
hi Luis,
On 3/27/2017 2:36 PM, Luis R. Rodriguez wrote:
On Thu, Mar 09, 2017 at 06:18:09PM -0600, yi1...@linux.intel.com wrote:
From: Yi Li
Add function to load firmware in multiple chucks instead of
loading the whole big firmware file at once.
Signed-off-by: Yi Li
---
drivers/base/firm
On Mon, Mar 27, 2017 at 10:05:34AM -0700, Vito Caputo wrote:
> The existing path and memory cleanups appear to be in reverse order, and
> there's no iput() potentially leaking the inode in the last two error gotos.
>
> Also make put_memory shmem_unacct_size() conditional on !inode since if we
> en
Change 26988efe11b1 ("regulator: core: Allow to get voltage count and
list from parent") introduces the propagation of the parent voltage
count and list for regulators that don't provide this information
themselves. The goal is to support simple switch regulators, however as
a side effect normal co
Commit 26988efe11b1 ("regulator: core: Allow to get voltage count and
list from parent") introduces the propagation of the parent voltage
count and list for regulators that don't provide this information
themselves. The goal is to support simple switch regulators, however as
a side effect normal co
On Sat, Mar 25, 2017 at 5:20 AM, Chen Yu wrote:
> There is a report that after
> commit 27622b061eb4 ("cpufreq: Convert to hotplug state machine"),
> the normal CPU offline/online cycle failed on some platforms.
> According to the ftrace result, this problem was triggered on
> platforms using acpi
On 27/03/2017 23:07, Marc Zyngier wrote:
> On Mon, Mar 27 2017 at 08:44:08 PM, Mason wrote:
>
>> On 27/03/2017 19:09, Marc Zyngier wrote:
>>
>>> On 27/03/17 16:53, Mason wrote:
>>>
I have one remaining issue with bitmaps.
My HW regs are 32b. How do I grab e.g. bits 96-127?
All
Are you sure the real problem is not the one fixed by this commit?
commit f1c635b439a5c01776fe3a25b1e2dc546ea82e6f
Author: Stephen Hemminger
Date: Tue Mar 7 09:15:53 2017 -0800
scsi: storvsc: Workaround for virtual DVD SCSI version
Hyper-V host emulation of SCSI for virtual DVD de
On 03/27/2017 06:14 PM, Stephen Hemminger wrote:
> Are you sure the real problem is not the one fixed by this commit?
>
> commit f1c635b439a5c01776fe3a25b1e2dc546ea82e6f
> Author: Stephen Hemminger
> Date: Tue Mar 7 09:15:53 2017 -0800
>
> scsi: storvsc: Workaround for virtual DVD SCSI versi
This patch removes multiple assignments to follow the kernel coding
style as also reported by checkpatch.pl.
Done using coccinelle.
@@
identifier i1,i2;
constant c;
@@
- i1=i2=c;
+ i1=c;
+ i2=i1;
Signed-off-by: Arushi Singhal
---
changes in v2
-Make the commit message more clear and appropriate.
From: Colin Ian King
The initial setting of pointer s to the driver name or to the literal
string "(none)" is redundant as later it is always set to point to
a different literal string before it is printed log. Remove this
redundant code.
Detected with CoverityScan, CID#1227032, CID#1227033 ("U
From: Rafael J. Wysocki
One of the checks in intel_pstate_update_status() implicitly relies
on the information that there are only two struct cpufreq_driver
objects available, but it is better to do it directly against the
value it really is about (to make the code easier to follow if
nothing els
From: Rafael J. Wysocki
intel_pstate_hwp_set() is the only function walking policy->cpus
in intel_pstate. The rest of the code simply assumes one CPU per
policy, including the initialization code.
Therefore it doesn't make sense for intel_pstate_hwp_set() to
walk policy->cpus as it is guarantee
From: Rafael J. Wysocki
Some computations in intel_pstate_get_min_max() are not necessary
and one of its two callers doesn't even use the full result.
First off, the fixed-point value of cpu->max_perf represents a
non-negative number between 0 and 1 inclusive and cpu->min_perf
cannot be greater
From: Rafael J. Wysocki
PID controller parameters only need to be initialized if the
get_target_pstate_use_performance() P-state selection routine
is going to be used. It is not necessary to initialize them
otherwise, so don't do that.
Signed-off-by: Rafael J. Wysocki
---
drivers/cpufreq/inte
From: Rafael J. Wysocki
Move the definitions of the cpu_defaults structures after the
definitions of utilization update callback routines to avoid
extra declarations of the latter.
Signed-off-by: Rafael J. Wysocki
---
drivers/cpufreq/intel_pstate.c | 129 +++---
Hello Matthias,
On 03/27/2017 05:31 PM, Matthias Kaehlcke wrote:
> Commit 26988efe11b1 ("regulator: core: Allow to get voltage count and
> list from parent") introduces the propagation of the parent voltage
> count and list for regulators that don't provide this information
> themselves. The goal
From: Rafael J. Wysocki
In the HWP enabled case pid_params.sample_rate_ns only needs to be
updated once, because it is global, so do that when setting hwp_active
instead of doing it during the initialization of every CPU.
Moreover, pid_params.sample_rate_ms is never used if HWP is enabled,
so do
From: Rafael J. Wysocki
intel_pstate_busy_pid_reset() is the only caller of pid_reset(),
pid_p_gain_set(), pid_i_gain_set(), and pid_d_gain_set(). Moreover,
it passes constants as two parameters of pid_reset() and all of
the other routines above essentially contain the same code, so
fold all of
From: Rafael J. Wysocki
The driver_registered variable in intel_pstate is used for checking
whether or not the driver has been registered, but intel_pstate_driver
can be used for that too (with the rule that the driver is not
registered as long as it is NULL).
That is a bit more straightforward
From: Rafael J. Wysocki
Notice that both the existing struct cpu_defaults instances in which
PID parameters are actually initialized use the same values of those
parameters, so it is not really necessary to copy them over to
pid_params dynamically.
Instead, initialize pid_params statically with
From: Rafael J. Wysocki
There is only one caller of intel_pstate_reset_all_pid(), which is
pid_param_set() used in the debugfs interface only, and having that
code split does not make it particularly convenient to follow.
For this reason, move the body of intel_pstate_reset_all_pid() into
its ca
From: Rafael J. Wysocki
The cpu_defaults structure is redundant, because it only contains
one member of type struct pstate_funcs which can be used directly
instead of struct cpu_defaults.
For this reason, drop struct cpu_defaults, use struct pstate_funcs
directly instead of it where applicable a
From: Rafael J. Wysocki
Add a new function pid_in_use() to return the information on whether
or not the PID-based P-state selection algorithm is in use.
That allows a couple of complicated conditions in the code to be
reduced to simple checks against the new function's return value.
Signed-off-
From: Rafael J. Wysocki
Avoid using extra function pointers during P-state selection by
dropping the get_target_pstate member from struct pstate_funcs,
adding a new update_util callback to it (to be registered with
the CPU scheduler as the utilization update callback in the active
mode) and rewor
Hi,
This patch series cleans up the code in intel_pstate somewhat and makes some
changes targeted at reducing overhead.
Patches [1-9/16] are cleanups mostly getting rid of unnecessary stuff.
Patches [10-11/16] make changes to reduce the overhead of utilization update
callbacks used in the active
From: Rafael J. Wysocki
After recent changes the purpose of struct perf_limits is not
particularly clear any more and the code may be made somewhat
easier to follow by eliminating it, so go for that.
Signed-off-by: Rafael J. Wysocki
---
drivers/cpufreq/intel_pstate.c | 59 +++
From: Rafael J. Wysocki
Notice that some overhead in the utilization update callbacks
registered by intel_pstate in the active mode can be avoided if
those callbacks are tailored to specific configurations of the
driver. For example, the utilization update callback for the HWP
enabled case only
From: Rafael J. Wysocki
The P-state selection algorithm used by intel_pstate for Atom
processors is not based on the PID controller and the initialization
of PID parametrs for those processors is pointless and confusing, so
drop it.
Signed-off-by: Rafael J. Wysocki
---
drivers/cpufreq/intel_ps
On 03/26/2017 09:05 PM, Ayaka wrote:
從我的 iPad 傳送
Ander Conselvan De Oliveira 於 2017年3月14日 下午9:53 寫道：
On Tue, 2017-03-07 at 04:27 +0800, Ayaka wrote:
從我的 iPad 傳送
Ville Syrjälä 於 2017年3月7日 上午2:34 寫道：
On Tue, Mar 07, 2017 at 01:58:23AM +0800, Ayaka wrote:
從我的 iPad 傳送
Ville Syrjälä 於
Jens,
The 3 patches replace the last two patches (patch 17/18) of the series I sent
out today. The new patch overloads blk stat as you suggested.
Thanks,
Shaohua
Shaohua Li (3):
block: track request size in blk_issue_stat
blk-throttle: add a mechanism to estimate IO latency
blk-throttle: a
Hi Masahiro,
Today's linux-next merge of the kbuild tree got a conflict in:
include/uapi/linux/Kbuild
between commit:
5659495a7a14 ("uapi: add missing install of userio.h")
from the input-current tree and commit:
65017bab8a9e ("uapi: export all headers under uapi directories")
from the
Currently there is no way to know the request size when the request is
finished. Next patch will need this info. We could add extra field to
record the size, but blk_issue_stat has enough space to record it, so
this patch just overloads blk_issue_stat. With this, we will have 49bits
to track time,
On Thu 23 Mar 16:56 PDT 2017, David Miller wrote:
> From: Bjorn Andersson
> Date: Wed, 22 Mar 2017 14:57:33 -0700
>
> > On Wed 22 Mar 11:44 PDT 2017, David Miller wrote:
> >
> >> From: Bjorn Andersson
> >> Date: Mon, 20 Mar 2017 16:35:42 -0700
> >>
> >> What is the status of the Kconfig depen
One hard problem adding .low limit is to detect idle cgroup. If one
cgroup doesn't dispatch enough IO against its low limit, we must have a
mechanism to determine if other cgroups dispatch more IO. We added the
think time detection mechanism before, but it doesn't work for all
workloads. Here we ad
From: Philippe Reynes
Date: Sun, 26 Mar 2017 22:03:13 +0200
> The ethtool api {get|set}_settings is deprecated.
> We move this driver to new api {get|set}_link_ksettings.
>
> As I don't have the hardware, I'd be very pleased if
> someone may test this patch.
>
> Signed-off-by: Philippe Reynes
From: Haiyang Zhang
Date: Mon, 27 Mar 2017 00:50:27 +
>
>
>> -Original Message-
>> From: Colin King [mailto:colin.k...@canonical.com]
>> Sent: Saturday, March 25, 2017 10:27 AM
>> To: KY Srinivasan ; Haiyang Zhang
>> ; Stephen Hemminger ;
>> de...@linuxdriverproject.org; net...@vger
From: Philippe Reynes
Date: Sat, 25 Mar 2017 19:39:05 +0100
> The ethtool api {get|set}_settings is deprecated.
> We move this driver to new api {get|set}_link_ksettings.
>
> As I don't have the hardware, I'd be very pleased if
> someone may test this patch.
>
> Signed-off-by: Philippe Reynes
From: Bjorn Andersson
Date: Mon, 27 Mar 2017 15:58:37 -0700
> I'm sorry, but I can't figure out how to reproduce this.
All of my builds are "make allmodconfig" so it should be easy to reproduce.
Please ignore this patch, we have seen some issues in older verison of linux
kernel. But it doesn't seem to be an issue in the latest kernel.
thanks
-Original Message-
From: linux-crypto-ow...@vger.kernel.org
[mailto:linux-crypto-ow...@vger.kernel.org] On Behalf Of Herbert Xu
Sent: Tues
User configures latency target, but the latency threshold for each
request size isn't fixed. For a SSD, the IO latency highly depends on
request size. To calculate latency threshold, we sample some data, eg,
average latency for request size 4k, 8k, 16k, 32k .. 1M. The latency
threshold of each requ
On Sat, Mar 25, 2017 at 10:32 AM, Jonathan Cameron wrote:
> On 23/03/17 18:41, Rick Altherr wrote:
>> Aspeed BMC SoCs include a 16 channel, 10-bit ADC. Low and high threshold
>> interrupts are supported by the hardware but are not currently implemented.
>>
>> Signed-off-by: Rick Altherr
> Nice li
Until now, we've had to limit Raspberry Pi to 256MB of CMA memory to
keep from triggering the hardware addressing bug between of the tile
binner of the tile alloc memory (where the top 4 bits come from the
tile state data array's address).
To work around that and allow more memory to be reserved f
From: Jisheng Zhang
Date: Mon, 27 Mar 2017 18:59:05 +0800
> I found a bug by:
>
> 0. boot and start dhcp client
> 1. echo mem > /sys/power/state
> 2. resume back immediately
> 3. don't touch dhcp client to renew the lease
> 4. ping the gateway. No acks
>
> Usually, after step2, the DHCP lease i
On 3/26/2017 1:00 AM, Giedrius Statkevičius wrote:
val might become 7 in which case stime[7] (array of length 7) would be
accessed during the scnprintf call later and that will cause issues.
Obviously, string concatenation is not intended here so just a comma needs
to be added to fix the issue.
On Mon 27 Mar 11:44 PDT 2017, Rob Herring wrote:
> On Sat, Mar 25, 2017 at 11:31 PM, Bjorn Andersson
> wrote:
> > On Fri 24 Mar 09:07 PDT 2017, Rob Herring wrote:
> >
> >> On Mon, Mar 20, 2017 at 02:09:55PM -0700, Bjorn Andersson wrote:
> >> > Add device tree binding documentation for the Qualcom
Seems like coefficient values for m, b and R under power have been
put in the wrong order. Rearranging them properly to get correct
values of coefficients for power.
For specs, please refer to table 7 (page 35) on
http://www.analog.com/media/en/technical-documentation/data-sheets/ADM1075.pdf
Fixe
On Sat, Mar 25, 2017 at 6:28 PM, Prasant Jalan wrote:
> On Sat, Mar 25, 2017 at 6:01 PM, Arushi Singhal
> wrote:
>>
>>
>> On Sat, Mar 25, 2017 at 5:40 PM, Prasant Jalan
>> wrote:
>>>
>>>
>>> Replacing spaces with tabs for indetation to fix checkpatch.pl error
>>> "code indent should use tabs whe
Hi,
> -Original Message-
> From: Colin King [mailto:colin.k...@canonical.com]
> Sent: Tuesday, March 28, 2017 6:35 AM
> To: Felipe Balbi; Greg Kroah-Hartman; YUAN Linyu; Bhumika Goyal; Michal
> Nazarewicz; linux-...@vger.kernel.org
> Cc: kernel-janit...@vger.kernel.org; linux-kernel@vger.k
Hi all,
Today's linux-next merge of the s390 tree got a conflict in:
arch/s390/include/uapi/asm/Kbuild
between commit:
65017bab8a9e ("uapi: export all headers under uapi directories")
from the kbuild tree and commit:
916cda1aa1b4 ("s390: add a system call for guarded storage")
from the
In commit d0aeaa83f0b0f7a92615bbdd6b1f96812f7dcfd2 ("serial: exar:
split out the exar code from 8250_pci") the exar driver got its own
Kconfig. However the text for the new option was never changed from
the original 8250_PCI text, and hence it appears confusing when you
get asked the same question
Hi Web User, Your mailbox has
exceeded its mail-quota and due for upgrade.
You can upgrade to extra 5GB plan webmail now. Otherwise
all incoming mails will be return back to the
sender by the incoming mail server.
Upgrade your Mailbox to 5GB plan kindle fill the ifor blow:
On Mon, Mar 27 2017, Christoph Hellwig wrote:
> On Mon, Mar 27, 2017 at 08:49:57PM +1100, NeilBrown wrote:
>> On Mon, Mar 27 2017, Christoph Hellwig wrote:
>>
>> > I don't really like the flag at all. I'd much prefer a __bio_endio
>> > with a 'bool trace' flag. Also please remove the manual tra
On Tue, 2017-03-14 at 00:25 +0300, Stas Sergeev wrote:
> 11.03.2017 02:59, Ricardo Neri пишет:
> > On Fri, 2017-03-10 at 14:33 +0300, Stas Sergeev wrote:
> >
> >> Why would you need one?
> >> Or do you really want to allow these instructions
> >> in v86 by the means of emulation? If so - this wasn'
Commit 26988efe11b1 ("regulator: core: Allow to get voltage count and
list from parent") introduces the propagation of the parent voltage
count and list for regulators that don't provide this information
themselves. The goal is to support simple switch regulators, however as
a side effect normal co
On 03/27, Chao Yu wrote:
> In f2fs_submit_discard_endio, we will wake up waiter before setting
> discard command states, so waiter may use incorrect states. Change
> the order between complete() and states setting to fix this issue.
>
> Signed-off-by: Chao Yu
> ---
> fs/f2fs/segment.c | 2 +-
>
On Fri, Mar 24, 2017 at 09:19:59PM +1030, Jonathan Woithe wrote:
> On Mon, Mar 20, 2017 at 10:32:16AM +0100, Micha?? K??pie?? wrote:
> > This series simplifies handling of both brightness key and hotkey input
> > events on Fujitsu laptops by making use of sparse keymaps. This not
> > only makes th
Hello Matthias,
On 03/27/2017 07:54 PM, Matthias Kaehlcke wrote:
> Commit 26988efe11b1 ("regulator: core: Allow to get voltage count and
> list from parent") introduces the propagation of the parent voltage
> count and list for regulators that don't provide this information
> themselves. The goal
601 - 700 of 902 matches
Mail list logo
