Hi Jassi,
On Sat, Sep 02, 2017 at 01:07:50PM +0530, Jassi Brar wrote:
[...]
> > +#define MBOX_CHAN_MAX 32
> > +
> > +#define MBOX_TX0x1
> > +
> > +/* Mailbox message length: 2 words */
> > +#define MBOX_MSG_LEN 2
> > +
> >
Hi Jassi,
On Sat, Sep 02, 2017 at 01:07:50PM +0530, Jassi Brar wrote:
[...]
> > +#define MBOX_CHAN_MAX 32
> > +
> > +#define MBOX_TX0x1
> > +
> > +/* Mailbox message length: 2 words */
> > +#define MBOX_MSG_LEN 2
> > +
> >
This adds two tests to validate mirror functionality with mremap()
system call on shared and private anon mappings. After the commit
dba58d3b8c5 ("mm/mremap: fail map duplication attempts for private
mappings"), any attempt to mirror private anon mapping will fail.
Suggested-by: Mike Kravetz
This adds two tests to validate mirror functionality with mremap()
system call on shared and private anon mappings. After the commit
dba58d3b8c5 ("mm/mremap: fail map duplication attempts for private
mappings"), any attempt to mirror private anon mapping will fail.
Suggested-by: Mike Kravetz
There are cases we call device_del() without detaching it from the
driver(e.g. spi core del children devices).
Signed-off-by: Jeffy Chen
---
drivers/base/core.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/base/core.c b/drivers/base/core.c
index
There are cases we call device_del() without detaching it from the
driver(e.g. spi core del children devices).
Signed-off-by: Jeffy Chen
---
drivers/base/core.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/base/core.c b/drivers/base/core.c
index 12ebd055724c..717efc3020af
Hi Lorenzo,
On Tue, Oct 17, 2017 at 6:38 AM, Lorenzo Pieralisi
wrote:
> Hi Khuong,
>
> On Mon, Oct 16, 2017 at 02:19:50PM -0700, Khuong Dinh wrote:
>> Hi Lorenzo,
>> Do you have any comments for this patch?
>
> I'd have some comments but given that there are related
Hi Lorenzo,
On Tue, Oct 17, 2017 at 6:38 AM, Lorenzo Pieralisi
wrote:
> Hi Khuong,
>
> On Mon, Oct 16, 2017 at 02:19:50PM -0700, Khuong Dinh wrote:
>> Hi Lorenzo,
>> Do you have any comments for this patch?
>
> I'd have some comments but given that there are related issues with ACPI
> probe
Mathieu Desnoyers writes:
> - On Oct 17, 2017, at 6:36 AM, Michael Ellerman m...@ellerman.id.au wrote:
>
>> Mathieu Desnoyers writes:
>>
>>> Hi Michael,
>>>
>>> With your changes integrated, both rseq and cpu-opv selftests
Mathieu Desnoyers writes:
> - On Oct 17, 2017, at 6:36 AM, Michael Ellerman m...@ellerman.id.au wrote:
>
>> Mathieu Desnoyers writes:
>>
>>> Hi Michael,
>>>
>>> With your changes integrated, both rseq and cpu-opv selftests fail to
>>> build if I pass e.g. -j32 to make.
>>>
>>> cd
Kees Cook writes:
> On Tue, Oct 17, 2017 at 7:18 AM, Kalle Valo wrote:
>> + linux-wireless
>>
>> Hi Kees,
>>
>> Kees Cook writes:
>>
>>> This is the current set of outstanding networking patches to perform
>>> conversions to
Kees Cook writes:
> On Tue, Oct 17, 2017 at 7:18 AM, Kalle Valo wrote:
>> + linux-wireless
>>
>> Hi Kees,
>>
>> Kees Cook writes:
>>
>>> This is the current set of outstanding networking patches to perform
>>> conversions to the new timer interface (rebased to -next). This is not
>>> all
On (10/18/17 15:21), Tobin C. Harding wrote:
[..]
> diff --git a/lib/vsprintf.c b/lib/vsprintf.c
> index 86c3385b9eb3..4609738cd2cd 100644
> --- a/lib/vsprintf.c
> +++ b/lib/vsprintf.c
> @@ -33,6 +33,8 @@
> #include
> #include
> #include
> +#include
> +#include
> #ifdef CONFIG_BLOCK
>
On Tue, Oct 17, 2017 at 5:06 PM, Russell King - ARM Linux
wrote:
> On Sun, Oct 15, 2017 at 10:19:45AM +0100, Gilad Ben-Yossef wrote:
>> Many users of kernel async. crypto services have a pattern of
>> starting an async. crypto op and than using a completion
>> to wait for
On (10/18/17 15:21), Tobin C. Harding wrote:
[..]
> diff --git a/lib/vsprintf.c b/lib/vsprintf.c
> index 86c3385b9eb3..4609738cd2cd 100644
> --- a/lib/vsprintf.c
> +++ b/lib/vsprintf.c
> @@ -33,6 +33,8 @@
> #include
> #include
> #include
> +#include
> +#include
> #ifdef CONFIG_BLOCK
>
On Tue, Oct 17, 2017 at 5:06 PM, Russell King - ARM Linux
wrote:
> On Sun, Oct 15, 2017 at 10:19:45AM +0100, Gilad Ben-Yossef wrote:
>> Many users of kernel async. crypto services have a pattern of
>> starting an async. crypto op and than using a completion
>> to wait for it to end.
>>
>> This
Hi,
On 17.10.2017 17:22, Jeremy Linton wrote:
Hi,
On 10/17/2017 08:25 AM, Tomasz Nowicki wrote:
Hi Jeremy,
I did second round of review and have some more comments, please see
below:
On 12.10.2017 21:48, Jeremy Linton wrote:
ACPI 6.2 adds a new table, which describes how processing units
Hi,
On 17.10.2017 17:22, Jeremy Linton wrote:
Hi,
On 10/17/2017 08:25 AM, Tomasz Nowicki wrote:
Hi Jeremy,
I did second round of review and have some more comments, please see
below:
On 12.10.2017 21:48, Jeremy Linton wrote:
ACPI 6.2 adds a new table, which describes how processing units
On 10/17/2017 10:33 AM, Alexander Duyck wrote:
> On Tue, Oct 17, 2017 at 8:49 AM, Arnd Bergmann wrote:
>> The new bandwidth calculation caused a link error on 32-bit
>> architectures, like
>>
>> ERROR: "__aeabi_uldivmod" [drivers/net/ethernet/intel/i40e/i40e.ko]
>> undefined!
>>
On 10/17/2017 10:33 AM, Alexander Duyck wrote:
> On Tue, Oct 17, 2017 at 8:49 AM, Arnd Bergmann wrote:
>> The new bandwidth calculation caused a link error on 32-bit
>> architectures, like
>>
>> ERROR: "__aeabi_uldivmod" [drivers/net/ethernet/intel/i40e/i40e.ko]
>> undefined!
>>
>> The problem
Andi Kleen writes:
> From: Andi Kleen
>
> I like _ONCE warnings because it's guaranteed that they don't
> flood the log.
>
> During testing I find it useful to reset the state of the once warnings,
> so that I can rerun tests and see if they trigger
Andi Kleen writes:
> From: Andi Kleen
>
> I like _ONCE warnings because it's guaranteed that they don't
> flood the log.
>
> During testing I find it useful to reset the state of the once warnings,
> so that I can rerun tests and see if they trigger again, or can
> guarantee that a test run
On Tue, Oct 17, 2017 at 09:12:02AM +0200, Ingo Molnar wrote:
> > > diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> > > index 2689b7c..e270584 100644
> > > --- a/lib/Kconfig.debug
> > > +++ b/lib/Kconfig.debug
> > > @@ -1092,8 +1092,8 @@ config PROVE_LOCKING
> > > select DEBUG_MUTEXES
> > >
On Tue, Oct 17, 2017 at 09:12:02AM +0200, Ingo Molnar wrote:
> > > diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> > > index 2689b7c..e270584 100644
> > > --- a/lib/Kconfig.debug
> > > +++ b/lib/Kconfig.debug
> > > @@ -1092,8 +1092,8 @@ config PROVE_LOCKING
> > > select DEBUG_MUTEXES
> > >
On 18/10/17 02:39, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Tue, 17 Oct 2017 17:07:54 +0200
>
> Add a jump target so that a bit of code can be better reused
> at the end of this function.
Rather than moving bits around, I'd rather allocate pe_alloc
On 18/10/17 02:39, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Tue, 17 Oct 2017 17:07:54 +0200
>
> Add a jump target so that a bit of code can be better reused
> at the end of this function.
Rather than moving bits around, I'd rather allocate pe_alloc on stack and
ditch kfree() at
On 18/10/17 02:40, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Tue, 17 Oct 2017 17:18:10 +0200
>
> Replace the specification of a data structure by a pointer dereference
> as the parameter for the operator "sizeof" to make the corresponding size
>
On 18/10/17 02:40, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Tue, 17 Oct 2017 17:18:10 +0200
>
> Replace the specification of a data structure by a pointer dereference
> as the parameter for the operator "sizeof" to make the corresponding size
> determination a bit safer according
On 18/10/17 02:37, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Tue, 17 Oct 2017 16:52:43 +0200
>
> Omit an extra message for a memory allocation failure in this function.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by:
On 18/10/17 02:37, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Tue, 17 Oct 2017 16:52:43 +0200
>
> Omit an extra message for a memory allocation failure in this function.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus Elfring
> ---
>
Hi
On Tue, Sep 19, 2017 at 8:29 AM, Vignesh R wrote:
> From: Jeff Lance
>
> Step config setting for 5 wire touchscreen is incorrect for Y coordinates.
> It was broken while we moved to DT. If you look close at the offending
> commit bb76dc09ddfc ("input:
Hi
On Tue, Sep 19, 2017 at 8:29 AM, Vignesh R wrote:
> From: Jeff Lance
>
> Step config setting for 5 wire touchscreen is incorrect for Y coordinates.
> It was broken while we moved to DT. If you look close at the offending
> commit bb76dc09ddfc ("input: ti_am33x_tsc: Order of TSC wires, made
>
Hi guys,
On 10/18/2017 03:05 AM, Mark Brown wrote:
On Tue, Oct 17, 2017 at 11:53:01AM -0700, Brian Norris wrote:
On Tue, Oct 17, 2017 at 07:46:03PM +0100, Mark Brown wrote:
I would expect we can get a long way in the DT by doing a pass over the
tree and adding links between device nodes in
Hi guys,
On 10/18/2017 03:05 AM, Mark Brown wrote:
On Tue, Oct 17, 2017 at 11:53:01AM -0700, Brian Norris wrote:
On Tue, Oct 17, 2017 at 07:46:03PM +0100, Mark Brown wrote:
I would expect we can get a long way in the DT by doing a pass over the
tree and adding links between device nodes in
On Wed, May 31, 2017 at 04:04:17PM +0200, Frederic Weisbecker wrote:
> On Tue, May 30, 2017 at 02:29:20PM +0900, Byungchul Park wrote:
> > On Fri, May 12, 2017 at 09:45:35AM +0900, Byungchul Park wrote:
> > > Although llist provides proper APIs, they are not used. Make them used.
> >
> > +to
On Wed, May 31, 2017 at 04:04:17PM +0200, Frederic Weisbecker wrote:
> On Tue, May 30, 2017 at 02:29:20PM +0900, Byungchul Park wrote:
> > On Fri, May 12, 2017 at 09:45:35AM +0900, Byungchul Park wrote:
> > > Although llist provides proper APIs, they are not used. Make them used.
> >
> > +to
Hi Borislav,
On 2017/10/18 1:06, Borislav Petkov wrote:
> On Tue, Oct 17, 2017 at 04:02:21PM +0800, Dongjiu Geng wrote:
>> ARMv8.2 requires implementation of the RAS extension, in
>> this extension it adds SEI(SError Interrupt) notification
>> type, this patch adds new GHES error source SEI
Hi Borislav,
On 2017/10/18 1:06, Borislav Petkov wrote:
> On Tue, Oct 17, 2017 at 04:02:21PM +0800, Dongjiu Geng wrote:
>> ARMv8.2 requires implementation of the RAS extension, in
>> this extension it adds SEI(SError Interrupt) notification
>> type, this patch adds new GHES error source SEI
The zImage file size should be aligned.
Fixes: e4bae4d0b5f3 ("arm/efi: Split zImage code and data into separate PE/COFF
sections")
Signed-off-by: Jeffy Chen
---
arch/arm/boot/compressed/vmlinux.lds.S | 8
1 file changed, 4 insertions(+), 4 deletions(-)
The zImage file size should be aligned.
Fixes: e4bae4d0b5f3 ("arm/efi: Split zImage code and data into separate PE/COFF
sections")
Signed-off-by: Jeffy Chen
---
arch/arm/boot/compressed/vmlinux.lds.S | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
Hi,
On 10/18/2017 05:13 AM, Jingoo Han wrote:
On Tuesday, October 17, 2017 6:16 AM, Jeffy Chen wrote:
From: Tomasz Figa
The driver that instantiates the bridge should own the drvdata, as all
driver model callbacks (probe, remove, shutdown, PM ops, etc.) are also
owned by
Hi,
On 10/18/2017 05:13 AM, Jingoo Han wrote:
On Tuesday, October 17, 2017 6:16 AM, Jeffy Chen wrote:
From: Tomasz Figa
The driver that instantiates the bridge should own the drvdata, as all
driver model callbacks (probe, remove, shutdown, PM ops, etc.) are also
owned by its driver struct.
Greetings,
*
TL;DR
- LCA Kernel Miniconf, Sydney, Australia, 22 Jan 2018
- Submissions by 30 November 2017, 23:59 (AEDT/UTC+11)
- Wanted: anything interesting to kernel hackers! Speakers from
diverse backgrounds encouraged!
- Form:
Greetings,
*
TL;DR
- LCA Kernel Miniconf, Sydney, Australia, 22 Jan 2018
- Submissions by 30 November 2017, 23:59 (AEDT/UTC+11)
- Wanted: anything interesting to kernel hackers! Speakers from
diverse backgrounds encouraged!
- Form:
The GPIO controller also acts as an interrupt controller and the
interrupt lines are connected to the AIDET block.
Signed-off-by: Masahiro Yamada
---
arch/arm/boot/dts/uniphier-ld4.dtsi | 14 ++
arch/arm/boot/dts/uniphier-pro4.dtsi | 14
Interrupt lines from on-board devices are connected to the GPIO
controller. Add GPIO hogging so that the corresponding GPIO line
is automatically requested.
Signed-off-by: Masahiro Yamada
---
arch/arm/boot/dts/uniphier-ld4-ref.dts | 8
The GPIO controller also acts as an interrupt controller and the
interrupt lines are connected to the AIDET block.
Signed-off-by: Masahiro Yamada
---
arch/arm/boot/dts/uniphier-ld4.dtsi | 14 ++
arch/arm/boot/dts/uniphier-pro4.dtsi | 14 ++
Interrupt lines from on-board devices are connected to the GPIO
controller. Add GPIO hogging so that the corresponding GPIO line
is automatically requested.
Signed-off-by: Masahiro Yamada
---
arch/arm/boot/dts/uniphier-ld4-ref.dts | 8
arch/arm/boot/dts/uniphier-ld6b-ref.dts | 8
Masahiro Yamada (6):
ARM: dts: uniphier: add GPIO controller nodes
arm64: dts: uniphier: add GPIO controller nodes
ARM: dts: uniphier: route on-board device IRQ to GPIO controller
arm64: dts: uniphier: route on-board device IRQ to GPIO controller
ARM: dts: uniphier: add GPIO hog
Interrupt lines from on-board devices are connected to the GPIO
controller. Add GPIO hogging so that the corresponding GPIO line
is automatically requested.
Signed-off-by: Masahiro Yamada
---
arch/arm64/boot/dts/socionext/uniphier-ld11-ref.dts | 8
Interrupt lines from on-board devices are connected to the GPIO
controller. Handle this correctly.
Signed-off-by: Masahiro Yamada
---
arch/arm/boot/dts/uniphier-ld4-ref.dts | 2 +-
arch/arm/boot/dts/uniphier-ld6b-ref.dts | 2 +-
Interrupt lines from on-board devices are connected to the GPIO
controller. Handle this correctly.
Signed-off-by: Masahiro Yamada
---
arch/arm64/boot/dts/socionext/uniphier-ld11-ref.dts | 3 ++-
arch/arm64/boot/dts/socionext/uniphier-ld20-ref.dts | 3 ++-
2
The GPIO controller also acts as an interrupt controller and the
interrupt lines are connected to the AIDET block.
Signed-off-by: Masahiro Yamada
---
arch/arm64/boot/dts/socionext/uniphier-ld11.dtsi | 25
Interrupt lines from on-board devices are connected to the GPIO
controller. Handle this correctly.
Signed-off-by: Masahiro Yamada
---
arch/arm/boot/dts/uniphier-ld4-ref.dts | 2 +-
arch/arm/boot/dts/uniphier-ld6b-ref.dts | 2 +-
arch/arm/boot/dts/uniphier-pro4-ref.dts | 2 +-
Interrupt lines from on-board devices are connected to the GPIO
controller. Handle this correctly.
Signed-off-by: Masahiro Yamada
---
arch/arm64/boot/dts/socionext/uniphier-ld11-ref.dts | 3 ++-
arch/arm64/boot/dts/socionext/uniphier-ld20-ref.dts | 3 ++-
2 files changed, 4 insertions(+), 2
The GPIO controller also acts as an interrupt controller and the
interrupt lines are connected to the AIDET block.
Signed-off-by: Masahiro Yamada
---
arch/arm64/boot/dts/socionext/uniphier-ld11.dtsi | 25
arch/arm64/boot/dts/socionext/uniphier-ld20.dtsi | 19
Masahiro Yamada (6):
ARM: dts: uniphier: add GPIO controller nodes
arm64: dts: uniphier: add GPIO controller nodes
ARM: dts: uniphier: route on-board device IRQ to GPIO controller
arm64: dts: uniphier: route on-board device IRQ to GPIO controller
ARM: dts: uniphier: add GPIO hog
Interrupt lines from on-board devices are connected to the GPIO
controller. Add GPIO hogging so that the corresponding GPIO line
is automatically requested.
Signed-off-by: Masahiro Yamada
---
arch/arm64/boot/dts/socionext/uniphier-ld11-ref.dts | 8
Currently there are many places in the kernel where addresses are being
printed using an unadorned %p. Kernel pointers should be printed using
%pK allowing some control via the kptr_restrict sysctl. Exposing addresses
gives attackers sensitive information about the kernel layout in memory.
We can
Currently there are many places in the kernel where addresses are being
printed using an unadorned %p. Kernel pointers should be printed using
%pK allowing some control via the kptr_restrict sysctl. Exposing addresses
gives attackers sensitive information about the kernel layout in memory.
We can
On Sat, Oct 14, 2017 at 11:32:26AM +0100, Christos Gkekas wrote:
> Delete variables 'tree' and 'sb', which are set but never used.
>
> Signed-off-by: Christos Gkekas
Looks good. If it helps you can add:
Reviewed-by: Ernesto A. Fernández
On Sat, Oct 14, 2017 at 11:32:26AM +0100, Christos Gkekas wrote:
> Delete variables 'tree' and 'sb', which are set but never used.
>
> Signed-off-by: Christos Gkekas
Looks good. If it helps you can add:
Reviewed-by: Ernesto A. Fernández
> ---
> fs/hfs/bnode.c | 4
>
Colin King writes:
> From: Colin Ian King
>
> The variable slots is being assigned a value of zero that is never
> read, slots is being updated again a few lines later. Remove this
> redundant assignment.
> Cleans clang warning: Value stored
Colin King writes:
> From: Colin Ian King
>
> The variable slots is being assigned a value of zero that is never
> read, slots is being updated again a few lines later. Remove this
> redundant assignment.
> Cleans clang warning: Value stored to 'slots' is never read
>
> Signed-off-by: Colin Ian
On Tuesday 19 September 2017 11:59 AM, Vignesh R wrote:
> From: Jeff Lance
>
> Step config setting for 5 wire touchscreen is incorrect for Y coordinates.
> It was broken while we moved to DT. If you look close at the offending
> commit bb76dc09ddfc ("input: ti_am33x_tsc: Order
On Tuesday 19 September 2017 11:59 AM, Vignesh R wrote:
> From: Jeff Lance
>
> Step config setting for 5 wire touchscreen is incorrect for Y coordinates.
> It was broken while we moved to DT. If you look close at the offending
> commit bb76dc09ddfc ("input: ti_am33x_tsc: Order of TSC wires,
On 17-10-17, 16:42, Julia Lawall wrote:
>
>
> On Tue, 17 Oct 2017, Bhumika Goyal wrote:
>
> > Make the masks field of clk_aux structure const as it do not modify the
> > fields of the aux_clk_masks structure it points to.
> >
> > Make the struct aux_clk_masks *aux argument of the function
> >
On 17-10-17, 16:42, Julia Lawall wrote:
>
>
> On Tue, 17 Oct 2017, Bhumika Goyal wrote:
>
> > Make the masks field of clk_aux structure const as it do not modify the
> > fields of the aux_clk_masks structure it points to.
> >
> > Make the struct aux_clk_masks *aux argument of the function
> >
On 10/17/2017 10:18 AM, Petr Mladek wrote:
> On Thu 2017-10-12 17:12:29, Jason Baron wrote:
>> Sometimes we would like to revert a particular fix. This is currently
>> This is not easy because we want to keep all other fixes active and we
>> could revert only the last applied patch.
>>
>> One
On 17-10-17, 16:38, Bhumika Goyal wrote:
> Make these const as they are either stored in the masks 'const' field
> of a clk_aux structure or passed to the function clk_register_aux
> having the argument as const.
>
> Signed-off-by: Bhumika Goyal
> ---
>
On 10/17/2017 10:18 AM, Petr Mladek wrote:
> On Thu 2017-10-12 17:12:29, Jason Baron wrote:
>> Sometimes we would like to revert a particular fix. This is currently
>> This is not easy because we want to keep all other fixes active and we
>> could revert only the last applied patch.
>>
>> One
On 17-10-17, 16:38, Bhumika Goyal wrote:
> Make these const as they are either stored in the masks 'const' field
> of a clk_aux structure or passed to the function clk_register_aux
> having the argument as const.
>
> Signed-off-by: Bhumika Goyal
> ---
> drivers/clk/spear/clk-aux-synth.c | 2
On Oct 12, 2017, at 10:17, Gustavo A. R. Silva wrote:
>
> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> where we are expecting to fall through.
>
> Addresses-Coverity-ID: 1077598
> Signed-off-by: Gustavo A. R. Silva
On Oct 12, 2017, at 10:17, Gustavo A. R. Silva wrote:
>
> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> where we are expecting to fall through.
>
> Addresses-Coverity-ID: 1077598
> Signed-off-by: Gustavo A. R. Silva
Reviewed-by: Andreas Dilger
> ---
>
On 10/17/2017 09:50 AM, Miroslav Benes wrote:
> On Tue, 17 Oct 2017, Miroslav Benes wrote:
>
>> On Tue, 10 Oct 2017, Jason Baron wrote:
>>
>>>
>>>
>>> On 10/06/2017 06:32 PM, Josh Poimboeuf wrote:
On Wed, Sep 27, 2017 at 11:41:30PM -0400, Jason Baron wrote:
> Since 'atomic replace' has
On 10/17/2017 09:50 AM, Miroslav Benes wrote:
> On Tue, 17 Oct 2017, Miroslav Benes wrote:
>
>> On Tue, 10 Oct 2017, Jason Baron wrote:
>>
>>>
>>>
>>> On 10/06/2017 06:32 PM, Josh Poimboeuf wrote:
On Wed, Sep 27, 2017 at 11:41:30PM -0400, Jason Baron wrote:
> Since 'atomic replace' has
> From: "Guenter Roeck"
> To: shuw...@redhat.com
> Cc: "fenghua yu" , jdelv...@suse.com,
> linux-hw...@vger.kernel.org,
> linux-kernel@vger.kernel.org, ch...@redhat.com, yiz...@redhat.com
> Sent: Tuesday, October 17, 2017 11:25:50 PM
> Subject: Re:
> From: "Guenter Roeck"
> To: shuw...@redhat.com
> Cc: "fenghua yu" , jdelv...@suse.com,
> linux-hw...@vger.kernel.org,
> linux-kernel@vger.kernel.org, ch...@redhat.com, yiz...@redhat.com
> Sent: Tuesday, October 17, 2017 11:25:50 PM
> Subject: Re: [PATCH] hwmon: (coretemp) remove duplicated
From: Younian Wang
Add pinctrl nodes for hi3798cv200-poplar board
Signed-off-by: Younian Wang
Signed-off-by: Jiancheng Xue
---
.../boot/dts/hisilicon/hi3798cv200-poplar.dts | 1 +
From: Younian Wang
Add pinctrl nodes for hi3798cv200-poplar board
Signed-off-by: Younian Wang
Signed-off-by: Jiancheng Xue
---
.../boot/dts/hisilicon/hi3798cv200-poplar.dts | 1 +
arch/arm64/boot/dts/hisilicon/hi3798cv200.dtsi | 71 +++
Mimi Zohar writes:
> On Tue, 2017-10-17 at 12:11 +0200, Julia Lawall wrote:
>> On Tue, 17 Oct 2017, Dan Carpenter wrote:
>> > On Tue, Oct 17, 2017 at 10:56:42AM +0200, Julia Lawall wrote:
>> > > On Tue, 17 Oct 2017, Dan Carpenter wrote:
>> > > > On Mon, Oct 16, 2017 at
Mimi Zohar writes:
> On Tue, 2017-10-17 at 12:11 +0200, Julia Lawall wrote:
>> On Tue, 17 Oct 2017, Dan Carpenter wrote:
>> > On Tue, Oct 17, 2017 at 10:56:42AM +0200, Julia Lawall wrote:
>> > > On Tue, 17 Oct 2017, Dan Carpenter wrote:
>> > > > On Mon, Oct 16, 2017 at 09:35:12PM +0300, Jarkko
From: Younian Wang
Supplement properties of ir node for poplar board.
Signed-off-by: Younian Wang
---
arch/arm64/boot/dts/hisilicon/hi3798cv200.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git
Add more devices nodes and properties for poplar board, involving ir, emmc and
pinctrl nodes.
Younian Wang (2):
arm64: dts: hisilicon: supplement properties of ir node for poplar
board
arm64: dts: hisilicon: add pinctrl nodes for hi3798cv200-poplar board
tianshuliang (1):
arm64: dts:
From: tianshuliang
Supplement properties of emmc nodes to support high performance.
Signed-off-by: tianshuliang
---
arch/arm64/boot/dts/hisilicon/hi3798cv200-poplar.dts | 12
arch/arm64/boot/dts/hisilicon/hi3798cv200.dtsi
From: Younian Wang
Supplement properties of ir node for poplar board.
Signed-off-by: Younian Wang
---
arch/arm64/boot/dts/hisilicon/hi3798cv200.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/boot/dts/hisilicon/hi3798cv200.dtsi
Add more devices nodes and properties for poplar board, involving ir, emmc and
pinctrl nodes.
Younian Wang (2):
arm64: dts: hisilicon: supplement properties of ir node for poplar
board
arm64: dts: hisilicon: add pinctrl nodes for hi3798cv200-poplar board
tianshuliang (1):
arm64: dts:
From: tianshuliang
Supplement properties of emmc nodes to support high performance.
Signed-off-by: tianshuliang
---
arch/arm64/boot/dts/hisilicon/hi3798cv200-poplar.dts | 12
arch/arm64/boot/dts/hisilicon/hi3798cv200.dtsi | 8 +---
2 files changed, 17 insertions(+), 3
On Tue, Oct 17, 2017 at 8:06 PM, Martin K. Petersen
wrote:
>
> Kees,
>
>> Thanks for the reviews! Do you want the timer tree to carry these
>> patches, or can you pick them up in the scsi tree?
>
> Up to you. I'm not going to rebase my 4.15 queue this late in the cycle
On Tue, Oct 17, 2017 at 8:06 PM, Martin K. Petersen
wrote:
>
> Kees,
>
>> Thanks for the reviews! Do you want the timer tree to carry these
>> patches, or can you pick them up in the scsi tree?
>
> Up to you. I'm not going to rebase my 4.15 queue this late in the cycle
> so the patches would end
Add an specific emmc driver for hi3798cv200-poplar board. Previously, it used
the
generic dw-mmc driver with lower performance.
tianshuliang (2):
dt-bindings: mmc: add bindings for hi3798cv200-dw-mshc
mmc: dw_mmc: add support for hi3798cv200 specific extensions of
dw-mshc
Add an specific emmc driver for hi3798cv200-poplar board. Previously, it used
the
generic dw-mmc driver with lower performance.
tianshuliang (2):
dt-bindings: mmc: add bindings for hi3798cv200-dw-mshc
mmc: dw_mmc: add support for hi3798cv200 specific extensions of
dw-mshc
From: tianshuliang
Hi3798cv200 SoC extends the dw-mshc controller for additional clock
and bus control. Add support for these extensions.
Signed-off-by: tianshuliang
Signed-off-by: Jiancheng Xue
---
From: tianshuliang
Hisilicon hi3798cv200 SoC extends the dw-mshc controller
for additional clock control. Add device tree bindings for
hi3798cv200-dw-mshc.
Signed-off-by: tianshuliang
Signed-off-by: Jiancheng Xue
From: tianshuliang
Hi3798cv200 SoC extends the dw-mshc controller for additional clock
and bus control. Add support for these extensions.
Signed-off-by: tianshuliang
Signed-off-by: Jiancheng Xue
---
drivers/mmc/host/Kconfig | 9 ++
drivers/mmc/host/Makefile | 1 +
From: tianshuliang
Hisilicon hi3798cv200 SoC extends the dw-mshc controller
for additional clock control. Add device tree bindings for
hi3798cv200-dw-mshc.
Signed-off-by: tianshuliang
Signed-off-by: Jiancheng Xue
---
.../bindings/mmc/hi3798cv200-dw-mshc.txt | 51
Hi,Borislav
On 2017/10/18 0:43, Borislav Petkov wrote:
>> -}
>> -
> So GHES NMI notification method is x86-only AFAIK and HAVE_ACPI_APEI_NMI
> is selected only on x86. Why are you removing those guards? Does ARM
> have ACPI_HEST_NOTIFY_NMI notification type now too?
ARM does not have
Hi,Borislav
On 2017/10/18 0:43, Borislav Petkov wrote:
>> -}
>> -
> So GHES NMI notification method is x86-only AFAIK and HAVE_ACPI_APEI_NMI
> is selected only on x86. Why are you removing those guards? Does ARM
> have ACPI_HEST_NOTIFY_NMI notification type now too?
ARM does not have
Kees,
> Thanks for the reviews! Do you want the timer tree to carry these
> patches, or can you pick them up in the scsi tree?
Up to you. I'm not going to rebase my 4.15 queue this late in the cycle
so the patches would end up going in at the end of the merge window. If
you prefer to have them
Kees,
> Thanks for the reviews! Do you want the timer tree to carry these
> patches, or can you pick them up in the scsi tree?
Up to you. I'm not going to rebase my 4.15 queue this late in the cycle
so the patches would end up going in at the end of the merge window. If
you prefer to have them
1 - 100 of 2408 matches
Mail list logo