From: Joonsoo Kim
page_reference manipulation functions are introduced to track down
reference count change of the page. Use it instead of direct modification
of _count.
Signed-off-by: Joonsoo Kim
---
From: Joonsoo Kim
page_reference manipulation functions are introduced to track down
reference count change of the page. Use it instead of direct modification
of _count.
Signed-off-by: Joonsoo Kim
---
drivers/net/ethernet/cavium/thunder/nicvf_queues.c | 2 +-
On 25 March 2016 at 22:10, Jens Axboe wrote:
> On 03/25/2016 02:19 AM, Baolin Wang wrote:
>>
>> diff --git a/drivers/mmc/card/block.c b/drivers/mmc/card/block.c
>> index fe207e5..d372a2d 100644
>> --- a/drivers/mmc/card/block.c
>> +++ b/drivers/mmc/card/block.c
>> @@ -46,6 +46,9 @@
On 25 March 2016 at 22:10, Jens Axboe wrote:
> On 03/25/2016 02:19 AM, Baolin Wang wrote:
>>
>> diff --git a/drivers/mmc/card/block.c b/drivers/mmc/card/block.c
>> index fe207e5..d372a2d 100644
>> --- a/drivers/mmc/card/block.c
>> +++ b/drivers/mmc/card/block.c
>> @@ -46,6 +46,9 @@
>>
>>
在 2016年03月28日 10:43, David Miller 写道:
From: "zhaoxiu.zeng"
Date: Sun, 27 Mar 2016 14:43:10 +0800
+
+/*
+ * parityN: returns the parity of a N-bit word,
+ * i.e. the number of 1-bits in x modulo 2.
+ */
+
+#define __arch_parity4(w) (__arch_hweight8((w) & 0xf) & 1)
在 2016年03月28日 10:43, David Miller 写道:
From: "zhaoxiu.zeng"
Date: Sun, 27 Mar 2016 14:43:10 +0800
+
+/*
+ * parityN: returns the parity of a N-bit word,
+ * i.e. the number of 1-bits in x modulo 2.
+ */
+
+#define __arch_parity4(w) (__arch_hweight8((w) & 0xf) & 1)
+#define
Hello,
Ping.
- Sanchayan.
On 16-03-11 14:29:27, Sanchayan Maity wrote:
> Hello,
>
> This patchset implements SoC bus support for Freescale Vybrid platform,
> implementing the following
> https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-devices-soc
>
> This a reworked version of an
Hello,
Ping.
- Sanchayan.
On 16-03-11 14:29:27, Sanchayan Maity wrote:
> Hello,
>
> This patchset implements SoC bus support for Freescale Vybrid platform,
> implementing the following
> https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-devices-soc
>
> This a reworked version of an
On 28.03.2016 14:35, Anand Moon wrote:
> Should their be a fix in the u-boot for HK for this issue ?
It depends whether U-Boot S2MPS11 driver has this bug or has not. I did
not observe any issues with U-Boot at this matter.
> mmc card detection logic is pretty old in HK u-boot.
This is not
On 28.03.2016 14:35, Anand Moon wrote:
> Should their be a fix in the u-boot for HK for this issue ?
It depends whether U-Boot S2MPS11 driver has this bug or has not. I did
not observe any issues with U-Boot at this matter.
> mmc card detection logic is pretty old in HK u-boot.
This is not
Hi Krzysztof
On 28 March 2016 at 09:02, Krzysztof Kozlowski wrote:
> On 28.03.2016 10:59, Javier Martinez Canillas wrote:
>> Hello Krzysztof,
>>
>> On 03/27/2016 08:54 PM, Krzysztof Kozlowski wrote:
>>> The buck9 regulator of S2MPS11 PMIC lacked minimal selector for
Hi Krzysztof
On 28 March 2016 at 09:02, Krzysztof Kozlowski wrote:
> On 28.03.2016 10:59, Javier Martinez Canillas wrote:
>> Hello Krzysztof,
>>
>> On 03/27/2016 08:54 PM, Krzysztof Kozlowski wrote:
>>> The buck9 regulator of S2MPS11 PMIC lacked minimal selector for linear
>>> mapping. The
On 22-03-16, 02:51, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Move definitions of symbols related to transition latency and
> sampling rate to include/linux/cpufreq.h so they can be used by
> (future) goverernors located outside of drivers/cpufreq/.
On 22-03-16, 02:51, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Move definitions of symbols related to transition latency and
> sampling rate to include/linux/cpufreq.h so they can be used by
> (future) goverernors located outside of drivers/cpufreq/.
s/goverernors/governors
>
> No
On 27.03.2016 16:41, Anand Moon wrote:
>
> On My Odroid U3 with debug flags enable I am observing bellow deadlock.
There is a sleep in atomic context and possible deadlock, but:
1. Are you sure it does not happen without the patch?
2. Are you sure it is not the same as already known issue on
On 27.03.2016 16:41, Anand Moon wrote:
>
> On My Odroid U3 with debug flags enable I am observing bellow deadlock.
There is a sleep in atomic context and possible deadlock, but:
1. Are you sure it does not happen without the patch?
2. Are you sure it is not the same as already known issue on
On Sun, 2016-03-27 at 13:00 -0400, Paul Gortmaker wrote:
> In the ongoing audit/cleanup of non-modular code needlessly using
> modular infrastructure, the SCSI subsystem fortunately only contains
> two instances that I detected. Both are for legacy drivers that
> predate the git epoch, so
This patch adds the description to explain the TDP reporting mechanism
and accumulated power algorithm.
Signed-off-by: Huang Rui
Cc: Borislav Petkov
---
Documentation/hwmon/fam15h_power | 57 +++-
On Sun, 2016-03-27 at 13:00 -0400, Paul Gortmaker wrote:
> In the ongoing audit/cleanup of non-modular code needlessly using
> modular infrastructure, the SCSI subsystem fortunately only contains
> two instances that I detected. Both are for legacy drivers that
> predate the git epoch, so
This patch adds the description to explain the TDP reporting mechanism
and accumulated power algorithm.
Signed-off-by: Huang Rui
Cc: Borislav Petkov
---
Documentation/hwmon/fam15h_power | 57 +++-
drivers/hwmon/fam15h_power.c | 2 +-
2 files changed, 57
This patch adds a platform check function to make code more readable.
Signed-off-by: Huang Rui
---
drivers/hwmon/fam15h_power.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/hwmon/fam15h_power.c b/drivers/hwmon/fam15h_power.c
index
This patch introduces an algorithm that computes the average power by
reading a delta value of “core power accumulator” register during
measurement interval, and then dividing delta value by the length of
the time interval.
User is able to use power1_average entry to measure the processor power
This patch adds a platform check function to make code more readable.
Signed-off-by: Huang Rui
---
drivers/hwmon/fam15h_power.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/hwmon/fam15h_power.c b/drivers/hwmon/fam15h_power.c
index c1cad26..622c646 100644
This patch introduces an algorithm that computes the average power by
reading a delta value of “core power accumulator” register during
measurement interval, and then dividing delta value by the length of
the time interval.
User is able to use power1_average entry to measure the processor power
On 22-03-16, 02:46, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Replace the single helper for adding and removing cpufreq utilization
> update hooks, cpufreq_set_update_util_data(), with a pair of helpers,
> cpufreq_add_update_util_hook() and
Hi Guenter,
This serial of patches introduces an accumulated power reporting
algorithm. It will calculate the average power consumption for the
processor. The cpu feature flag is CPUID.8000_0007H:EDX[12].
This algorithm is used to test the comparison of processor power
consumption with between
On 22-03-16, 02:46, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Replace the single helper for adding and removing cpufreq utilization
> update hooks, cpufreq_set_update_util_data(), with a pair of helpers,
> cpufreq_add_update_util_hook() and cpufreq_remove_update_util_hook(),
> and
Hi Guenter,
This serial of patches introduces an accumulated power reporting
algorithm. It will calculate the average power consumption for the
processor. The cpu feature flag is CPUID.8000_0007H:EDX[12].
This algorithm is used to test the comparison of processor power
consumption with between
This patch adds CONFIG_CPU_SUP_AMD as the dependence of fam15h_power
driver. Because the following patch will use the interface from
x86/kernel/cpu/amd.c.
Otherwise, the below error might be encountered:
All errors (new ones prefixed by >>):
drivers/built-in.o: In function
PTSC is the performance timestamp counter value in a cpu core and the
cores in one compute unit have the fixed frequency. So it picks up the
performance timestamp counter value of the first core per compute unit
to measure the interval for average power per compute unit.
Signed-off-by: Huang Rui
This patch adds CONFIG_CPU_SUP_AMD as the dependence of fam15h_power
driver. Because the following patch will use the interface from
x86/kernel/cpu/amd.c.
Otherwise, the below error might be encountered:
All errors (new ones prefixed by >>):
drivers/built-in.o: In function
PTSC is the performance timestamp counter value in a cpu core and the
cores in one compute unit have the fixed frequency. So it picks up the
performance timestamp counter value of the first core per compute unit
to measure the interval for average power per compute unit.
Signed-off-by: Huang Rui
This patch adds a member in fam15h_power_data which specifies the
compute unit accumulated power. It adds do_read_registers_on_cu to do
all the read to all MSRs and run it on one of the online cores on each
compute unit with smp_call_function_many(). This behavior can decrease
IPI numbers.
This patch adds a member in fam15h_power_data which specifies the
compute unit accumulated power. It adds do_read_registers_on_cu to do
all the read to all MSRs and run it on one of the online cores on each
compute unit with smp_call_function_many(). This behavior can decrease
IPI numbers.
Hi Soren,
> -Original Message-
> From: Sören Brinkmann [mailto:soren.brinkm...@xilinx.com]
> Sent: Monday, March 28, 2016 12:56 AM
> To: Appana Durga Kedareswara Rao
> Cc: robh...@kernel.org; pawel.m...@arm.com; mark.rutl...@arm.com;
> ijc+devicet...@hellion.org.uk; ga...@codeaurora.org;
Hi Soren,
> -Original Message-
> From: Sören Brinkmann [mailto:soren.brinkm...@xilinx.com]
> Sent: Monday, March 28, 2016 12:56 AM
> To: Appana Durga Kedareswara Rao
> Cc: robh...@kernel.org; pawel.m...@arm.com; mark.rutl...@arm.com;
> ijc+devicet...@hellion.org.uk; ga...@codeaurora.org;
From: Joonsoo Kim
There are mostly same code for setting up kmem_cache_node either
in cpuup_prepare() or alloc_kmem_cache_node(). Factor out and
clean-up them.
Signed-off-by: Joonsoo Kim
---
mm/slab.c | 167
Add clock controller nodes for MT2701, include topckgen, infracfg,
pericfg, apmixedsys, mmsys, imgsys, vdecsys, hifsys, ethsys and
bdpsys. This patch also add two oscillators that provide clocks for
MT2701.
Signed-off-by: James Liao
---
This patch is based on v4.6-rc1
From: Joonsoo Kim
There are mostly same code for setting up kmem_cache_node either
in cpuup_prepare() or alloc_kmem_cache_node(). Factor out and
clean-up them.
Signed-off-by: Joonsoo Kim
---
mm/slab.c | 167 +-
1 file changed, 67
Add clock controller nodes for MT2701, include topckgen, infracfg,
pericfg, apmixedsys, mmsys, imgsys, vdecsys, hifsys, ethsys and
bdpsys. This patch also add two oscillators that provide clocks for
MT2701.
Signed-off-by: James Liao
---
This patch is based on v4.6-rc1 and MT2701 clock patches
From: Joonsoo Kim
Currently, determination to free a slab is done whenever free object is
put into the slab. This has a problem that free slabs are not freed
even if we have free slabs and have more free_objects than free_limit
when processed slab isn't a free slab. This
From: Joonsoo Kim
Slab color isn't needed to be changed strictly. Because locking
for changing slab color could cause more lock contention so this patch
implements racy access/modify the slab color. This is a preparation step
to implement lockless allocation path when
From: Joonsoo Kim
Currently, determination to free a slab is done whenever free object is
put into the slab. This has a problem that free slabs are not freed
even if we have free slabs and have more free_objects than free_limit
when processed slab isn't a free slab. This would cause to keep
too
From: Joonsoo Kim
Slab color isn't needed to be changed strictly. Because locking
for changing slab color could cause more lock contention so this patch
implements racy access/modify the slab color. This is a preparation step
to implement lockless allocation path when there is no free objects in
From: Joonsoo Kim
This is a preparation step to implement lockless allocation path when
there is no free objects in kmem_cache. What we'd like to do here is
to refill cpu cache without holding a node lock. To accomplish this
purpose, refill should be done after new slab
From: Joonsoo Kim
Currently, cache_grow() assumes that allocated page's nodeid would be
same with parameter nodeid which is used for allocation request. If
we discard this assumption, we can handle fallback_alloc() case
gracefully. So, this patch makes cache_grow() handle
From: Joonsoo Kim
To check whther free objects exist or not precisely, we need to grab
a lock. But, accuracy isn't that important because race window would
be even small and if there is too much free object, cache reaper would
reap it. So, this patch makes the check for
From: Joonsoo Kim
This is a preparation step to implement lockless allocation path when
there is no free objects in kmem_cache. What we'd like to do here is
to refill cpu cache without holding a node lock. To accomplish this
purpose, refill should be done after new slab allocation but before
From: Joonsoo Kim
Currently, cache_grow() assumes that allocated page's nodeid would be
same with parameter nodeid which is used for allocation request. If
we discard this assumption, we can handle fallback_alloc() case
gracefully. So, this patch makes cache_grow() handle the page allocated
on
From: Joonsoo Kim
To check whther free objects exist or not precisely, we need to grab
a lock. But, accuracy isn't that important because race window would
be even small and if there is too much free object, cache reaper would
reap it. So, this patch makes the check for free object exisistence
From: Joonsoo Kim
Major kmem_cache metadata in slab subsystem is synchronized with
the slab_mutex. In SLAB, if some of them is changed, node's shared
array cache would be freed and re-populated. If __kmem_cache_shrink()
is called at the same time, it will call
From: Joonsoo Kim
Until now, cache growing makes a free slab on node's slab list and then
we can allocate free objects from it. This necessarily requires
to hold a node lock which is very contended. If we refill cpu cache
before attaching it to node's slab list, we can
From: Joonsoo Kim
Until now, cache growing makes a free slab on node's slab list and then
we can allocate free objects from it. This necessarily requires
to hold a node lock which is very contended. If we refill cpu cache
before attaching it to node's slab list, we can avoid holding a node lock
From: Joonsoo Kim
Major kmem_cache metadata in slab subsystem is synchronized with
the slab_mutex. In SLAB, if some of them is changed, node's shared
array cache would be freed and re-populated. If __kmem_cache_shrink()
is called at the same time, it will call drain_array() with n->shared
From: Joonsoo Kim
Initial attemp to remove BAD_ALIEN_MAGIC is once reverted by
'commit edcad2509550 ("Revert "slab: remove BAD_ALIEN_MAGIC"")'
because it causes a problem on m68k which has many node
but !CONFIG_NUMA. In this case, although alien cache isn't used
at all
From: Joonsoo Kim
Initial attemp to remove BAD_ALIEN_MAGIC is once reverted by
'commit edcad2509550 ("Revert "slab: remove BAD_ALIEN_MAGIC"")'
because it causes a problem on m68k which has many node
but !CONFIG_NUMA. In this case, although alien cache isn't used
at all but to cope with some
From: Joonsoo Kim
slabs_tofree() implies freeing all free slab. We can do it with
just providing INT_MAX.
Signed-off-by: Joonsoo Kim
---
mm/slab.c | 12 +++-
1 file changed, 3 insertions(+), 9 deletions(-)
diff --git a/mm/slab.c
Hi Soren,
> -Original Message-
> From: Sören Brinkmann [mailto:soren.brinkm...@xilinx.com]
> Sent: Monday, March 28, 2016 12:58 AM
> To: Appana Durga Kedareswara Rao
> Cc: robh...@kernel.org; pawel.m...@arm.com; mark.rutl...@arm.com;
> ijc+devicet...@hellion.org.uk; ga...@codeaurora.org;
From: Joonsoo Kim
While processing concurrent allocation, SLAB could be contended
a lot because it did a lots of work with holding a lock. This
patchset try to reduce the number of critical section to reduce
lock contention. Major changes are lockless decision to allocate
From: Joonsoo Kim
While processing concurrent allocation, SLAB could be contended
a lot because it did a lots of work with holding a lock. This
patchset try to reduce the number of critical section to reduce
lock contention. Major changes are lockless decision to allocate
more slab and lockless
Hi Soren,
> -Original Message-
> From: Sören Brinkmann [mailto:soren.brinkm...@xilinx.com]
> Sent: Monday, March 28, 2016 12:58 AM
> To: Appana Durga Kedareswara Rao
> Cc: robh...@kernel.org; pawel.m...@arm.com; mark.rutl...@arm.com;
> ijc+devicet...@hellion.org.uk; ga...@codeaurora.org;
From: Joonsoo Kim
slabs_tofree() implies freeing all free slab. We can do it with
just providing INT_MAX.
Signed-off-by: Joonsoo Kim
---
mm/slab.c | 12 +++-
1 file changed, 3 insertions(+), 9 deletions(-)
diff --git a/mm/slab.c b/mm/slab.c
index a5a205b..ba2eacf 100644
---
From: Joonsoo Kim
It can be reused on other place, so factor out it. Following
patch will use it.
Signed-off-by: Joonsoo Kim
---
mm/slab.c | 68 ---
1 file changed, 39 insertions(+), 29
From: Joonsoo Kim
It can be reused on other place, so factor out it. Following
patch will use it.
Signed-off-by: Joonsoo Kim
---
mm/slab.c | 68 ---
1 file changed, 39 insertions(+), 29 deletions(-)
diff --git a/mm/slab.c
Hello Krzysztof,
On 03/28/2016 12:28 AM, Krzysztof Kozlowski wrote:
> On 25.03.2016 12:15, Javier Martinez Canillas wrote:
>>>
>>> How about doing the same for multi_v7?
>>>
>>
>> I didn't consider multi_v7 because media drivers aren't necessary for booting
>> the boards and so it could increase
Hello Krzysztof,
On 03/28/2016 12:28 AM, Krzysztof Kozlowski wrote:
> On 25.03.2016 12:15, Javier Martinez Canillas wrote:
>>>
>>> How about doing the same for multi_v7?
>>>
>>
>> I didn't consider multi_v7 because media drivers aren't necessary for booting
>> the boards and so it could increase
Hello Andrew,
On Mon, Mar 21, 2016 at 03:30:49PM +0900, Minchan Kim wrote:
> Recently, I got many reports about perfermance degradation
> in embedded system(Android mobile phone, webOS TV and so on)
> and failed to fork easily.
>
> The problem was fragmentation caused by zram and GPU driver
>
Hello Andrew,
On Mon, Mar 21, 2016 at 03:30:49PM +0900, Minchan Kim wrote:
> Recently, I got many reports about perfermance degradation
> in embedded system(Android mobile phone, webOS TV and so on)
> and failed to fork easily.
>
> The problem was fragmentation caused by zram and GPU driver
>
Hi,
arm:collie_defconfig is broken since commit ff2b135922 ("gpio: make the gpiochip a
real device").
Test is quite simple:
Build arm:collie_defconfig, run with
qemu-system-arm -M collie -kernel arch/arm/boot/zImage --append
"console=ttySA1" -monitor null -nographic
Prior to the
Hi,
arm:collie_defconfig is broken since commit ff2b135922 ("gpio: make the gpiochip a
real device").
Test is quite simple:
Build arm:collie_defconfig, run with
qemu-system-arm -M collie -kernel arch/arm/boot/zImage --append
"console=ttySA1" -monitor null -nographic
Prior to the
This patch adds support for Broadcom NS2 SATA3 PHY in existing
Broadcom SATA3 PHY driver.
Signed-off-by: Anup Patel
---
drivers/phy/phy-brcm-sata.c | 238 +---
1 file changed, 200 insertions(+), 38 deletions(-)
diff --git
This patch adds support for Broadcom NS2 SATA3 PHY in existing
Broadcom SATA3 PHY driver.
Signed-off-by: Anup Patel
---
drivers/phy/phy-brcm-sata.c | 238 +---
1 file changed, 200 insertions(+), 38 deletions(-)
diff --git a/drivers/phy/phy-brcm-sata.c
Currently, we have a common SATA3 PHY driver for all Broadcom
STB SoCs. This driver can be extended and re-used for Broadcom
iProc SoCs having same SATA3 PHY.
This patch renames existing Broadcom STB SATA3 PHY driver to
common Broadcom SATA3 PHY driver to share this PHY driver across
Broadcom
This patch:
1. Renames DT bindings document of Broadcom STB SATA3 PHY driver to
common Broadcom SATA3 PHY driver bindings document
2. Adds bindings info for NS2 SATA3 PHY
Signed-off-by: Anup Patel
Acked-by: Rob Herring
---
The Broadcom iProc SoCs have AHCI compliant SATA controller. This
patch adds common compatible string for AHCI SATA controller on
iProc SoCs.
Signed-off-by: Anup Patel
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/ata/ahci-platform.txt |
We have one dual-port SATA3 AHCI controller present in
NS2 SoC.
This patch enables SATA3 AHCI controller and SATA3 PHY
for NS2 SoC in NS2 DT.
Signed-off-by: Anup Patel
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
---
The Broadcom iProc SoCs have AHCI compliant SATA controller. This
patch adds common compatible string for AHCI SATA controller on
iProc SoCs.
Signed-off-by: Anup Patel
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/ata/ahci-platform.txt | 1 +
1 file changed, 1 insertion(+)
diff
We have one dual-port SATA3 AHCI controller present in
NS2 SoC.
This patch enables SATA3 AHCI controller and SATA3 PHY
for NS2 SoC in NS2 DT.
Signed-off-by: Anup Patel
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
---
arch/arm64/boot/dts/broadcom/ns2-svk.dts | 12 +
Currently, we have a common SATA3 PHY driver for all Broadcom
STB SoCs. This driver can be extended and re-used for Broadcom
iProc SoCs having same SATA3 PHY.
This patch renames existing Broadcom STB SATA3 PHY driver to
common Broadcom SATA3 PHY driver to share this PHY driver across
Broadcom
This patch:
1. Renames DT bindings document of Broadcom STB SATA3 PHY driver to
common Broadcom SATA3 PHY driver bindings document
2. Adds bindings info for NS2 SATA3 PHY
Signed-off-by: Anup Patel
Acked-by: Rob Herring
---
.../phy/{brcm,brcmstb-sata-phy.txt => brcm-sata-phy.txt} | 15
The Broadcom NS2 SoC has a AHCI compliant SATA3 controller with
two ports.
This patchset adds common Broadcom SATA3 PHY driver and related
DT bindings document. It also adds appropriate DT nodes in NS2 DT.
The patchset is based on v4.6-rc1 tag and is available in branch
ns2_sata3_v2 of
The Broadcom NS2 SoC has a AHCI compliant SATA3 controller with
two ports.
This patchset adds common Broadcom SATA3 PHY driver and related
DT bindings document. It also adds appropriate DT nodes in NS2 DT.
The patchset is based on v4.6-rc1 tag and is available in branch
ns2_sata3_v2 of
On Wed, Mar 23, 2016 at 01:45:34PM +0900, Joonsoo Kim wrote:
> On Tue, Mar 22, 2016 at 11:06:29PM +0900, Minchan Kim wrote:
> > On Tue, Mar 22, 2016 at 05:20:08PM +0900, Joonsoo Kim wrote:
> > > 2016-03-22 17:00 GMT+09:00 Minchan Kim :
> > > > On Tue, Mar 22, 2016 at 02:08:59PM
On Wed, Mar 23, 2016 at 01:45:34PM +0900, Joonsoo Kim wrote:
> On Tue, Mar 22, 2016 at 11:06:29PM +0900, Minchan Kim wrote:
> > On Tue, Mar 22, 2016 at 05:20:08PM +0900, Joonsoo Kim wrote:
> > > 2016-03-22 17:00 GMT+09:00 Minchan Kim :
> > > > On Tue, Mar 22, 2016 at 02:08:59PM +0900, Joonsoo Kim
On 25 March 2016 at 22:07, Jens Axboe wrote:
> On 03/25/2016 01:32 AM, Baolin Wang wrote:
>>
>> On 24 March 2016 at 22:08, Jens Axboe wrote:
>>>
>>> On 03/24/2016 05:54 AM, Baolin Wang wrote:
This patch provides some tracepoints for the lifecycle of a
On 25 March 2016 at 22:07, Jens Axboe wrote:
> On 03/25/2016 01:32 AM, Baolin Wang wrote:
>>
>> On 24 March 2016 at 22:08, Jens Axboe wrote:
>>>
>>> On 03/24/2016 05:54 AM, Baolin Wang wrote:
This patch provides some tracepoints for the lifecycle of a request from
fetching to
the dgnc_offset_table has a same value with (1 << port).
So I tried to replace dgnc_offset_table array with 1 << port.
And also there are redundant assignments(tmp and current_port)
inside while loop for checking uart port, and remove them.
Signed-off-by: Daeseok Youn
---
the dgnc_offset_table has a same value with (1 << port).
So I tried to replace dgnc_offset_table array with 1 << port.
And also there are redundant assignments(tmp and current_port)
inside while loop for checking uart port, and remove them.
Signed-off-by: Daeseok Youn
---
V2: clean up useless
* Balbir Singh [2016-03-26 18:11:22]:
> On Fri, Mar 25, 2016 at 3:37 AM, Kamalesh Babulal
> wrote:
> > * Michael Ellerman [2016-03-24 22:04:00]:
> >
> >> Not for merging.
> >>
> >
> > Hi Michael,
> >
> > Loading the
* Balbir Singh [2016-03-26 18:11:22]:
> On Fri, Mar 25, 2016 at 3:37 AM, Kamalesh Babulal
> wrote:
> > * Michael Ellerman [2016-03-24 22:04:00]:
> >
> >> Not for merging.
> >>
> >
> > Hi Michael,
> >
> > Loading the livepatch sample module, trigger following warning
> >
>
> The #if
On 25.03.2016 12:15, Javier Martinez Canillas wrote:
>>
>> How about doing the same for multi_v7?
>>
>
> I didn't consider multi_v7 because media drivers aren't necessary for booting
> the boards and so it could increase build times for not real benefits in most
> machines. But I can enable it in
On 25.03.2016 12:15, Javier Martinez Canillas wrote:
>>
>> How about doing the same for multi_v7?
>>
>
> I didn't consider multi_v7 because media drivers aren't necessary for booting
> the boards and so it could increase build times for not real benefits in most
> machines. But I can enable it in
Hi All,
On Mon, Mar 21, 2016 at 4:34 AM, Colin King wrote:
> From: Colin Ian King
>
> retry_limit has never been used during the life of this driver, so
> we may as well remove it as it is redundant.
>
> Signed-off-by: Colin Ian King
Hi All,
On Mon, Mar 21, 2016 at 4:34 AM, Colin King wrote:
> From: Colin Ian King
>
> retry_limit has never been used during the life of this driver, so
> we may as well remove it as it is redundant.
>
> Signed-off-by: Colin Ian King
Looks right to me.
Reviewed-by: Julian Calaby
> ---
>
Hi All,
On Sat, Mar 26, 2016 at 5:24 PM, Bhumika Goyal wrote:
> The functions rtw_enqueue_recvbuf23a and rtw_enqueue_recvbuf23a_to_head
> are never used anywhere in the kernel. So, remove their definition and
> prototype.
> Grepped to find occurences.
>
> Signed-off-by:
The buck9 regulator of S2MPS11 PMIC had incorrect vsel_mask (0xff
instead of 0x1f) thus reading entire register as buck9's voltage. This
effectively caused regulator core to interpret values as higher voltages
than they were and then to set real voltage much lower than intended.
The buck9
Hi All,
On Sat, Mar 26, 2016 at 5:24 PM, Bhumika Goyal wrote:
> The functions rtw_enqueue_recvbuf23a and rtw_enqueue_recvbuf23a_to_head
> are never used anywhere in the kernel. So, remove their definition and
> prototype.
> Grepped to find occurences.
>
> Signed-off-by: Bhumika Goyal
Looks
The buck9 regulator of S2MPS11 PMIC had incorrect vsel_mask (0xff
instead of 0x1f) thus reading entire register as buck9's voltage. This
effectively caused regulator core to interpret values as higher voltages
than they were and then to set real voltage much lower than intended.
The buck9
Hi All,
On Sat, Mar 26, 2016 at 5:14 PM, Bhumika Goyal wrote:
> The functions rtw_get_oper_bw23a and rtw_get_oper_ch23aoffset are never
> used anywhere in the kernel. So, remove their definition and prototype.
> Grepped to find occurences.
>
> Signed-off-by: Bhumika Goyal
Hi All,
On Sat, Mar 26, 2016 at 5:14 PM, Bhumika Goyal wrote:
> The functions rtw_get_oper_bw23a and rtw_get_oper_ch23aoffset are never
> used anywhere in the kernel. So, remove their definition and prototype.
> Grepped to find occurences.
>
> Signed-off-by: Bhumika Goyal
Looks right to me.
1 - 100 of 578 matches
Mail list logo