Commit-ID: ef0f3ed5a4acfb24740480bf2e50b178724f094d
Gitweb: http://git.kernel.org/tip/ef0f3ed5a4acfb24740480bf2e50b178724f094d
Author: Josh Poimboeuf
AuthorDate: Thu, 21 Jan 2016 16:49:24 -0600
Committer: Ingo Molnar
CommitDate: Wed, 24 Feb 2016
Commit-ID: ef0f3ed5a4acfb24740480bf2e50b178724f094d
Gitweb: http://git.kernel.org/tip/ef0f3ed5a4acfb24740480bf2e50b178724f094d
Author: Josh Poimboeuf
AuthorDate: Thu, 21 Jan 2016 16:49:24 -0600
Committer: Ingo Molnar
CommitDate: Wed, 24 Feb 2016 08:35:43 +0100
x86/asm/power: Create
On 02/24/2016 02:05 AM, Jiri Slaby wrote:
This is the start of the stable review cycle for the 3.12.55 release.
There are 142 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by
On 02/24/2016 02:05 AM, Jiri Slaby wrote:
This is the start of the stable review cycle for the 3.12.55 release.
There are 142 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by
Commit-ID: f66f61919eb38c5f20e8a978cae7ecdede4c23b9
Gitweb: http://git.kernel.org/tip/f66f61919eb38c5f20e8a978cae7ecdede4c23b9
Author: Josh Poimboeuf
AuthorDate: Thu, 21 Jan 2016 16:49:16 -0600
Committer: Ingo Molnar
CommitDate: Wed, 24 Feb 2016
Commit-ID: 68874ac3304ade7ed5ebb12af00d6b9bbbca0a16
Gitweb: http://git.kernel.org/tip/68874ac3304ade7ed5ebb12af00d6b9bbbca0a16
Author: Josh Poimboeuf
AuthorDate: Thu, 21 Jan 2016 16:49:18 -0600
Committer: Ingo Molnar
CommitDate: Wed, 24 Feb 2016
Commit-ID: f66f61919eb38c5f20e8a978cae7ecdede4c23b9
Gitweb: http://git.kernel.org/tip/f66f61919eb38c5f20e8a978cae7ecdede4c23b9
Author: Josh Poimboeuf
AuthorDate: Thu, 21 Jan 2016 16:49:16 -0600
Committer: Ingo Molnar
CommitDate: Wed, 24 Feb 2016 08:35:42 +0100
x86/asm/crypto: Move
Commit-ID: 68874ac3304ade7ed5ebb12af00d6b9bbbca0a16
Gitweb: http://git.kernel.org/tip/68874ac3304ade7ed5ebb12af00d6b9bbbca0a16
Author: Josh Poimboeuf
AuthorDate: Thu, 21 Jan 2016 16:49:18 -0600
Committer: Ingo Molnar
CommitDate: Wed, 24 Feb 2016 08:35:42 +0100
x86/asm/crypto: Don't
Commit-ID: aec4d0e301f17bb143341c82cc44685b8af0b945
Gitweb: http://git.kernel.org/tip/aec4d0e301f17bb143341c82cc44685b8af0b945
Author: Josh Poimboeuf
AuthorDate: Thu, 21 Jan 2016 16:49:17 -0600
Committer: Ingo Molnar
CommitDate: Wed, 24 Feb 2016
Commit-ID: aec4d0e301f17bb143341c82cc44685b8af0b945
Gitweb: http://git.kernel.org/tip/aec4d0e301f17bb143341c82cc44685b8af0b945
Author: Josh Poimboeuf
AuthorDate: Thu, 21 Jan 2016 16:49:17 -0600
Committer: Ingo Molnar
CommitDate: Wed, 24 Feb 2016 08:35:42 +0100
x86/asm/crypto: Simplify
Commit-ID: de642faf48670c3c8eae5899177f786c624f4894
Gitweb: http://git.kernel.org/tip/de642faf48670c3c8eae5899177f786c624f4894
Author: Josh Poimboeuf
AuthorDate: Thu, 21 Jan 2016 16:49:14 -0600
Committer: Ingo Molnar
CommitDate: Wed, 24 Feb 2016
Commit-ID: bb93eb4cd606888f879897e8289d9c1143571feb
Gitweb: http://git.kernel.org/tip/bb93eb4cd606888f879897e8289d9c1143571feb
Author: Josh Poimboeuf
AuthorDate: Thu, 21 Jan 2016 16:49:12 -0600
Committer: Ingo Molnar
CommitDate: Wed, 24 Feb 2016
> Fine with me.
>
> Is there any chance for the set of chipset dependent registers that are safe
> to
> be read when in D3 state to be documented ?
>
I think except registers in PCI configuration, all other registers should be
read in D0 state.
--Please consider the environment before
Commit-ID: 87b240cbe3e51bf070fe2839fecb6450323aaef4
Gitweb: http://git.kernel.org/tip/87b240cbe3e51bf070fe2839fecb6450323aaef4
Author: Josh Poimboeuf
AuthorDate: Thu, 21 Jan 2016 16:49:13 -0600
Committer: Ingo Molnar
CommitDate: Wed, 24 Feb 2016
Commit-ID: 1253cab8a35278c0493a48aa5ab74992f7a849ea
Gitweb: http://git.kernel.org/tip/1253cab8a35278c0493a48aa5ab74992f7a849ea
Author: Josh Poimboeuf
AuthorDate: Thu, 21 Jan 2016 16:49:15 -0600
Committer: Ingo Molnar
CommitDate: Wed, 24 Feb 2016
Commit-ID: de642faf48670c3c8eae5899177f786c624f4894
Gitweb: http://git.kernel.org/tip/de642faf48670c3c8eae5899177f786c624f4894
Author: Josh Poimboeuf
AuthorDate: Thu, 21 Jan 2016 16:49:14 -0600
Committer: Ingo Molnar
CommitDate: Wed, 24 Feb 2016 08:35:42 +0100
x86/amd: Set ELF
Commit-ID: bb93eb4cd606888f879897e8289d9c1143571feb
Gitweb: http://git.kernel.org/tip/bb93eb4cd606888f879897e8289d9c1143571feb
Author: Josh Poimboeuf
AuthorDate: Thu, 21 Jan 2016 16:49:12 -0600
Committer: Ingo Molnar
CommitDate: Wed, 24 Feb 2016 08:35:42 +0100
x86/paravirt: Add stack
> Fine with me.
>
> Is there any chance for the set of chipset dependent registers that are safe
> to
> be read when in D3 state to be documented ?
>
I think except registers in PCI configuration, all other registers should be
read in D0 state.
--Please consider the environment before
Commit-ID: 87b240cbe3e51bf070fe2839fecb6450323aaef4
Gitweb: http://git.kernel.org/tip/87b240cbe3e51bf070fe2839fecb6450323aaef4
Author: Josh Poimboeuf
AuthorDate: Thu, 21 Jan 2016 16:49:13 -0600
Committer: Ingo Molnar
CommitDate: Wed, 24 Feb 2016 08:35:42 +0100
x86/paravirt: Create a
Commit-ID: 1253cab8a35278c0493a48aa5ab74992f7a849ea
Gitweb: http://git.kernel.org/tip/1253cab8a35278c0493a48aa5ab74992f7a849ea
Author: Josh Poimboeuf
AuthorDate: Thu, 21 Jan 2016 16:49:15 -0600
Committer: Ingo Molnar
CommitDate: Wed, 24 Feb 2016 08:35:42 +0100
x86/asm/crypto: Move
Commit-ID: 8be0eb7e0d53bc2dbe6e9ad6e96a2d5b89d148a8
Gitweb: http://git.kernel.org/tip/8be0eb7e0d53bc2dbe6e9ad6e96a2d5b89d148a8
Author: Josh Poimboeuf
AuthorDate: Thu, 21 Jan 2016 16:49:11 -0600
Committer: Ingo Molnar
CommitDate: Wed, 24 Feb 2016
Commit-ID: 0e8e2238b52e5301d1d1d4a298ec5b72ac54c702
Gitweb: http://git.kernel.org/tip/0e8e2238b52e5301d1d1d4a298ec5b72ac54c702
Author: Josh Poimboeuf
AuthorDate: Thu, 21 Jan 2016 16:49:09 -0600
Committer: Ingo Molnar
CommitDate: Wed, 24 Feb 2016
Commit-ID: 9fd216067d75b45eb18d84dc476059de47da07c2
Gitweb: http://git.kernel.org/tip/9fd216067d75b45eb18d84dc476059de47da07c2
Author: Josh Poimboeuf
AuthorDate: Thu, 21 Jan 2016 16:49:10 -0600
Committer: Ingo Molnar
CommitDate: Wed, 24 Feb 2016
Commit-ID: 8be0eb7e0d53bc2dbe6e9ad6e96a2d5b89d148a8
Gitweb: http://git.kernel.org/tip/8be0eb7e0d53bc2dbe6e9ad6e96a2d5b89d148a8
Author: Josh Poimboeuf
AuthorDate: Thu, 21 Jan 2016 16:49:11 -0600
Committer: Ingo Molnar
CommitDate: Wed, 24 Feb 2016 08:35:42 +0100
x86/asm/xen: Create
Commit-ID: 0e8e2238b52e5301d1d1d4a298ec5b72ac54c702
Gitweb: http://git.kernel.org/tip/0e8e2238b52e5301d1d1d4a298ec5b72ac54c702
Author: Josh Poimboeuf
AuthorDate: Thu, 21 Jan 2016 16:49:09 -0600
Committer: Ingo Molnar
CommitDate: Wed, 24 Feb 2016 08:35:41 +0100
x86/xen: Add stack frame
Commit-ID: 9fd216067d75b45eb18d84dc476059de47da07c2
Gitweb: http://git.kernel.org/tip/9fd216067d75b45eb18d84dc476059de47da07c2
Author: Josh Poimboeuf
AuthorDate: Thu, 21 Jan 2016 16:49:10 -0600
Committer: Ingo Molnar
CommitDate: Wed, 24 Feb 2016 08:35:41 +0100
x86/asm/xen: Set ELF
Hi Linus, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm libnvdimm-fixes
...to receive:
1/ Two fixes for compatibility with the ACPI 6.1 specification.
Without these fixes multi-interface DIMMs will fail to be probed, and
address range scrub commands to find
Hi Linus, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm libnvdimm-fixes
...to receive:
1/ Two fixes for compatibility with the ACPI 6.1 specification.
Without these fixes multi-interface DIMMs will fail to be probed, and
address range scrub commands to find
Commit-ID: d1130686f463e6feff19196475c3c15b1923c525
Gitweb: http://git.kernel.org/tip/d1130686f463e6feff19196475c3c15b1923c525
Author: Arnaldo Carvalho de Melo
AuthorDate: Tue, 23 Feb 2016 16:18:37 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: bea2400621836b028d82c3d6a74053921d70dbd7
Gitweb: http://git.kernel.org/tip/bea2400621836b028d82c3d6a74053921d70dbd7
Author: Arnaldo Carvalho de Melo
AuthorDate: Tue, 23 Feb 2016 16:21:04 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: d1130686f463e6feff19196475c3c15b1923c525
Gitweb: http://git.kernel.org/tip/d1130686f463e6feff19196475c3c15b1923c525
Author: Arnaldo Carvalho de Melo
AuthorDate: Tue, 23 Feb 2016 16:18:37 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 23 Feb 2016 16:18:37 -0300
Commit-ID: bea2400621836b028d82c3d6a74053921d70dbd7
Gitweb: http://git.kernel.org/tip/bea2400621836b028d82c3d6a74053921d70dbd7
Author: Arnaldo Carvalho de Melo
AuthorDate: Tue, 23 Feb 2016 16:21:04 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 23 Feb 2016 16:21:04 -0300
Commit-ID: 940db6dcd3f4659303fdf6befe7416adc4d24118
Gitweb: http://git.kernel.org/tip/940db6dcd3f4659303fdf6befe7416adc4d24118
Author: Andi Kleen
AuthorDate: Wed, 17 Feb 2016 14:44:55 -0800
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 23
Commit-ID: 940db6dcd3f4659303fdf6befe7416adc4d24118
Gitweb: http://git.kernel.org/tip/940db6dcd3f4659303fdf6befe7416adc4d24118
Author: Andi Kleen
AuthorDate: Wed, 17 Feb 2016 14:44:55 -0800
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 23 Feb 2016 12:46:16 -0300
perf tools:
Commit-ID: ff7b191583c368612fde88bf3cff6e3f3b0d73d5
Gitweb: http://git.kernel.org/tip/ff7b191583c368612fde88bf3cff6e3f3b0d73d5
Author: Jiri Olsa
AuthorDate: Mon, 15 Feb 2016 09:34:52 +0100
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 23 Feb
Commit-ID: ff7b191583c368612fde88bf3cff6e3f3b0d73d5
Gitweb: http://git.kernel.org/tip/ff7b191583c368612fde88bf3cff6e3f3b0d73d5
Author: Jiri Olsa
AuthorDate: Mon, 15 Feb 2016 09:34:52 +0100
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 23 Feb 2016 12:20:21 -0300
perf script:
This patch improves the error message given by jvmti Makefile
when the alternatives command cannot be found. It now suggests
the user locates the root of their Java installation and pass it
with JDIR=
Signed-off-by: Stephane Eranian
---
tools/perf/jvmti/Makefile | 17
This patch improves the error message given by jvmti Makefile
when the alternatives command cannot be found. It now suggests
the user locates the root of their Java installation and pass it
with JDIR=
Signed-off-by: Stephane Eranian
---
tools/perf/jvmti/Makefile | 17 +
1 file
Hi,
On 02/25/2016 05:01 AM, Olof Johansson wrote:
On Fri, Feb 12, 2016 at 07:20:43AM +0700, Suravee Suthikulpanit wrote:
From: Suravee Suthikulpanit
This is a fix-up patch based on the review comment from
Arnd regarding:
* fix ccn504 address in the node
Hi,
On 02/25/2016 05:01 AM, Olof Johansson wrote:
On Fri, Feb 12, 2016 at 07:20:43AM +0700, Suravee Suthikulpanit wrote:
From: Suravee Suthikulpanit
This is a fix-up patch based on the review comment from
Arnd regarding:
* fix ccn504 address in the node name
* remove kcs
Fail all pending requests after surprise removal of a drive.
Signed-off-by: Vignesh Gunasekaran
Signed-off-by: Selvan Mani
Signed-off-by: Asai Thambi S P
---
drivers/block/mtip32xx/mtip32xx.c | 78
Fail all pending requests after surprise removal of a drive.
Signed-off-by: Vignesh Gunasekaran
Signed-off-by: Selvan Mani
Signed-off-by: Asai Thambi S P
---
drivers/block/mtip32xx/mtip32xx.c | 78
1 files changed, 60 insertions(+), 18 deletions(-)
Added timeout handler. Replaced blk_mq_end_request() with
blk_mq_complete_request() to avoid double completion of a request.
Signed-off-by: Selvan Mani
Signed-off-by: Rajesh Kumar Sambandam
Signed-off-by: Asai Thambi S P
---
Added timeout handler. Replaced blk_mq_end_request() with
blk_mq_complete_request() to avoid double completion of a request.
Signed-off-by: Selvan Mani
Signed-off-by: Rajesh Kumar Sambandam
Signed-off-by: Asai Thambi S P
---
drivers/block/mtip32xx/mtip32xx.c | 95
Allow device initialization to finish gracefully when it is in
FTL rebuild failure state. Also, recover device out of this state
after successfully secure erasing it.
Signed-off-by: Selvan Mani
Signed-off-by: Vignesh Gunasekaran
Signed-off-by: Asai
Hi all,
Changes since 20160224:
The renesas tree gained a conflict against the arm-soc tree.
The mac80211-next tree lost its build failure.
The aio tree still had a build failure so I used the version from
next-20160111.
The akpm-current tree gained a build failure for which I applied a
fix
Allow device initialization to finish gracefully when it is in
FTL rebuild failure state. Also, recover device out of this state
after successfully secure erasing it.
Signed-off-by: Selvan Mani
Signed-off-by: Vignesh Gunasekaran
Signed-off-by: Asai Thambi S P
---
Hi all,
Changes since 20160224:
The renesas tree gained a conflict against the arm-soc tree.
The mac80211-next tree lost its build failure.
The aio tree still had a build failure so I used the version from
next-20160111.
The akpm-current tree gained a build failure for which I applied a
fix
Flush inflight IOs using fsync_bdev() when the device is safely
removed. Also, block further IOs in device open function.
Signed-off-by: Selvan Mani
Signed-off-by: Rajesh Kumar Sambandam
Signed-off-by: Asai Thambi S P
---
Flush inflight IOs using fsync_bdev() when the device is safely
removed. Also, block further IOs in device open function.
Signed-off-by: Selvan Mani
Signed-off-by: Rajesh Kumar Sambandam
Signed-off-by: Asai Thambi S P
---
drivers/block/mtip32xx/mtip32xx.c | 34
Prevent standby immediate command from being issued in remove,
suspend and shutdown paths, while drive is in FTL rebuild process.
Signed-off-by: Selvan Mani
Signed-off-by: Vignesh Gunasekaran
Signed-off-by: Asai Thambi S P
Prevent standby immediate command from being issued in remove,
suspend and shutdown paths, while drive is in FTL rebuild process.
Signed-off-by: Selvan Mani
Signed-off-by: Vignesh Gunasekaran
Signed-off-by: Asai Thambi S P
---
drivers/block/mtip32xx/mtip32xx.c | 20
1
When FTL rebuild is in progress, alloc_disk() initializes the disk
but device node will be created by add_disk() only after successful
completion of FTL rebuild. So, skip deletion of device node in
removal path when FTL rebuild is in progress.
Signed-off-by: Selvan Mani
When FTL rebuild is in progress, alloc_disk() initializes the disk
but device node will be created by add_disk() only after successful
completion of FTL rebuild. So, skip deletion of device node in
removal path when FTL rebuild is in progress.
Signed-off-by: Selvan Mani
Signed-off-by: Asai
Print exact time when an internal command is interrupted.
Signed-off-by: Selvan Mani
Signed-off-by: Rajesh Kumar Sambandam
Signed-off-by: Asai Thambi S P
---
drivers/block/mtip32xx/mtip32xx.c |8 ++--
1 files changed,
Print exact time when an internal command is interrupted.
Signed-off-by: Selvan Mani
Signed-off-by: Rajesh Kumar Sambandam
Signed-off-by: Asai Thambi S P
---
drivers/block/mtip32xx/mtip32xx.c |8 ++--
1 files changed, 6 insertions(+), 2 deletions(-)
diff --git
Remove setting and clearing MTIP_PF_EH_ACTIVE_BIT flag in
mtip_handle_tfe() as they are redundant. Also avoid waking
up service thread from mtip_handle_tfe() because it is
already woken up in case of taskfile error.
Signed-off-by: Selvan Mani
Signed-off-by: Rajesh Kumar
Remove setting and clearing MTIP_PF_EH_ACTIVE_BIT flag in
mtip_handle_tfe() as they are redundant. Also avoid waking
up service thread from mtip_handle_tfe() because it is
already woken up in case of taskfile error.
Signed-off-by: Selvan Mani
Signed-off-by: Rajesh Kumar Sambandam
Hi Jens,
This patchset includes various fixes for mtip32xx driver, tested
on kernel 4.5-rc3.
Selvan Mani (9):
mtip32xx: Fix broken service thread handling
mtip32xx: Remove unwanted code from taskfile error handler
mtip32xx: Print exact time when an internal command is interrupted
Service thread does not detect the need for taskfile error hanlding. Fixed the
flag condition to process taskfile error.
Signed-off-by: Selvan Mani
Signed-off-by: Asai Thambi S P
---
drivers/block/mtip32xx/mtip32xx.c |6 +++---
Hi Jens,
This patchset includes various fixes for mtip32xx driver, tested
on kernel 4.5-rc3.
Selvan Mani (9):
mtip32xx: Fix broken service thread handling
mtip32xx: Remove unwanted code from taskfile error handler
mtip32xx: Print exact time when an internal command is interrupted
Service thread does not detect the need for taskfile error hanlding. Fixed the
flag condition to process taskfile error.
Signed-off-by: Selvan Mani
Signed-off-by: Asai Thambi S P
---
drivers/block/mtip32xx/mtip32xx.c |6 +++---
drivers/block/mtip32xx/mtip32xx.h |5 +
2 files
On Wed, Feb 24, 2016 at 8:28 AM, Ross Green wrote:
> On Wed, Feb 24, 2016 at 7:55 AM, Paul E. McKenney
> wrote:
>> On Tue, Feb 23, 2016 at 08:34:11PM +, Mathieu Desnoyers wrote:
>>> - On Feb 21, 2016, at 1:15 PM, Ross Green
On Wed, Feb 24, 2016 at 8:28 AM, Ross Green wrote:
> On Wed, Feb 24, 2016 at 7:55 AM, Paul E. McKenney
> wrote:
>> On Tue, Feb 23, 2016 at 08:34:11PM +, Mathieu Desnoyers wrote:
>>> - On Feb 21, 2016, at 1:15 PM, Ross Green rgker...@gmail.com wrote:
>>>
>>> > On Sun, Feb 21, 2016 at 4:04
On Wen, Feb 24, 2016 at 04:22AM, Rob Herring wrote:
> -Original Message-
> From: Rob Herring [mailto:r...@kernel.org]
> Sent: Wednesday, February 24, 2016 4:22 AM
> To: Qiang Zhao
> Cc: o...@buserror.net; Yang-Leo Li ; linux-
>
On Wen, Feb 24, 2016 at 04:22AM, Rob Herring wrote:
> -Original Message-
> From: Rob Herring [mailto:r...@kernel.org]
> Sent: Wednesday, February 24, 2016 4:22 AM
> To: Qiang Zhao
> Cc: o...@buserror.net; Yang-Leo Li ; linux-
> ker...@vger.kernel.org; devicet...@vger.kernel.org; linuxppc-
linux-next modulo printk patches
was observed.
next-20160224
git revert 8a30bf8ff5e07a589ad43363b06ea361ad723a0e
2822460a0ea97656ae71b2b4ddac087f79c5876a
b6751672d3ac1d3d876fd5ea7ec579956eee4d6b
set PREEMPT_NONE
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# C
linux-next modulo printk patches
was observed.
next-20160224
git revert 8a30bf8ff5e07a589ad43363b06ea361ad723a0e
2822460a0ea97656ae71b2b4ddac087f79c5876a
b6751672d3ac1d3d876fd5ea7ec579956eee4d6b
set PREEMPT_NONE
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# C
From: Diego Viola
Date: Tue, 23 Feb 2016 12:04:04 -0300
> The JMC260 network card fails to suspend/resume because the call to
> jme_start_irq() was too early, moving the call to jme_start_irq() after
> the call to jme_reset_link() makes it work.
>
> Prior this change
From: Diego Viola
Date: Tue, 23 Feb 2016 12:04:04 -0300
> The JMC260 network card fails to suspend/resume because the call to
> jme_start_irq() was too early, moving the call to jme_start_irq() after
> the call to jme_reset_link() makes it work.
>
> Prior this change suspend/resume would fail
On Thu, Feb 25, 2016 at 1:13 PM, Ross Green wrote:
> On Thu, Feb 25, 2016 at 11:11 AM, Emil Goode wrote:
>> Hello Ross
>>
>> On Wed, Feb 24, 2016 at 04:40:50PM +1100, Ross Green wrote:
>>> On Wed, Feb 17, 2016 at 4:34 PM, Ross Green
On Thu, Feb 25, 2016 at 1:13 PM, Ross Green wrote:
> On Thu, Feb 25, 2016 at 11:11 AM, Emil Goode wrote:
>> Hello Ross
>>
>> On Wed, Feb 24, 2016 at 04:40:50PM +1100, Ross Green wrote:
>>> On Wed, Feb 17, 2016 at 4:34 PM, Ross Green wrote:
>>> > Appreciate your efforts!
>>> >
>>> > Just trying
On 02/23/2016 07:33 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.98 release.
There are 54 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On 02/23/2016 07:33 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.98 release.
There are 54 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
arch/arm/mm/mmu.c:737:37: error: macro "pte_alloc" passed 4 arguments, but
takes just 3
void *(*alloc)(unsigned long sz))
^
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
arch/arm/mm/mmu.c:737:37: error: macro "pte_alloc" passed 4 arguments, but
takes just 3
void *(*alloc)(unsigned long sz))
^
On 25.02.2016 13:19, pankaj.dubey wrote:
> Hi Krzysztof,
>
>>>
>>> OMAP has GPMC drivers under drivers/memory. I wonder if SROM should go there
>>> too, since it's a quite similar bus.
>>
>> I wish I get this feedback before, when we were discussing the SROM
>> patches. :/
>>
>> Indeed this
On 25.02.2016 13:19, pankaj.dubey wrote:
> Hi Krzysztof,
>
>>>
>>> OMAP has GPMC drivers under drivers/memory. I wonder if SROM should go there
>>> too, since it's a quite similar bus.
>>
>> I wish I get this feedback before, when we were discussing the SROM
>> patches. :/
>>
>> Indeed this
According to Data Manual(SPRS915P) of AM57x, TI QSPI controller on
DRA74(rev 1.1+) can support up to 64MHz in MODE-0, whereas MODE-3 is
limited to 48MHz. Hence, switch to MODE-0 for better throughput.
Signed-off-by: Vignesh R
---
arch/arm/boot/dts/dra7-evm.dts | 6 ++
1
According to Data Manual(SPRS915P) of AM57x, TI QSPI controller on
DRA74(rev 1.1+) can support up to 64MHz in MODE-0, whereas MODE-3 is
limited to 48MHz. Hence, switch to MODE-0 for better throughput.
Signed-off-by: Vignesh R
---
arch/arm/boot/dts/dra7-evm.dts | 6 ++
1 file changed, 2
On Wed, Feb 24, 2016 at 04:24AM, Rob Herring wrote:
> -Original Message-
> From: Rob Herring [mailto:r...@kernel.org]
> Sent: Wednesday, February 24, 2016 4:24 AM
> To: Qiang Zhao
> Cc: o...@buserror.net; Yang-Leo Li ; linux-
>
On Wed, Feb 24, 2016 at 04:24AM, Rob Herring wrote:
> -Original Message-
> From: Rob Herring [mailto:r...@kernel.org]
> Sent: Wednesday, February 24, 2016 4:24 AM
> To: Qiang Zhao
> Cc: o...@buserror.net; Yang-Leo Li ; linux-
> ker...@vger.kernel.org; devicet...@vger.kernel.org;
On Wed, Feb 24, 2016 at 09:47:27PM -0500, Rik van Riel wrote:
> On Thu, 2016-02-25 at 09:30 +0900, Joonsoo Kim wrote:
> > On Wed, Feb 24, 2016 at 05:17:56PM -0500, Rik van Riel wrote:
> > > On Wed, 2016-02-24 at 14:15 -0800, David Rientjes wrote:
> > > > On Wed, 24 Feb 2016, Rik van Riel wrote:
>
On Wed, Feb 24, 2016 at 09:47:27PM -0500, Rik van Riel wrote:
> On Thu, 2016-02-25 at 09:30 +0900, Joonsoo Kim wrote:
> > On Wed, Feb 24, 2016 at 05:17:56PM -0500, Rik van Riel wrote:
> > > On Wed, 2016-02-24 at 14:15 -0800, David Rientjes wrote:
> > > > On Wed, 24 Feb 2016, Rik van Riel wrote:
>
On 25/02/16 10:55, Balbir Singh wrote:
>
> On 25/02/16 01:28, Michael Ellerman wrote:
>> Currently we generate the module stub for ftrace_caller() at the bottom
>> of apply_relocate_add(). However apply_relocate_add() is potentially
>> called more than once per module, which means we will try to
On 25/02/16 10:55, Balbir Singh wrote:
>
> On 25/02/16 01:28, Michael Ellerman wrote:
>> Currently we generate the module stub for ftrace_caller() at the bottom
>> of apply_relocate_add(). However apply_relocate_add() is potentially
>> called more than once per module, which means we will try to
Hi Krzysztof,
On Thursday 25 February 2016 06:13 AM, Krzysztof Kozlowski wrote:
> On 25.02.2016 07:22, Olof Johansson wrote:
>> On Mon, Feb 15, 2016 at 09:34:02AM +0900, Krzysztof Kozlowski wrote:
>>> Hi Arnd, Kevin and Olof,
>>>
>>> This finally moves SROM controller and PMU code to separate
>>>
Hi Krzysztof,
On Thursday 25 February 2016 06:13 AM, Krzysztof Kozlowski wrote:
> On 25.02.2016 07:22, Olof Johansson wrote:
>> On Mon, Feb 15, 2016 at 09:34:02AM +0900, Krzysztof Kozlowski wrote:
>>> Hi Arnd, Kevin and Olof,
>>>
>>> This finally moves SROM controller and PMU code to separate
>>>
Hi Krzysztof,
On Thursday 25 February 2016 09:36 AM, Krzysztof Kozlowski wrote:
> On 25.02.2016 12:27, Pankaj Dubey wrote:
>> From: Alim Akhtar
>>
>> This patch adds tmu node, related temprature sensor and triping
>> point data for Atlas cpu core found on exynos7 SoC.
>>
Hi Krzysztof,
On Thursday 25 February 2016 09:36 AM, Krzysztof Kozlowski wrote:
> On 25.02.2016 12:27, Pankaj Dubey wrote:
>> From: Alim Akhtar
>>
>> This patch adds tmu node, related temprature sensor and triping
>> point data for Atlas cpu core found on exynos7 SoC.
>>
>> Signed-off-by: Alim
On 2016/2/24 23:19, Arnaldo Carvalho de Melo wrote:
Em Wed, Feb 24, 2016 at 11:20:45AM +, Wang Nan escreveu:
This patch allows 'perf script' output messages from BPF program.
For example, use test_bpf_output_3.c at the end of this commit
message,
# ./perf record -e
On 2016/2/24 23:19, Arnaldo Carvalho de Melo wrote:
Em Wed, Feb 24, 2016 at 11:20:45AM +, Wang Nan escreveu:
This patch allows 'perf script' output messages from BPF program.
For example, use test_bpf_output_3.c at the end of this commit
message,
# ./perf record -e
Hi Peter,
On 24/02/2016:05:02:41 PM, Peter Zijlstra wrote:
> On Wed, Feb 24, 2016 at 03:02:39PM +0100, Peter Zijlstra wrote:
> > FWIW, it would be nice to have a similar test for:
+ Michael, (C Test case for following proposed test case is at the end)
> >
> > attr = {
> >
Hi Peter,
On 24/02/2016:05:02:41 PM, Peter Zijlstra wrote:
> On Wed, Feb 24, 2016 at 03:02:39PM +0100, Peter Zijlstra wrote:
> > FWIW, it would be nice to have a similar test for:
+ Michael, (C Test case for following proposed test case is at the end)
> >
> > attr = {
> >
On 25.02.2016 12:27, Pankaj Dubey wrote:
> From: Alim Akhtar
>
> This patch adds tmu node, related temprature sensor and triping
> point data for Atlas cpu core found on exynos7 SoC.
>
> Signed-off-by: Alim Akhtar
Yours Sob is missing.
Cc-ed
On 25.02.2016 12:27, Pankaj Dubey wrote:
> From: Alim Akhtar
>
> This patch adds tmu node, related temprature sensor and triping
> point data for Atlas cpu core found on exynos7 SoC.
>
> Signed-off-by: Alim Akhtar
Yours Sob is missing.
Cc-ed Lukasz Majewski.
Lukasz,
Your review or ack would
Hi,
I promised a review and here it goes.
Let me focus on this one as the rest seems to depend on it.
On Monday, February 22, 2016 05:22:43 PM Steve Muckle wrote:
> From: Michael Turquette
>
> Scheduler-driven CPU frequency selection hopes to exploit both
> per-task
Hi,
I promised a review and here it goes.
Let me focus on this one as the rest seems to depend on it.
On Monday, February 22, 2016 05:22:43 PM Steve Muckle wrote:
> From: Michael Turquette
>
> Scheduler-driven CPU frequency selection hopes to exploit both
> per-task and global information in
Hi Joe,
Yes, first thing to try is to increase the tries.
Can you please point me to the bug and provide more details like platform,
monitor, cable.
Are you referring to the same issue as Oleksandr reported where a single link
dvi/hdmi cable didn’t work and dual link worked?
Regards,
Sonika
Hi Joe,
Yes, first thing to try is to increase the tries.
Can you please point me to the bug and provide more details like platform,
monitor, cable.
Are you referring to the same issue as Oleksandr reported where a single link
dvi/hdmi cable didn’t work and dual link worked?
Regards,
Sonika
201 - 300 of 2678 matches
Mail list logo