The J-Core project (j-core.org) produces open source cpu and SoC
peripheral cores synthesizable as FPGA bitstreams or ASICs.
Signed-off-by: Rich Felker
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git
The J-Core project (j-core.org) produces open source cpu and SoC
peripheral cores synthesizable as FPGA bitstreams or ASICs.
Signed-off-by: Rich Felker
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git
Signed-off-by: Rich Felker
---
My previous post of the patch series accidentally omitted omitted
Cc'ing of subsystem maintainers for the necessary clocksource,
irqchip, and spi drivers. Please ack if this looks ok because I want
to get it merged as part of the arch/sh pull
Signed-off-by: Rich Felker
---
My previous post of the patch series accidentally omitted omitted
Cc'ing of subsystem maintainers for the necessary clocksource,
irqchip, and spi drivers. Please ack if this looks ok because I want
to get it merged as part of the arch/sh pull
Signed-off-by: Rich Felker
---
My previous post of the patch series accidentally omitted omitted
Cc'ing of subsystem maintainers for the necessary clocksource,
irqchip, and spi drivers. Please ack if this looks ok because I want
to get it merged as part of the arch/sh pull request for 4.7.
Signed-off-by: Rich Felker
---
My previous post of the patch series accidentally omitted omitted
Cc'ing of subsystem maintainers for the necessary clocksource,
irqchip, and spi drivers. Please ack if this looks ok because I want
to get it merged as part of the arch/sh pull request for 4.7.
Signed-off-by: Rich Felker
---
My previous post of the patch series accidentally omitted omitted
Cc'ing of subsystem maintainers for the necessary clocksource,
irqchip, and spi drivers. Please ack if this looks ok because I want
to get it merged as part of the arch/sh pull
Signed-off-by: Rich Felker
---
My previous post of the patch series accidentally omitted omitted
Cc'ing of subsystem maintainers for the necessary clocksource,
irqchip, and spi drivers. Please ack if this looks ok because I want
to get it merged as part of the arch/sh pull request for 4.7.
The following patchset adds support for the J-core J2, an open-source
VHDL reimplementation of the SH-2 ISA, and drivers for the associated
SoC devices (interrupt controller, clocksource, and SPI).
As arch/sh co-maintainer my intent is to have this merged for 4.7, but
I realized my previous post
Signed-off-by: Rich Felker
---
.../bindings/interrupt-controller/jcore,aic.txt| 28 ++
1 file changed, 28 insertions(+)
create mode 100644
Documentation/devicetree/bindings/interrupt-controller/jcore,aic.txt
diff --git
Signed-off-by: Rich Felker
---
arch/sh/boot/dts/j2_mimas_v2.dts | 87
1 file changed, 87 insertions(+)
create mode 100755 arch/sh/boot/dts/j2_mimas_v2.dts
diff --git a/arch/sh/boot/dts/j2_mimas_v2.dts b/arch/sh/boot/dts/j2_mimas_v2.dts
Signed-off-by: Rich Felker
---
.../bindings/interrupt-controller/jcore,aic.txt| 28 ++
1 file changed, 28 insertions(+)
create mode 100644
Documentation/devicetree/bindings/interrupt-controller/jcore,aic.txt
diff --git
Signed-off-by: Rich Felker
---
arch/sh/boot/dts/j2_mimas_v2.dts | 87
1 file changed, 87 insertions(+)
create mode 100755 arch/sh/boot/dts/j2_mimas_v2.dts
diff --git a/arch/sh/boot/dts/j2_mimas_v2.dts b/arch/sh/boot/dts/j2_mimas_v2.dts
new file mode
The following patchset adds support for the J-core J2, an open-source
VHDL reimplementation of the SH-2 ISA, and drivers for the associated
SoC devices (interrupt controller, clocksource, and SPI).
As arch/sh co-maintainer my intent is to have this merged for 4.7, but
I realized my previous post
Signed-off-by: Rich Felker
---
.../devicetree/bindings/spi/jcore,spi.txt | 23 ++
1 file changed, 23 insertions(+)
create mode 100644 Documentation/devicetree/bindings/spi/jcore,spi.txt
diff --git
Signed-off-by: Rich Felker
---
This revision of the patch is less invasive than the previous one,
moving J2-specific cache init from arch/sh/kernel/cpu/init.c to
arch/sh/kernel/cpu/sh2/probe.c. Unnecessary variable cpu-offset for
CCR register has also been removed.
Signed-off-by: Rich Felker
---
.../devicetree/bindings/timer/jcore,pit.txt| 28 ++
1 file changed, 28 insertions(+)
create mode 100644 Documentation/devicetree/bindings/timer/jcore,pit.txt
diff --git
Signed-off-by: Rich Felker
---
Documentation/devicetree/bindings/jcore/cpus.txt | 91
1 file changed, 91 insertions(+)
create mode 100644 Documentation/devicetree/bindings/jcore/cpus.txt
diff --git a/Documentation/devicetree/bindings/jcore/cpus.txt
Signed-off-by: Rich Felker
---
.../devicetree/bindings/spi/jcore,spi.txt | 23 ++
1 file changed, 23 insertions(+)
create mode 100644 Documentation/devicetree/bindings/spi/jcore,spi.txt
diff --git a/Documentation/devicetree/bindings/spi/jcore,spi.txt
Signed-off-by: Rich Felker
---
This revision of the patch is less invasive than the previous one,
moving J2-specific cache init from arch/sh/kernel/cpu/init.c to
arch/sh/kernel/cpu/sh2/probe.c. Unnecessary variable cpu-offset for
CCR register has also been removed.
arch/sh/Kconfig
Signed-off-by: Rich Felker
---
.../devicetree/bindings/timer/jcore,pit.txt| 28 ++
1 file changed, 28 insertions(+)
create mode 100644 Documentation/devicetree/bindings/timer/jcore,pit.txt
diff --git a/Documentation/devicetree/bindings/timer/jcore,pit.txt
Signed-off-by: Rich Felker
---
Documentation/devicetree/bindings/jcore/cpus.txt | 91
1 file changed, 91 insertions(+)
create mode 100644 Documentation/devicetree/bindings/jcore/cpus.txt
diff --git a/Documentation/devicetree/bindings/jcore/cpus.txt
On Thu, 2016-05-19 at 17:43 -0400, Rik van Riel wrote:
> On Wed, 2016-05-18 at 07:51 +0200, Mike Galbraith wrote:
> > On Mon, 2016-05-09 at 12:48 +0200, Peter Zijlstra wrote:
> > > Hai,
> >
> > (got some of the frozen variety handy?:)
> >
> > > here be a semi coherent patch series for the recent
This defconfig is intended not to be specific to a particular board;
it enables drivers for all currently-supported hardware, and should be
updated to include additional drivers as they are added.
Signed-off-by: Rich Felker
---
arch/sh/configs/j2_defconfig | 38
On Thu, 2016-05-19 at 17:43 -0400, Rik van Riel wrote:
> On Wed, 2016-05-18 at 07:51 +0200, Mike Galbraith wrote:
> > On Mon, 2016-05-09 at 12:48 +0200, Peter Zijlstra wrote:
> > > Hai,
> >
> > (got some of the frozen variety handy?:)
> >
> > > here be a semi coherent patch series for the recent
This defconfig is intended not to be specific to a particular board;
it enables drivers for all currently-supported hardware, and should be
updated to include additional drivers as they are added.
Signed-off-by: Rich Felker
---
arch/sh/configs/j2_defconfig | 38
On Fri, May 20, 2016 at 10:26 AM, Jeremy Kerr wrote:
> Hi Ming,
>
>> Not sure this one is needed for stable because it justs dumps
>> a warning, and not set a valid period to ops->cur_blink_jiffies.
>>
>> So I guess other fix patch is still required for the soft lockup
>> issue,
On Fri, May 20, 2016 at 10:26 AM, Jeremy Kerr wrote:
> Hi Ming,
>
>> Not sure this one is needed for stable because it justs dumps
>> a warning, and not set a valid period to ops->cur_blink_jiffies.
>>
>> So I guess other fix patch is still required for the soft lockup
>> issue, right?
>
> The
On 05/10/2016 06:09 PM, Shawn Lin wrote:
> Controllers use data strobe line to latch data from devices
> under hs400 mode, but not for cmd line. So since emmc 5.1, JEDEC
> introduces enhanced strobe mode for latching cmd response from
> emmc devices to host controllers. This new feature is
On 05/10/2016 06:09 PM, Shawn Lin wrote:
> Controllers use data strobe line to latch data from devices
> under hs400 mode, but not for cmd line. So since emmc 5.1, JEDEC
> introduces enhanced strobe mode for latching cmd response from
> emmc devices to host controllers. This new feature is
On Thu, May 19, 2016 at 07:48:18AM -0500, Rob Herring wrote:
>On Thu, May 19, 2016 at 6:19 AM, Gavin Shan wrote:
>> On Wed, May 18, 2016 at 08:51:59PM -0500, Rob Herring wrote:
>>>On Wed, May 18, 2016 at 7:23 PM, Rob Herring wrote:
On Wed, May 18,
On Thu, May 19, 2016 at 07:48:18AM -0500, Rob Herring wrote:
>On Thu, May 19, 2016 at 6:19 AM, Gavin Shan wrote:
>> On Wed, May 18, 2016 at 08:51:59PM -0500, Rob Herring wrote:
>>>On Wed, May 18, 2016 at 7:23 PM, Rob Herring wrote:
On Wed, May 18, 2016 at 4:26 PM, Rhyland Klein wrote:
2016-05-20 2:18 GMT+09:00 Shi, Yang :
> On 5/18/2016 5:28 PM, Joonsoo Kim wrote:
>>
>> Vlastiml, thanks for ccing me on original bug report.
>>
>> On Wed, May 18, 2016 at 03:23:45PM -0700, Yang Shi wrote:
>>>
>>> When enabling the below kernel configs:
>>>
>>>
2016-05-20 2:18 GMT+09:00 Shi, Yang :
> On 5/18/2016 5:28 PM, Joonsoo Kim wrote:
>>
>> Vlastiml, thanks for ccing me on original bug report.
>>
>> On Wed, May 18, 2016 at 03:23:45PM -0700, Yang Shi wrote:
>>>
>>> When enabling the below kernel configs:
>>>
>>> CONFIG_DEFERRED_STRUCT_PAGE_INIT
>>>
Hi Andrew,
On Thu, 19 May 2016 18:02:16 -0700 a...@linux-foundation.org wrote:
>
> The mm-of-the-moment snapshot 2016-05-19-18-01 has been uploaded to
>
>http://www.ozlabs.org/~akpm/mmotm/
.
.
> mm-page_alloc-defer-debugging-checks-of-pages-allocated-from-the-pcp.patch
>
Hi Andrew,
On Thu, 19 May 2016 18:02:16 -0700 a...@linux-foundation.org wrote:
>
> The mm-of-the-moment snapshot 2016-05-19-18-01 has been uploaded to
>
>http://www.ozlabs.org/~akpm/mmotm/
.
.
> mm-page_alloc-defer-debugging-checks-of-pages-allocated-from-the-pcp.patch
>
On Wed, May 18, 2016 at 8:00 AM, Crestez Dan Leonard
wrote:
> Signed-off-by: Crestez Dan Leonard
> ---
> drivers/iio/imu/inv_mpu6050/inv_mpu_core.c | 47
> ++
> drivers/iio/imu/inv_mpu6050/inv_mpu_i2c.c | 5
On Wed, May 18, 2016 at 8:00 AM, Crestez Dan Leonard
wrote:
> Signed-off-by: Crestez Dan Leonard
> ---
> drivers/iio/imu/inv_mpu6050/inv_mpu_core.c | 47
> ++
> drivers/iio/imu/inv_mpu6050/inv_mpu_i2c.c | 5
> drivers/iio/imu/inv_mpu6050/inv_mpu_iio.h | 1 +
2016-05-19 23:18 GMT+08:00 Dan Streetman :
> Change the return type of zs_pool_stat_create() to void, and
> remove the logic to abort pool creation if the stat debugfs
> dir/file could not be created.
>
> The debugfs stat file is for debugging/information only, and doesn't
>
2016-05-19 23:18 GMT+08:00 Dan Streetman :
> Change the return type of zs_pool_stat_create() to void, and
> remove the logic to abort pool creation if the stat debugfs
> dir/file could not be created.
>
> The debugfs stat file is for debugging/information only, and doesn't
> affect operation of
Hi Greg,
Today's linux-next merge of the tty tree got a conflict in:
include/uapi/linux/serial_core.h
between commits:
157b9394709e ("serial: pic32_uart: Add PIC32 UART driver")
07b75260ebc2 ("Merge branch 'upstream' of
git://git.linux-mips.org/pub/scm/ralf/upstream-linus")
from Linus'
Hi Greg,
Today's linux-next merge of the tty tree got a conflict in:
include/uapi/linux/serial_core.h
between commits:
157b9394709e ("serial: pic32_uart: Add PIC32 UART driver")
07b75260ebc2 ("Merge branch 'upstream' of
git://git.linux-mips.org/pub/scm/ralf/upstream-linus")
from Linus'
Hi Ming,
> Not sure this one is needed for stable because it justs dumps
> a warning, and not set a valid period to ops->cur_blink_jiffies.
>
> So I guess other fix patch is still required for the soft lockup
> issue, right?
The main thing is that we don't set cur_blink_jiffies to the < 50ms
Hi Ming,
> Not sure this one is needed for stable because it justs dumps
> a warning, and not set a valid period to ops->cur_blink_jiffies.
>
> So I guess other fix patch is still required for the soft lockup
> issue, right?
The main thing is that we don't set cur_blink_jiffies to the < 50ms
On 20-05-16, 03:41, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Loops over online CPUs in cpufreq_stats_init() and cpufreq_stats_exit()
> should be carried out with CPU offline/online locked or races are
> possible otherwise, so make that happen.
>
>
On 20-05-16, 03:41, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Loops over online CPUs in cpufreq_stats_init() and cpufreq_stats_exit()
> should be carried out with CPU offline/online locked or races are
> possible otherwise, so make that happen.
>
> Signed-off-by: Rafael J. Wysocki
> "Julia" == Julia Lawall writes:
Julia> firmare -> firmware
Applied to 4.8/scsi-queue.
--
Martin K. Petersen Oracle Linux Engineering
> "Julia" == Julia Lawall writes:
Julia> firmare -> firmware
Applied to 4.8/scsi-queue.
--
Martin K. Petersen Oracle Linux Engineering
Hi,
I mounted overlayfs at /
My cat /proc/mounts looks like the following.
# cat /proc/mounts
/dev/root / squashfs ro,seclabel,relatime 0 0
..
overlayfs / overlay
rw,relatime,lowerdir=/,upperdir=/cache/upper,workdir=/cache/working 0
0
The original blockdevice at fs root is squashfs formatted so
Hi,
I mounted overlayfs at /
My cat /proc/mounts looks like the following.
# cat /proc/mounts
/dev/root / squashfs ro,seclabel,relatime 0 0
..
overlayfs / overlay
rw,relatime,lowerdir=/,upperdir=/cache/upper,workdir=/cache/working 0
0
The original blockdevice at fs root is squashfs formatted so
Shawn,
On Thu, May 19, 2016 at 6:48 PM, Shawn Lin wrote:
>>> #define EXT_CSD_BUS_WIDTH_10 /* Card is in 1 bit mode */
>>> #define EXT_CSD_BUS_WIDTH_41 /* Card is in 4 bit mode */
>>> #define EXT_CSD_BUS_WIDTH_82 /* Card is in 8 bit
Shawn,
On Thu, May 19, 2016 at 6:48 PM, Shawn Lin wrote:
>>> #define EXT_CSD_BUS_WIDTH_10 /* Card is in 1 bit mode */
>>> #define EXT_CSD_BUS_WIDTH_41 /* Card is in 4 bit mode */
>>> #define EXT_CSD_BUS_WIDTH_82 /* Card is in 8 bit mode */
>>> #define
On Fri, May 20, 2016 at 6:31 AM, Scot Doyle wrote:
> Two systems are locking on boot [1] because ops->cur_blink_jiffies
> is set to zero from vc->vc_cur_blink_ms.
>
> Ignore such invalid intervals and log a warning.
>
> [1] https://bugs.launchpad.net/bugs/1574814
>
>
On Fri, May 20, 2016 at 6:31 AM, Scot Doyle wrote:
> Two systems are locking on boot [1] because ops->cur_blink_jiffies
> is set to zero from vc->vc_cur_blink_ms.
>
> Ignore such invalid intervals and log a warning.
>
> [1] https://bugs.launchpad.net/bugs/1574814
>
> Suggested-by: David Daney
>
2016-05-20 5:20 GMT+09:00 Thomas Garnier :
> I ran the test given by Joonsoo and it gave me these minimum cycles
> per size across 20 usage:
I can't understand what you did here. Maybe, it's due to my poor Engling.
Please explain more. You did single thread test? Why minimum
2016-05-20 5:20 GMT+09:00 Thomas Garnier :
> I ran the test given by Joonsoo and it gave me these minimum cycles
> per size across 20 usage:
I can't understand what you did here. Maybe, it's due to my poor Engling.
Please explain more. You did single thread test? Why minimum cycles
rather than
On 2016/5/20 2:36, David Matlack wrote:
On Thu, May 19, 2016 at 11:01 AM, David Matlack wrote:
On Thu, May 19, 2016 at 6:27 AM, Wanpeng Li wrote:
From: Wanpeng Li
If an emulated lapic timer will fire soon(in the scope of
On 2016/5/20 2:36, David Matlack wrote:
On Thu, May 19, 2016 at 11:01 AM, David Matlack wrote:
On Thu, May 19, 2016 at 6:27 AM, Wanpeng Li wrote:
From: Wanpeng Li
If an emulated lapic timer will fire soon(in the scope of 10us the
base of dynamic halt-polling, lower-end of message passing
Hi
在 2016-5-20 8:11, Doug Anderson 写道:
Hi,
On Tue, May 10, 2016 at 2:10 AM, Shawn Lin wrote:
Currently sdhci-arasan 5.1 can support enhanced strobe function,
and we now limit it just for "arasan,sdhci-5.1". Add
mmc-hs400-enhanced-strobe in DT to enable the function
Hi
在 2016-5-20 8:11, Doug Anderson 写道:
Hi,
On Tue, May 10, 2016 at 2:10 AM, Shawn Lin wrote:
Currently sdhci-arasan 5.1 can support enhanced strobe function,
and we now limit it just for "arasan,sdhci-5.1". Add
mmc-hs400-enhanced-strobe in DT to enable the function if we'r sure
Hi
在 2016-5-20 8:18, Doug Anderson 写道:
Hi,
On Tue, May 10, 2016 at 2:09 AM, Shawn Lin wrote:
Controllers use data strobe line to latch data from devices
under hs400 mode, but not for cmd line. So since emmc 5.1, JEDEC
introduces enhanced strobe mode for latching cmd
Hi
在 2016-5-20 8:18, Doug Anderson 写道:
Hi,
On Tue, May 10, 2016 at 2:09 AM, Shawn Lin wrote:
Controllers use data strobe line to latch data from devices
under hs400 mode, but not for cmd line. So since emmc 5.1, JEDEC
introduces enhanced strobe mode for latching cmd response from
emmc
On Wed, May 18, 2016 at 03:45:11PM +0300, Roger Quadros wrote:
> On 18/05/16 06:18, Peter Chen wrote:
> > On Mon, May 16, 2016 at 12:51:53PM +0300, Roger Quadros wrote:
> >> On 16/05/16 12:23, Peter Chen wrote:
> >>> On Mon, May 16, 2016 at 11:26:57AM +0300, Roger Quadros wrote:
> Hi,
>
On Wed, May 18, 2016 at 03:45:11PM +0300, Roger Quadros wrote:
> On 18/05/16 06:18, Peter Chen wrote:
> > On Mon, May 16, 2016 at 12:51:53PM +0300, Roger Quadros wrote:
> >> On 16/05/16 12:23, Peter Chen wrote:
> >>> On Mon, May 16, 2016 at 11:26:57AM +0300, Roger Quadros wrote:
> Hi,
>
From: Rafael J. Wysocki
Loops over online CPUs in cpufreq_stats_init() and cpufreq_stats_exit()
should be carried out with CPU offline/online locked or races are
possible otherwise, so make that happen.
Signed-off-by: Rafael J. Wysocki
From: Rafael J. Wysocki
Loops over online CPUs in cpufreq_stats_init() and cpufreq_stats_exit()
should be carried out with CPU offline/online locked or races are
possible otherwise, so make that happen.
Signed-off-by: Rafael J. Wysocki
---
v1 -> v2: On a second thought, add the policy
On 2016/5/20 1:45, Vlastimil Babka wrote:
> On 19.5.2016 19:23, Hugh Dickins wrote:
>> On Thu, 19 May 2016, Vlastimil Babka wrote:
>>> On 05/19/2016 02:11 PM, Vlastimil Babka wrote:
On 05/19/2016 01:58 PM, Chen Feng wrote:
> While testing the kcompactd in my platform 3G MEM only DMA
On 2016/5/20 1:45, Vlastimil Babka wrote:
> On 19.5.2016 19:23, Hugh Dickins wrote:
>> On Thu, 19 May 2016, Vlastimil Babka wrote:
>>> On 05/19/2016 02:11 PM, Vlastimil Babka wrote:
On 05/19/2016 01:58 PM, Chen Feng wrote:
> While testing the kcompactd in my platform 3G MEM only DMA
Forking new thread because my comment is not related to this patch's
purpose but found a thing during reading this patch.
On Tue, Apr 26, 2016 at 04:04:30PM +0200, Michal Hocko wrote:
> From: Michal Hocko
>
> Tetsuo has properly noted that mmput slow path might get blocked
From: Rafael J. Wysocki
Loops over online CPUs in cpufreq_stats_init() and cpufreq_stats_exit()
should be carried out with CPU offline/online locked or races are
possible otherwise, so make that happen.
Signed-off-by: Rafael J. Wysocki
Forking new thread because my comment is not related to this patch's
purpose but found a thing during reading this patch.
On Tue, Apr 26, 2016 at 04:04:30PM +0200, Michal Hocko wrote:
> From: Michal Hocko
>
> Tetsuo has properly noted that mmput slow path might get blocked waiting
> for another
From: Rafael J. Wysocki
Loops over online CPUs in cpufreq_stats_init() and cpufreq_stats_exit()
should be carried out with CPU offline/online locked or races are
possible otherwise, so make that happen.
Signed-off-by: Rafael J. Wysocki
---
drivers/cpufreq/cpufreq_stats.c | 12 ++--
Hi Scot,
> Two systems are locking on boot [1] because ops->cur_blink_jiffies
> is set to zero from vc->vc_cur_blink_ms.
>
> Ignore such invalid intervals and log a warning.
This prevents a lockup on AST BMC machines, but (as expected) generates
a warning against the fbcon driver, which is a
Hi Scot,
> Two systems are locking on boot [1] because ops->cur_blink_jiffies
> is set to zero from vc->vc_cur_blink_ms.
>
> Ignore such invalid intervals and log a warning.
This prevents a lockup on AST BMC machines, but (as expected) generates
a warning against the fbcon driver, which is a
On Thu, 19 May 2016, Jason Low wrote:
The mutex owner can get read and written to without the wait_lock.
Use WRITE_ONCE when setting and clearing the owner field in order
to avoid optimizations such as store tearing. This avoids
situations where the owner field gets written to with multiple
On Thu, 19 May 2016, Jason Low wrote:
The mutex owner can get read and written to without the wait_lock.
Use WRITE_ONCE when setting and clearing the owner field in order
to avoid optimizations such as store tearing. This avoids
situations where the owner field gets written to with multiple
The mm-of-the-moment snapshot 2016-05-19-18-01 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You
The mm-of-the-moment snapshot 2016-05-19-18-01 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You
On 2016/5/20 1:45, Vlastimil Babka wrote:
> On 19.5.2016 19:23, Hugh Dickins wrote:
>> On Thu, 19 May 2016, Vlastimil Babka wrote:
>>> On 05/19/2016 02:11 PM, Vlastimil Babka wrote:
On 05/19/2016 01:58 PM, Chen Feng wrote:
> While testing the kcompactd in my platform 3G MEM only DMA
On 2016/5/20 1:45, Vlastimil Babka wrote:
> On 19.5.2016 19:23, Hugh Dickins wrote:
>> On Thu, 19 May 2016, Vlastimil Babka wrote:
>>> On 05/19/2016 02:11 PM, Vlastimil Babka wrote:
On 05/19/2016 01:58 PM, Chen Feng wrote:
> While testing the kcompactd in my platform 3G MEM only DMA
On Thu, 19 May 2016 17:50:31 -0700, Greg Kroah-Hartman said:
> On Thu, May 19, 2016 at 05:19:00PM -0400, Valdis Kletnieks wrote:
> > UBSAN throws a complaint:
> >
> > [2.418579] UBSAN: Undefined behaviour in
> > drivers/usb/host/ehci-hub.c:877:47
> > [2.418582] index -1 is out of range
On Thu, 19 May 2016 17:50:31 -0700, Greg Kroah-Hartman said:
> On Thu, May 19, 2016 at 05:19:00PM -0400, Valdis Kletnieks wrote:
> > UBSAN throws a complaint:
> >
> > [2.418579] UBSAN: Undefined behaviour in
> > drivers/usb/host/ehci-hub.c:877:47
> > [2.418582] index -1 is out of range
Hi, Rafael
> From: rjwyso...@gmail.com [mailto:rjwyso...@gmail.com] On Behalf Of
> Rafael J. Wysocki
> Subject: Re: [PATCH v2 0/4] ACPI 2.0: Enable TermList interpretion for table
> loading
>
> On Tue, May 17, 2016 at 2:29 AM, Zheng, Lv wrote:
> > Hi, Rafael
> >
> > Can we
Hi, Rafael
> From: rjwyso...@gmail.com [mailto:rjwyso...@gmail.com] On Behalf Of
> Rafael J. Wysocki
> Subject: Re: [PATCH v2 0/4] ACPI 2.0: Enable TermList interpretion for table
> loading
>
> On Tue, May 17, 2016 at 2:29 AM, Zheng, Lv wrote:
> > Hi, Rafael
> >
> > Can we queue this up in
On Fri, May 20, 2016 at 2:37 AM, Steve Muckle wrote:
> On Fri, May 20, 2016 at 02:24:19AM +0200, Rafael J. Wysocki wrote:
>> On Fri, May 20, 2016 at 1:34 AM, Steve Muckle
>> wrote:
>> > On Thu, May 19, 2016 at 11:15:52PM +0200, Rafael J. Wysocki
On Fri, May 20, 2016 at 2:37 AM, Steve Muckle wrote:
> On Fri, May 20, 2016 at 02:24:19AM +0200, Rafael J. Wysocki wrote:
>> On Fri, May 20, 2016 at 1:34 AM, Steve Muckle
>> wrote:
>> > On Thu, May 19, 2016 at 11:15:52PM +0200, Rafael J. Wysocki wrote:
>> >> But anyway this change again seems
Hi guys ,
I tested kernel 4.6 with the built in microcode method , following
Documentation/x86/early-microcode.txt.
The kernel config[1] has :
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE="intel-ucode/06-1a-05"
CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"
also
CONFIG_MICROCODE=y
Hi guys ,
I tested kernel 4.6 with the built in microcode method , following
Documentation/x86/early-microcode.txt.
The kernel config[1] has :
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE="intel-ucode/06-1a-05"
CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"
also
CONFIG_MICROCODE=y
Hi,
Looks real good now. :)
If there is a next version, feel free to add:
Acked-by: Lv Zheng
Thanks and best regards
-Lv
> From: Aleksey Makarov [mailto:aleksey.maka...@linaro.org]
> Subject: [PATCH v2 2/5] ACPI: table upgrade: refactor function definitions
>
> Refer
Hi,
Looks real good now. :)
If there is a next version, feel free to add:
Acked-by: Lv Zheng
Thanks and best regards
-Lv
> From: Aleksey Makarov [mailto:aleksey.maka...@linaro.org]
> Subject: [PATCH v2 2/5] ACPI: table upgrade: refactor function definitions
>
> Refer initrd_start, initrd_end
On Tue, May 17, 2016 at 10:20:40PM +0800, 廖崇榮 wrote:
> Hi Dmitry,
>
> I want to confirm my thought for your idea to avoid misunderstanding.
> I think you want to encapsulate " BTN_TOOL_FINGER" in the
> [input_mt_report_pointer_emulation] if hover happen.
> Vendor driver only report
On Tue, May 17, 2016 at 10:20:40PM +0800, 廖崇榮 wrote:
> Hi Dmitry,
>
> I want to confirm my thought for your idea to avoid misunderstanding.
> I think you want to encapsulate " BTN_TOOL_FINGER" in the
> [input_mt_report_pointer_emulation] if hover happen.
> Vendor driver only report
On Thu, May 19, 2016 at 05:19:00PM -0400, Valdis Kletnieks wrote:
> UBSAN throws a complaint:
>
> [2.418579] UBSAN: Undefined behaviour in
> drivers/usb/host/ehci-hub.c:877:47
> [2.418582] index -1 is out of range for type 'u32 [1]'
>
> though it's only on the hostpc[] part, not on the
On Thu, May 19, 2016 at 05:19:00PM -0400, Valdis Kletnieks wrote:
> UBSAN throws a complaint:
>
> [2.418579] UBSAN: Undefined behaviour in
> drivers/usb/host/ehci-hub.c:877:47
> [2.418582] index -1 is out of range for type 'u32 [1]'
>
> though it's only on the hostpc[] part, not on the
On Fri, May 20, 2016 at 2:40 AM, Steve Muckle wrote:
> On Fri, May 20, 2016 at 02:37:17AM +0200, Rafael J. Wysocki wrote:
>> Also I think that it would be good to avoid walking the frequency
>> table twice in case we end up wanting to update the frequency after
>> all.
On Fri, May 20, 2016 at 2:40 AM, Steve Muckle wrote:
> On Fri, May 20, 2016 at 02:37:17AM +0200, Rafael J. Wysocki wrote:
>> Also I think that it would be good to avoid walking the frequency
>> table twice in case we end up wanting to update the frequency after
>> all. With the [4/5] we'd do it
On Fri, May 20, 2016 at 02:37:17AM +0200, Rafael J. Wysocki wrote:
> Also I think that it would be good to avoid walking the frequency
> table twice in case we end up wanting to update the frequency after
> all. With the [4/5] we'd do it once in get_next_freq() and then once
> more in
On Fri, May 20, 2016 at 02:37:17AM +0200, Rafael J. Wysocki wrote:
> Also I think that it would be good to avoid walking the frequency
> table twice in case we end up wanting to update the frequency after
> all. With the [4/5] we'd do it once in get_next_freq() and then once
> more in
From: Megha Dey
Currently there are several checkpatch warnings in the sha1_mb.c file:
'WARNING: line over 80 characters' in the sha1_mb.c file. Also, the
syntax of some multi-line comments are not correct. This patch fixes
these issues.
Signed-off-by: Megha Dey
From: Megha Dey
Herbert wants the sha1-mb algorithm to have an async implementation:
https://lkml.org/lkml/2016/4/5/286.
Currently, sha1-mb uses an async interface for the outer algorithm
and a sync interface for the inner algorithm. This patch introduces
a async
101 - 200 of 1438 matches
Mail list logo