Hello Christoph,
On Wed, Feb 07, 2018 at 06:08:00PM +0100, Christoph Böhmwalder wrote:
> Remove some "out of memory" messages that are considered useless.
>
> Signed-off-by: Christoph Böhmwalder
> ---
> drivers/hid/hid-logitech-dj.c | 11 +++
> 1 file changed,
Hello Christoph,
On Wed, Feb 07, 2018 at 06:08:00PM +0100, Christoph Böhmwalder wrote:
> Remove some "out of memory" messages that are considered useless.
>
> Signed-off-by: Christoph Böhmwalder
> ---
> drivers/hid/hid-logitech-dj.c | 11 +++
> 1 file changed, 3 insertions(+), 8
On 07/02/2018 05:11, Jia He wrote:
> In commit 316ca8804ea8 ("ACPI/IORT: Remove linker section for IORT entries
> probing"), iort entries was removed in vmlinux.lds.h. But in
> commit 2fcc112af37f ("clocksource/drivers: Rename clksrc table to timer"),
> this line was back incorrectly.
>
> It does
On 07/02/2018 05:11, Jia He wrote:
> In commit 316ca8804ea8 ("ACPI/IORT: Remove linker section for IORT entries
> probing"), iort entries was removed in vmlinux.lds.h. But in
> commit 2fcc112af37f ("clocksource/drivers: Rename clksrc table to timer"),
> this line was back incorrectly.
>
> It does
On Wed, Feb 07, 2018 at 11:50:28PM -0600, Daniel Díaz wrote:
> The 5lvl.c test file was incorporated into another one in
> selftests/vm (va_128TBswitch.c) in commit 235266b8.
>
> Signed-off-by: Daniel Díaz
Acked-by: Kirill A. Shutemov
On Wed, Feb 07, 2018 at 11:50:28PM -0600, Daniel Díaz wrote:
> The 5lvl.c test file was incorporated into another one in
> selftests/vm (va_128TBswitch.c) in commit 235266b8.
>
> Signed-off-by: Daniel Díaz
Acked-by: Kirill A. Shutemov
--
Kirill A. Shutemov
On Tue, Feb 06, 2018 at 05:49:03PM +0100, Stefan Agner wrote:
> Add support for the Computer on Module Colibri iMX6ULL and its
> Bluetooth/Wifi variant along with the development/evaluation carrier
> board device trees. Follow the usual hierarchic include model,
> maintaining shared configuration
On Tue, Feb 06, 2018 at 05:49:03PM +0100, Stefan Agner wrote:
> Add support for the Computer on Module Colibri iMX6ULL and its
> Bluetooth/Wifi variant along with the development/evaluation carrier
> board device trees. Follow the usual hierarchic include model,
> maintaining shared configuration
On 06.02.2018 09:42, Philippe Cornu wrote:
> Add support for the Synopsys DesignWare MIPI DSI version 1.31
> Two registers need to be updated/added for supporting 1.31:
> * PHY_TMR_CFG 0x9c (updated)
> 1.30 [31:24] phy_hs2lp_time
>[23:16] phy_lp2hs_time
>[14: 0] max_rd_time
>
>
On 04.02.2018 22:31, Philippe Cornu wrote:
> This patch adds the DCS/GENERIC DSI read feature.
>
> Signed-off-by: Philippe Cornu
> ---
Queued to drm-misc-next.
--
Regards
Andrzej
On 06.02.2018 09:42, Philippe Cornu wrote:
> Add support for the Synopsys DesignWare MIPI DSI version 1.31
> Two registers need to be updated/added for supporting 1.31:
> * PHY_TMR_CFG 0x9c (updated)
> 1.30 [31:24] phy_hs2lp_time
>[23:16] phy_lp2hs_time
>[14: 0] max_rd_time
>
>
On 04.02.2018 22:31, Philippe Cornu wrote:
> This patch adds the DCS/GENERIC DSI read feature.
>
> Signed-off-by: Philippe Cornu
> ---
Queued to drm-misc-next.
--
Regards
Andrzej
2018-02-07 22:16 GMT+08:00 Paolo Bonzini :
> On 07/02/2018 07:25, Wanpeng Li wrote:
>> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
>> index 786cd00..445e702 100644
>> --- a/arch/x86/kvm/x86.c
>> +++ b/arch/x86/kvm/x86.c
>> @@ -7458,6 +7458,11 @@ int
2018-02-07 22:16 GMT+08:00 Paolo Bonzini :
> On 07/02/2018 07:25, Wanpeng Li wrote:
>> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
>> index 786cd00..445e702 100644
>> --- a/arch/x86/kvm/x86.c
>> +++ b/arch/x86/kvm/x86.c
>> @@ -7458,6 +7458,11 @@ int kvm_arch_vcpu_ioctl_run(struct kvm_vcpu
HI Jerome:
On 02/01/18 02:09, Jerome Brunet wrote:
> Meson clock controllers needs to move the classical iomem registers to
> regmap. This is triggered because the HHI controllers found on the GXBB
> and GXL host more than just clocks. To properly handle this, we would
> like to migrate HHI to
HI Jerome:
On 02/01/18 02:09, Jerome Brunet wrote:
> Meson clock controllers needs to move the classical iomem registers to
> regmap. This is triggered because the HHI controllers found on the GXBB
> and GXL host more than just clocks. To properly handle this, we would
> like to migrate HHI to
From: Wanpeng Li
Reported by syzkaller:
WARNING: CPU: 6 PID: 2434 at arch/x86/kvm/vmx.c:6660
handle_ept_misconfig+0x54/0x1e0 [kvm_intel]
CPU: 6 PID: 2434 Comm: repro_test Not tainted 4.15.0+ #4
RIP: 0010:handle_ept_misconfig+0x54/0x1e0 [kvm_intel]
Call Trace:
From: Wanpeng Li
Reported by syzkaller:
WARNING: CPU: 6 PID: 2434 at arch/x86/kvm/vmx.c:6660
handle_ept_misconfig+0x54/0x1e0 [kvm_intel]
CPU: 6 PID: 2434 Comm: repro_test Not tainted 4.15.0+ #4
RIP: 0010:handle_ept_misconfig+0x54/0x1e0 [kvm_intel]
Call Trace:
The commit message says that we are allowed to read and write up to 32
bytes but the code only allows us to write 31 bytes. In other words,
the ">=" should be changed to ">". But this is already checked in
regmap_raw_read()/write() so we can just remove the if statemetents.
Fixes: 29332534e2b6
The commit message says that we are allowed to read and write up to 32
bytes but the code only allows us to write 31 bytes. In other words,
the ">=" should be changed to ">". But this is already checked in
regmap_raw_read()/write() so we can just remove the if statemetents.
Fixes: 29332534e2b6
We're supposed to be checking that "val_len" is not too large but
instead we check if it is smaller than the max.
The only function affected would be regmap_i2c_smbus_i2c_write() in
drivers/base/regmap/regmap-i2c.c. Strangely that function has its own
limit check which returns an error if (count
We're supposed to be checking that "val_len" is not too large but
instead we check if it is smaller than the max.
The only function affected would be regmap_i2c_smbus_i2c_write() in
drivers/base/regmap/regmap-i2c.c. Strangely that function has its own
limit check which returns an error if (count
On Wed, Feb 07, 2018 at 01:58:20PM -0800, Linus Torvalds wrote:
> I was just hoping that we could play some tricks.
>
> [...]
>
> See what I'm saying?
Clever. Though I'd include the "pushq %rsi" in the macro, to be even more
tricky.
textdata bss dec hex filename
19500
On Wed, Feb 07, 2018 at 01:58:20PM -0800, Linus Torvalds wrote:
> I was just hoping that we could play some tricks.
>
> [...]
>
> See what I'm saying?
Clever. Though I'd include the "pushq %rsi" in the macro, to be even more
tricky.
textdata bss dec hex filename
19500
> Il giorno 07 feb 2018, alle ore 23:18, Jens Axboe ha
> scritto:
>
> On 2/7/18 2:19 PM, Paolo Valente wrote:
>> Commit 'a6a252e64914 ("blk-mq-sched: decide how to handle flush rq via
>> RQF_FLUSH_SEQ")' makes all non-flush re-prepared requests for a device
>> be re-inserted
> Il giorno 07 feb 2018, alle ore 23:18, Jens Axboe ha
> scritto:
>
> On 2/7/18 2:19 PM, Paolo Valente wrote:
>> Commit 'a6a252e64914 ("blk-mq-sched: decide how to handle flush rq via
>> RQF_FLUSH_SEQ")' makes all non-flush re-prepared requests for a device
>> be re-inserted into the active
Dear Nathan & Russel,
I have few more question about vdso for arm-32-bit.
I am using iMX7 board to very VDSO gettimeofday timing.
To make kernel/Documentation/vDSO/vdsotest work on this board, I
commented the device tree reading property:
arm,cpu-registers-not-fw-configured , from the :
Dear Nathan & Russel,
I have few more question about vdso for arm-32-bit.
I am using iMX7 board to very VDSO gettimeofday timing.
To make kernel/Documentation/vDSO/vdsotest work on this board, I
commented the device tree reading property:
arm,cpu-registers-not-fw-configured , from the :
On Fri, Jan 26, 2018 at 09:52:18AM +0100, Lothar Waßmann wrote:
> imx6ull-14x14-evk.dts currently includes the imx6ul.dtsi file for an
> i.MX6ULL SoC which is plain wrong.
>
> Rename the current imx6ul-14x14-evk.dts to .dtsi and include it from
> imx6ul-14x14-evk.dts and imx6ull-14x14-evk.dts, so
On Fri, Jan 26, 2018 at 09:52:18AM +0100, Lothar Waßmann wrote:
> imx6ull-14x14-evk.dts currently includes the imx6ul.dtsi file for an
> i.MX6ULL SoC which is plain wrong.
>
> Rename the current imx6ul-14x14-evk.dts to .dtsi and include it from
> imx6ul-14x14-evk.dts and imx6ull-14x14-evk.dts, so
On Thu, Feb 8, 2018 at 7:51 AM, Ulf Magnusson wrote:
> On Thu, Feb 8, 2018 at 7:35 AM, Ulf Magnusson wrote:
>> On Thu, Feb 8, 2018 at 6:56 AM, Masahiro Yamada
>> wrote:
>>> If stdio is not tty, conf_askvalue() puts
On Thu, Feb 8, 2018 at 7:51 AM, Ulf Magnusson wrote:
> On Thu, Feb 8, 2018 at 7:35 AM, Ulf Magnusson wrote:
>> On Thu, Feb 8, 2018 at 6:56 AM, Masahiro Yamada
>> wrote:
>>> If stdio is not tty, conf_askvalue() puts additional new line to
>>> prevent prompts are all concatenated into a single
* Will Deacon wrote:
> For the sake of avoiding the conflict, can we just drop it for now, please?
Yeah, so I resolved the conflict by merging the (already upstream) bits and
Linus
pulled that resolution. From now on the level of comments you want there is up
to
you!
* Will Deacon wrote:
> For the sake of avoiding the conflict, can we just drop it for now, please?
Yeah, so I resolved the conflict by merging the (already upstream) bits and
Linus
pulled that resolution. From now on the level of comments you want there is up
to
you! :-)
Thanks,
2018-02-08 15:51 GMT+09:00 Ulf Magnusson :
> On Thu, Feb 8, 2018 at 7:35 AM, Ulf Magnusson wrote:
>> On Thu, Feb 8, 2018 at 6:56 AM, Masahiro Yamada
>> wrote:
>>> If stdio is not tty, conf_askvalue() puts additional new
2018-02-08 15:51 GMT+09:00 Ulf Magnusson :
> On Thu, Feb 8, 2018 at 7:35 AM, Ulf Magnusson wrote:
>> On Thu, Feb 8, 2018 at 6:56 AM, Masahiro Yamada
>> wrote:
>>> If stdio is not tty, conf_askvalue() puts additional new line to
>>> prevent prompts are all concatenated into a single line. This
On Thu, Feb 8, 2018 at 7:35 AM, Ulf Magnusson wrote:
> On Thu, Feb 8, 2018 at 6:56 AM, Masahiro Yamada
> wrote:
>> If stdio is not tty, conf_askvalue() puts additional new line to
>> prevent prompts are all concatenated into a single line.
On Thu, Feb 8, 2018 at 7:35 AM, Ulf Magnusson wrote:
> On Thu, Feb 8, 2018 at 6:56 AM, Masahiro Yamada
> wrote:
>> If stdio is not tty, conf_askvalue() puts additional new line to
>> prevent prompts are all concatenated into a single line. This care
>> is missing in conf_choice(), so a 'choice'
the driver reads in the ISR first the IRQpending register,
and clears after that in a write *all* bits in it.
It could happen that the isr register raise bits between
this 2 register accesses, which leads in lost bits ...
In case it clears "TX message sent successfully", the driver
never sends
the driver reads in the ISR first the IRQpending register,
and clears after that in a write *all* bits in it.
It could happen that the isr register raise bits between
this 2 register accesses, which leads in lost bits ...
In case it clears "TX message sent successfully", the driver
never sends
restores the ICS write for rx/tx queue interrupts which was present before
commit 16ecba59bc33 ("e1000e: Do not read ICR in Other interrupt",
v4.5-rc1) but was not restored in commit 4aea7a5c5e94 ("e1000e: Avoid
receiver overrun interrupt bursts", v4.15-rc1).
This re-raises the queue interrupts
Current ifi driver reads first Rx messages, than loopback
the Tx message, if the IFI_CANFD_INTERRUPT_TXFIFO_REMOVE
bit is set. This can lead into the case, that Rx messages
overhelm Tx messages!
Fixed this in the following way:
Set in the IFI_CANFD_TXFIFO_DLC register the FN value to
1, so the
restores the ICS write for rx/tx queue interrupts which was present before
commit 16ecba59bc33 ("e1000e: Do not read ICR in Other interrupt",
v4.5-rc1) but was not restored in commit 4aea7a5c5e94 ("e1000e: Avoid
receiver overrun interrupt bursts", v4.15-rc1).
This re-raises the queue interrupts
Current ifi driver reads first Rx messages, than loopback
the Tx message, if the IFI_CANFD_INTERRUPT_TXFIFO_REMOVE
bit is set. This can lead into the case, that Rx messages
overhelm Tx messages!
Fixed this in the following way:
Set in the IFI_CANFD_TXFIFO_DLC register the FN value to
1, so the
On Mon, Jan 22, 2018 at 07:07:47AM -0800, Andrey Smirnov wrote:
> Platform device core assumes the ownership of dev.platform_data as
> well as that it is dynamically allocated and it will try to kfree it
> as a part of platform_device_release(). Change the code to pass
> kzalloc'ed chunk of memory
On Mon, Jan 22, 2018 at 07:07:47AM -0800, Andrey Smirnov wrote:
> Platform device core assumes the ownership of dev.platform_data as
> well as that it is dynamically allocated and it will try to kfree it
> as a part of platform_device_release(). Change the code to pass
> kzalloc'ed chunk of memory
This partially reverts commit 4aea7a5c5e940c1723add439f4088844cd26196d.
We keep the fix for the first part of the problem (1) described in the log
of that commit, that is to read ICR in the other interrupt handler. We
remove the fix for the second part of the problem (2), Other interrupt
The 82574 specification update errata 12 states that interrupts may be
missed if ICR is read while INT_ASSERTED is not set. Avoid that problem by
setting all bits related to events that can trigger the Other interrupt in
IMS.
The Other interrupt is raised for such events regardless of whether or
This partially reverts commit 4aea7a5c5e940c1723add439f4088844cd26196d.
We keep the fix for the first part of the problem (1) described in the log
of that commit, that is to read ICR in the other interrupt handler. We
remove the fix for the second part of the problem (2), Other interrupt
The 82574 specification update errata 12 states that interrupts may be
missed if ICR is read while INT_ASSERTED is not set. Avoid that problem by
setting all bits related to events that can trigger the Other interrupt in
IMS.
The Other interrupt is raised for such events regardless of whether or
On Mon, Feb 05, 2018 at 06:08:40PM +0100, Sebastian Reichel wrote:
> From: Peter Senna Tschudin
>
> Enable secure debug enable register access for Bx50v3 devices to enable
> PMU and hardware counters for perf.
>
> Signed-off-by: Peter Senna Tschudin
On Mon, Feb 05, 2018 at 06:08:40PM +0100, Sebastian Reichel wrote:
> From: Peter Senna Tschudin
>
> Enable secure debug enable register access for Bx50v3 devices to enable
> PMU and hardware counters for perf.
>
> Signed-off-by: Peter Senna Tschudin
> Signed-off-by: Sebastian Reichel
> ---
>
mpls_label_ok() validates that the 'platform_label' array index from a
userspace netlink message payload is valid. Under speculation the
mpls_label_ok() result may not resolve in the CPU pipeline until after
the index is used to access an array element. Sanitize the index to zero
to prevent
mpls_label_ok() validates that the 'platform_label' array index from a
userspace netlink message payload is valid. Under speculation the
mpls_label_ok() result may not resolve in the CPU pipeline until after
the index is used to access an array element. Sanitize the index to zero
to prevent
On 2018/01/29 09:22, Alexander Duyck wrote:
[...]
>
> > Consequently, we must clear OTHER manually from ICR, otherwise the
> > interrupt is immediately re-raised after exiting the handler.
> >
> > These observations are the same whether the interrupt is triggered via a
> > write to ICS or in
On 2018/01/29 09:22, Alexander Duyck wrote:
[...]
>
> > Consequently, we must clear OTHER manually from ICR, otherwise the
> > interrupt is immediately re-raised after exiting the handler.
> >
> > These observations are the same whether the interrupt is triggered via a
> > write to ICS or in
ALIGN(8) is superfluous since macro TEXT_TEXT already has one.
bonus: indentation fix, spaces -> tab.
Signed-off-by: Cao jin
---
arch/x86/kernel/vmlinux.lds.S | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/arch/x86/kernel/vmlinux.lds.S
ALIGN(8) is superfluous since macro TEXT_TEXT already has one.
bonus: indentation fix, spaces -> tab.
Signed-off-by: Cao jin
---
arch/x86/kernel/vmlinux.lds.S | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/arch/x86/kernel/vmlinux.lds.S b/arch/x86/kernel/vmlinux.lds.S
Dear Mario,
Am 08.02.2018 um 05:57 schrieb mario.limoncie...@dell.com:
-Original Message-
From: Paul Menzel [mailto:pmenzel+platform-driver-...@molgen.mpg.de]
Sent: Wednesday, February 7, 2018 3:41 AM
To: Limonciello, Mario
Cc: Pali Rohár
Dear Mario,
Am 08.02.2018 um 05:57 schrieb mario.limoncie...@dell.com:
-Original Message-
From: Paul Menzel [mailto:pmenzel+platform-driver-...@molgen.mpg.de]
Sent: Wednesday, February 7, 2018 3:41 AM
To: Limonciello, Mario
Cc: Pali Rohár ; it+platform-driver-...@molgen.mpg.de;
On Thu, Feb 8, 2018 at 6:56 AM, Masahiro Yamada
wrote:
> If stdio is not tty, conf_askvalue() puts additional new line to
> prevent prompts are all concatenated into a single line. This care
> is missing in conf_choice(), so a 'choice' prompt and the next prompt
>
On Thu, Feb 8, 2018 at 6:56 AM, Masahiro Yamada
wrote:
> If stdio is not tty, conf_askvalue() puts additional new line to
> prevent prompts are all concatenated into a single line. This care
> is missing in conf_choice(), so a 'choice' prompt and the next prompt
> are shown in the same line.
>
>
A user with i386 instead of AMD64 machine reports [1] that commit 19809c2da28a
("mm, vmalloc: use __GFP_HIGHMEM implicitly”) causes a regression.
BUG_ON(PageHighMem(pg)) in drivers/media/common/saa7146/saa7146_core.c always
gets triggered after that commit.
Commit 704b862f9efd ("mm/vmalloc.c:
A user with i386 instead of AMD64 machine reports [1] that commit 19809c2da28a
("mm, vmalloc: use __GFP_HIGHMEM implicitly”) causes a regression.
BUG_ON(PageHighMem(pg)) in drivers/media/common/saa7146/saa7146_core.c always
gets triggered after that commit.
Commit 704b862f9efd ("mm/vmalloc.c:
2018-02-08 0:57 GMT+08:00 Jim Mattson :
> vmcs12->host_cr[34] does not contain the up-to-date values when L1 is
> running. L1 can vmwrite any values there. We know at this point that
It will incur a vmexit to emulate L1 vmwrites vmcs12->host_cr[34] even
if vmcs shadow is
2018-02-08 0:57 GMT+08:00 Jim Mattson :
> vmcs12->host_cr[34] does not contain the up-to-date values when L1 is
> running. L1 can vmwrite any values there. We know at this point that
It will incur a vmexit to emulate L1 vmwrites vmcs12->host_cr[34] even
if vmcs shadow is enabled since host_cr[34]
On Thu, Feb 8, 2018 at 6:56 AM, Masahiro Yamada
wrote:
> Except silentoldconfig, valid_stdin is 1, so check_stdin() is no-op.
>
> oldconfig and silentoldconfig work almost in the same way except that
> the latter generates additional files. Both ask users for input
On Thu, Feb 8, 2018 at 6:56 AM, Masahiro Yamada
wrote:
> Except silentoldconfig, valid_stdin is 1, so check_stdin() is no-op.
>
> oldconfig and silentoldconfig work almost in the same way except that
> the latter generates additional files. Both ask users for input for
> new symbols.
>
> I do
On 02/07/18 06:45, Takashi Iwai wrote:
> On Mon, 29 Jan 2018 06:37:55 +0100,
> Kirill Marinushkin wrote:
>> The layout of the UAC2 Control request and response varies depending on
>> the request type. With the current implementation, only the Layout 2
>> Parameter Block (with the 2-byte sized
On 02/07/18 06:45, Takashi Iwai wrote:
> On Mon, 29 Jan 2018 06:37:55 +0100,
> Kirill Marinushkin wrote:
>> The layout of the UAC2 Control request and response varies depending on
>> the request type. With the current implementation, only the Layout 2
>> Parameter Block (with the 2-byte sized
Hi Rob,
On 8 February 2018 at 05:19, Rob Herring wrote:
> On Mon, Feb 05, 2018 at 09:55:10AM +0800, Baolin Wang wrote:
>> This patch adds the device tree bindings for the Spreadtrum
>> GPIO controller. The gpios will be supported by the GPIO
>> generic library.
>>
>>
Hi Rob,
On 8 February 2018 at 05:19, Rob Herring wrote:
> On Mon, Feb 05, 2018 at 09:55:10AM +0800, Baolin Wang wrote:
>> This patch adds the device tree bindings for the Spreadtrum
>> GPIO controller. The gpios will be supported by the GPIO
>> generic library.
>>
>> Signed-off-by: Baolin Wang
On Thu, 8 Feb 2018 07:35:39 +1100
Stephen Rothwell wrote:
> Commit
>
> b175210bd231 ("s390/kconfig: Remove ARCH_WANTS_PROT_NUMA_PROT_NONE select")
>
> is missing a Signed-off-by from its committer.
It is always that "last" one you add. Fixed. Thanks.
--
blue skies,
On Thu, 8 Feb 2018 07:35:39 +1100
Stephen Rothwell wrote:
> Commit
>
> b175210bd231 ("s390/kconfig: Remove ARCH_WANTS_PROT_NUMA_PROT_NONE select")
>
> is missing a Signed-off-by from its committer.
It is always that "last" one you add. Fixed. Thanks.
--
blue skies,
Martin.
"Reality
Hi Linus,
Ben missed sending his tree, but he really didn't have much stuff in
it, GP108 acceleration support is enabled by "secure boot" support,
some clockgating work on Kepler, and bunch of fixes. The main bulk is
regenerated firmware files, the change to them really isn't that
large.
Hi Linus,
Ben missed sending his tree, but he really didn't have much stuff in
it, GP108 acceleration support is enabled by "secure boot" support,
some clockgating work on Kepler, and bunch of fixes. The main bulk is
regenerated firmware files, the change to them really isn't that
large.
2018-02-08 8:34 GMT+09:00 Ulf Magnusson :
> On Tue, Feb 6, 2018 at 1:34 AM, Masahiro Yamada
> wrote:
>> If stdout is redirected to a file, prompts look differently due to
>> missing new lines.
>>
>> Currently, conf_askvalue() takes care of this
2018-02-08 8:34 GMT+09:00 Ulf Magnusson :
> On Tue, Feb 6, 2018 at 1:34 AM, Masahiro Yamada
> wrote:
>> If stdout is redirected to a file, prompts look differently due to
>> missing new lines.
>>
>> Currently, conf_askvalue() takes care of this by putting additional
>> new line, but conf_choice()
If stdio is not tty, conf_askvalue() puts additional new line to
prevent prompts are all concatenated into a single line. This care
is missing in conf_choice(), so a 'choice' prompt and the next prompt
are shown in the same line.
Move the code into xfgets() to take care of all cases. To improve
Except silentoldconfig, valid_stdin is 1, so check_stdin() is no-op.
oldconfig and silentoldconfig work almost in the same way except that
the latter generates additional files. Both ask users for input for
new symbols.
I do not know why only silentoldconfig requires stdio be tty.
$ rm -f
If stdio is not tty, conf_askvalue() puts additional new line to
prevent prompts are all concatenated into a single line. This care
is missing in conf_choice(), so a 'choice' prompt and the next prompt
are shown in the same line.
Move the code into xfgets() to take care of all cases. To improve
Except silentoldconfig, valid_stdin is 1, so check_stdin() is no-op.
oldconfig and silentoldconfig work almost in the same way except that
the latter generates additional files. Both ask users for input for
new symbols.
I do not know why only silentoldconfig requires stdio be tty.
$ rm -f
On Wed, 2018-02-07 at 16:18 +0100, Matthias Brugger wrote:
>
> On 02/05/2018 05:07 AM, Ryder Lee wrote:
> > On Sat, 2018-02-03 at 15:26 +0100, Matthias Brugger wrote:
> >>
> >> On 01/31/2018 08:42 AM, Ryder Lee wrote:
> >>> As the new MFD parent is in place, switch probing method to adapt it.
>
On Wed, 2018-02-07 at 16:18 +0100, Matthias Brugger wrote:
>
> On 02/05/2018 05:07 AM, Ryder Lee wrote:
> > On Sat, 2018-02-03 at 15:26 +0100, Matthias Brugger wrote:
> >>
> >> On 01/31/2018 08:42 AM, Ryder Lee wrote:
> >>> As the new MFD parent is in place, switch probing method to adapt it.
>
On Wed, 2018-02-07 at 18:49 -0600, Rob Herring wrote:
> >> > diff --git
> >> > a/Documentation/devicetree/bindings/arm/mediatek/mediatek,audsys.txt
> >> > b/Documentation/devicetree/bindings/arm/mediatek/mediatek,audsys.txt
> >> > index 9b8f578..677af40 100644
> >> > ---
On Wed, 2018-02-07 at 18:49 -0600, Rob Herring wrote:
> >> > diff --git
> >> > a/Documentation/devicetree/bindings/arm/mediatek/mediatek,audsys.txt
> >> > b/Documentation/devicetree/bindings/arm/mediatek/mediatek,audsys.txt
> >> > index 9b8f578..677af40 100644
> >> > ---
The 5lvl.c test file was incorporated into another one in
selftests/vm (va_128TBswitch.c) in commit 235266b8.
Signed-off-by: Daniel Díaz
---
tools/testing/selftests/x86/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
The 5lvl.c test file was incorporated into another one in
selftests/vm (va_128TBswitch.c) in commit 235266b8.
Signed-off-by: Daniel Díaz
---
tools/testing/selftests/x86/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/x86/Makefile
Hi Steve,
On Fri, Feb 02, 2018 at 06:05:02PM -0500, Steven Rostedt wrote:
> From: "Steven Rostedt (VMware)"
>
> Add function to get the function arguments from pt_regs.
>
> Signed-off-by: Steven Rostedt (VMware)
> ---
> arch/x86/kernel/ftrace.c | 28
Hi Steve,
On Fri, Feb 02, 2018 at 06:05:02PM -0500, Steven Rostedt wrote:
> From: "Steven Rostedt (VMware)"
>
> Add function to get the function arguments from pt_regs.
>
> Signed-off-by: Steven Rostedt (VMware)
> ---
> arch/x86/kernel/ftrace.c | 28
> 1 file
Without btcoex_enable, WiFi activies make both WiFi and Bluetooth
unstable if there's a bluetooth connection.
Enable this option when bt_ant_diversity is disabled.
BugLink: https://bugs.launchpad.net/bugs/1746164
Signed-off-by: Kai-Heng Feng
---
Without btcoex_enable, WiFi activies make both WiFi and Bluetooth
unstable if there's a bluetooth connection.
Enable this option when bt_ant_diversity is disabled.
BugLink: https://bugs.launchpad.net/bugs/1746164
Signed-off-by: Kai-Heng Feng
---
drivers/net/wireless/ath/ath9k/init.c | 10
On 2/3/2018 3:21 AM, Bjorn Andersson wrote:
On Thu 18 Jan 00:05 PST 2018, Vijay Viswanath wrote:
From: Krishna Konda
The PADs for sdhc controller are dual-voltage that support 3v/1.8v.
Those PADs have a control signal (io_pad_pwr_switch/mode18 ) that
indicates
On 2/3/2018 3:21 AM, Bjorn Andersson wrote:
On Thu 18 Jan 00:05 PST 2018, Vijay Viswanath wrote:
From: Krishna Konda
The PADs for sdhc controller are dual-voltage that support 3v/1.8v.
Those PADs have a control signal (io_pad_pwr_switch/mode18 ) that
indicates whether the PAD works in 3v
On Wed, Feb 7, 2018 at 5:22 AM, Daniel Díaz wrote:
> The Makefile lacks a couple of line continuation backslashes
> in an `if' clause, which can make the subsequent rsync
> command go awry over the whole filesystem (`rsync -a / /`).
>
> /bin/sh: -c: line 5: syntax error:
On Wed, Feb 7, 2018 at 5:22 AM, Daniel Díaz wrote:
> The Makefile lacks a couple of line continuation backslashes
> in an `if' clause, which can make the subsequent rsync
> command go awry over the whole filesystem (`rsync -a / /`).
>
> /bin/sh: -c: line 5: syntax error: unexpected end of file
On Wed, Feb 7, 2018 at 10:46 PM, Daniel Díaz Rodríguez
wrote:
> Hello!
>
>
> On 7 February 2018 at 00:01, Pintu Kumar wrote:
> [...]
>> Thanks for your patch.
>> However, I have copied this Makefile from
>> tools/testing/selftests/futex/Makefile
On Wed, Feb 7, 2018 at 10:46 PM, Daniel Díaz Rodríguez
wrote:
> Hello!
>
>
> On 7 February 2018 at 00:01, Pintu Kumar wrote:
> [...]
>> Thanks for your patch.
>> However, I have copied this Makefile from
>> tools/testing/selftests/futex/Makefile before modifying it.
>> If there is a problem with
Although L2 is in halt state, it will be in the active state after
VM entry if the VM entry is vectoring. Halting the vcpu here means
the event won't be injected to L2 and this decision isn't reported
to L1. Thus L0 drops an event that should be injected to L2.
Because virtual interrupt delivery
Although L2 is in halt state, it will be in the active state after
VM entry if the VM entry is vectoring. Halting the vcpu here means
the event won't be injected to L2 and this decision isn't reported
to L1. Thus L0 drops an event that should be injected to L2.
Because virtual interrupt delivery
1 - 100 of 1730 matches
Mail list logo