Re: [PATCH 1/2] crypto: caam: Delete an error message for a failed memory allocation in seven functions

On 2/14/2018 8:31 PM, SF Markus Elfring wrote: > From: Markus Elfring > Date: Wed, 14 Feb 2018 18:22:38 +0100 > > Omit an extra message for a memory allocation failure in these functions. > > This issue was detected by using the Coccinelle software. > >

Re: [PATCH 1/2] crypto: caam: Delete an error message for a failed memory allocation in seven functions

On 2/14/2018 8:31 PM, SF Markus Elfring wrote: > From: Markus Elfring > Date: Wed, 14 Feb 2018 18:22:38 +0100 > > Omit an extra message for a memory allocation failure in these functions. > > This issue was detected by using the Coccinelle software. > > Signed-off-by: Markus Elfring

Re: [PATCH 2/2] usb: dwc3: drd: Fix lock-up on ID change during system suspend/resume

Felipe, On 25/01/18 18:11, Roger Quadros wrote: > Hi, > > On 24/01/18 14:19, Roger Quadros wrote: >> On 23/01/18 14:41, Roger Quadros wrote: >>> Hi Manu, >>> >>> On 23/01/18 05:45, Manu Gautam wrote: Hi, On 1/22/2018 6:31 PM, Roger Quadros wrote: > Adding/removing

Re: [PATCH 2/2] usb: dwc3: drd: Fix lock-up on ID change during system suspend/resume

Felipe, On 25/01/18 18:11, Roger Quadros wrote: > Hi, > > On 24/01/18 14:19, Roger Quadros wrote: >> On 23/01/18 14:41, Roger Quadros wrote: >>> Hi Manu, >>> >>> On 23/01/18 05:45, Manu Gautam wrote: Hi, On 1/22/2018 6:31 PM, Roger Quadros wrote: > Adding/removing

Re: [PATCH 0/4] usb: dwc3: Add dual-role support using OTG core

Hi Felipe, On 22/01/18 15:11, Roger Quadros wrote: > Hi Felipe, > > Some platforms (e.g. TI's AM437x) don't have USB ID pin state available > over GPIO/extcon but need to rely on the DWC3 core's OTG block to > get the ID pin state instead. > > This series implements simple dual-role

Re: [PATCH 0/4] usb: dwc3: Add dual-role support using OTG core

Hi Felipe, On 22/01/18 15:11, Roger Quadros wrote: > Hi Felipe, > > Some platforms (e.g. TI's AM437x) don't have USB ID pin state available > over GPIO/extcon but need to rely on the DWC3 core's OTG block to > get the ID pin state instead. > > This series implements simple dual-role

Re: [alsa-devel] [PATCH] ASoC: dmic: Add optional wakeup delay

On 2018-02-15 01:51, Matthias Kaehlcke wrote: > On some systems a delay is needed after switching on the clocks, to allow > the DMIC output to stabilize and avoid a popping noise at the beginning > of the recording. Add the optional device tree property 'wakeup-delay-ms' > and apply the

Re: [alsa-devel] [PATCH] ASoC: dmic: Add optional wakeup delay

On 2018-02-15 01:51, Matthias Kaehlcke wrote: > On some systems a delay is needed after switching on the clocks, to allow > the DMIC output to stabilize and avoid a popping noise at the beginning > of the recording. Add the optional device tree property 'wakeup-delay-ms' > and apply the

Re: [PATCH 1/4] rtc: isl1208: Fix unintended clear of SR bits

Am Mittwoch, den 14.02.2018, 21:26 +0100 schrieb Alexandre Belloni: > On 23/01/2018 at 13:17:58 +0100, Michael Grzeschik wrote: > > > > From: Denis Osterland > > > > After successful > > sr = isl1208_i2c_set_regs(client, 0, regs, ISL1208_RTC_SECTION_LEN); > > sr will

Re: [PATCH 1/4] rtc: isl1208: Fix unintended clear of SR bits

Am Mittwoch, den 14.02.2018, 21:26 +0100 schrieb Alexandre Belloni: > On 23/01/2018 at 13:17:58 +0100, Michael Grzeschik wrote: > > > > From: Denis Osterland > > > > After successful > > sr = isl1208_i2c_set_regs(client, 0, regs, ISL1208_RTC_SECTION_LEN); > > sr will be 0. > > As a result > >

Re: [PATCH V2] lib/scatterlist: Add SG_CHAIN and SG_END macros for LSB encodings

Quoting Anshuman Khandual (2018-02-15 03:33:56) > This replaces scatterlist->page_link LSB encodings with SG_CHAIN and > SG_END definitions without any functional change. > > Signed-off-by: Anshuman Khandual > --- > Changes in V2: > - Changed SG_EMARK as SG_END as

Re: [dm-devel] DM Regression in 4.16-rc1 - read() returns data when it shouldn't

On 02/15/2018 01:07 AM, NeilBrown wrote: > > And looking again at the code, it doesn't seem so bad. I was worried > about reassigning ci.io->orig_bio after calling > __split_and_process_non_flush(), but the important thing is to set it > before the last dec_pending() call, and the code gets that

Re: [PATCH V2] lib/scatterlist: Add SG_CHAIN and SG_END macros for LSB encodings

Quoting Anshuman Khandual (2018-02-15 03:33:56) > This replaces scatterlist->page_link LSB encodings with SG_CHAIN and > SG_END definitions without any functional change. > > Signed-off-by: Anshuman Khandual > --- > Changes in V2: > - Changed SG_EMARK as SG_END as per Johannes and Tvrtko > -

Re: [dm-devel] DM Regression in 4.16-rc1 - read() returns data when it shouldn't

On 02/15/2018 01:07 AM, NeilBrown wrote: > > And looking again at the code, it doesn't seem so bad. I was worried > about reassigning ci.io->orig_bio after calling > __split_and_process_non_flush(), but the important thing is to set it > before the last dec_pending() call, and the code gets that

Re: [PATCH 18/20] iwlwifi: fix malformed CONFIG_IWLWIFI_PCIE_RTPM default

On Mon, 2018-02-05 at 02:21 +0100, Ulf Magnusson wrote: > 'default false' should be 'default n', though they happen to have the > same effect here, due to undefined symbols ('false' in this case) > evaluating to n in a tristate sense. > > Remove the default instead of changing it. bool and

Re: [PATCH 18/20] iwlwifi: fix malformed CONFIG_IWLWIFI_PCIE_RTPM default

On Mon, 2018-02-05 at 02:21 +0100, Ulf Magnusson wrote: > 'default false' should be 'default n', though they happen to have the > same effect here, due to undefined symbols ('false' in this case) > evaluating to n in a tristate sense. > > Remove the default instead of changing it. bool and

[PATCH] extcon: intel-cht-wc: Also set direction and drv flags for V5 boost GPIO

Sometimes (firmware bug?) the V5 boost GPIO is not configured as output by the BIOS, leading to the 5V boost convertor being permanently on, Explicitly set the direction and drv flags rather then inheriting them from the firmware to fix this. Signed-off-by: Hans de Goede

[PATCH] extcon: intel-cht-wc: Also set direction and drv flags for V5 boost GPIO

Sometimes (firmware bug?) the V5 boost GPIO is not configured as output by the BIOS, leading to the 5V boost convertor being permanently on, Explicitly set the direction and drv flags rather then inheriting them from the firmware to fix this. Signed-off-by: Hans de Goede ---

[PATCH] rtl8187: Fix NULL pointer dereference in priv->conf_mutex

This can be reproduced by bind/unbind the driver multiple times in AM3517 board. Analysis revealed that rtl8187_start() was invoked before probe finishes(ie. before the mutex is initialized). INFO: trying to register non-static key. the code is fine but needs lockdep annotation. turning off

[PATCH] rtl8187: Fix NULL pointer dereference in priv->conf_mutex

This can be reproduced by bind/unbind the driver multiple times in AM3517 board. Analysis revealed that rtl8187_start() was invoked before probe finishes(ie. before the mutex is initialized). INFO: trying to register non-static key. the code is fine but needs lockdep annotation. turning off

Re: [PATCH] powerpc/xmon: Dont register sysrq key when kernel param xmon=off

Thanks for looking into this patch Mpe. Michael Ellerman writes: > > > But the same crash happens with XMON_DEFAULT=n and nothing on the > command line. Yes, XMON_DEFAULT=n and empty boot command line implies xmon=off hence you will see the same issue and this patch should

Re: [PATCH] powerpc/xmon: Dont register sysrq key when kernel param xmon=off

Thanks for looking into this patch Mpe. Michael Ellerman writes: > > > But the same crash happens with XMON_DEFAULT=n and nothing on the > command line. Yes, XMON_DEFAULT=n and empty boot command line implies xmon=off hence you will see the same issue and this patch should fix that issue too.

Re: [RFC PATCH ghak21 1/4] audit: make ANOM_LINK obey audit_enabled and audit_dummy_context

On Wed, Feb 14, 2018 at 6:33 PM, Richard Guy Briggs wrote: > On 2018-02-14 09:51, Kees Cook wrote: >> On Wed, Feb 14, 2018 at 8:18 AM, Richard Guy Briggs wrote: >> > Audit link denied events emit disjointed records when audit is disabled. >> > No records should

Re: [RFC PATCH ghak21 1/4] audit: make ANOM_LINK obey audit_enabled and audit_dummy_context

On Wed, Feb 14, 2018 at 6:33 PM, Richard Guy Briggs wrote: > On 2018-02-14 09:51, Kees Cook wrote: >> On Wed, Feb 14, 2018 at 8:18 AM, Richard Guy Briggs wrote: >> > Audit link denied events emit disjointed records when audit is disabled. >> > No records should be emitted when audit is disabled.

[PATCH v11 02/10] arm: omap: timer: Wrap the inline functions under OMAP2PLUS define

Wrap the inline functions under OMAP2PLUS/OMAP1 defines. This patch also inlines omap_dm_timer_get_fclk function for non OMAP1 Config. Signed-off-by: Keerthy Tested-by: Ladislav Michl Reviewed-by: Sebastian Reichel ---

[PATCH v11 02/10] arm: omap: timer: Wrap the inline functions under OMAP2PLUS define

Wrap the inline functions under OMAP2PLUS/OMAP1 defines. This patch also inlines omap_dm_timer_get_fclk function for non OMAP1 Config. Signed-off-by: Keerthy Tested-by: Ladislav Michl Reviewed-by: Sebastian Reichel --- arch/arm/plat-omap/include/plat/dmtimer.h | 17 - 1 file

[PATCH v11 10/10] arm: omap: pdata-quirks: Remove unused timer pdata

Remove unused timer pdata. Signed-off-by: Keerthy Reviewed-by: Sebastian Reichel Tested-by: Ladislav Michl --- arch/arm/mach-omap2/pdata-quirks.c | 32 1 file changed, 32 deletions(-)

[PATCH v11 10/10] arm: omap: pdata-quirks: Remove unused timer pdata

Remove unused timer pdata. Signed-off-by: Keerthy Reviewed-by: Sebastian Reichel Tested-by: Ladislav Michl --- arch/arm/mach-omap2/pdata-quirks.c | 32 1 file changed, 32 deletions(-) diff --git a/arch/arm/mach-omap2/pdata-quirks.c

[PATCH v11 06/10] timer-ti-dm: Add timer ops to the platform data structure

Add timer ops to the platform data structure Signed-off-by: Keerthy Reviewed-by: Sebastian Reichel Tested-by: Ladislav Michl --- include/linux/platform_data/dmtimer-omap.h | 38 ++ 1 file

[PATCH v11 06/10] timer-ti-dm: Add timer ops to the platform data structure

Add timer ops to the platform data structure Signed-off-by: Keerthy Reviewed-by: Sebastian Reichel Tested-by: Ladislav Michl --- include/linux/platform_data/dmtimer-omap.h | 38 ++ 1 file changed, 38 insertions(+) diff --git

[PATCH v11 09/10] pwm: pwm-omap-dmtimer: Adapt driver to utilize dmtimer pdata ops

Adapt driver to utilize dmtimer pdata ops instead of pdata-quirks. Signed-off-by: Keerthy Acked-by: Neil Armstrong Reviewed-by: Claudiu Beznea --- drivers/pwm/pwm-omap-dmtimer.c | 68

[PATCH v11 08/10] clocksource: timer-ti-dm: Hook device platform data if not already assigned

From: Ladislav Michl In the case of device tree boot the device platform data is usually NULL so hook the platform data obtained from the match. As part of un-constify the platform_data pointer. Signed-off-by: Ladislav Michl Signed-off-by: Keerthy

[PATCH v11 09/10] pwm: pwm-omap-dmtimer: Adapt driver to utilize dmtimer pdata ops

Adapt driver to utilize dmtimer pdata ops instead of pdata-quirks. Signed-off-by: Keerthy Acked-by: Neil Armstrong Reviewed-by: Claudiu Beznea --- drivers/pwm/pwm-omap-dmtimer.c | 68 ++ 1 file changed, 42 insertions(+), 26 deletions(-) diff --git

[PATCH v11 08/10] clocksource: timer-ti-dm: Hook device platform data if not already assigned

From: Ladislav Michl In the case of device tree boot the device platform data is usually NULL so hook the platform data obtained from the match. As part of un-constify the platform_data pointer. Signed-off-by: Ladislav Michl Signed-off-by: Keerthy Reviewed-by: Sebastian Reichel ---

[PATCH v11 05/10] arm: OMAP: Move dmtimer driver out of plat-omap to drivers under clocksource

Move the dmtimer driver out of plat-omap to clocksource. So that non-omap devices also could use this. No Code changes done to the driver file only renamed to timer-ti-dm.c. Also removed the config dependencies for OMAP_DM_TIMER. Signed-off-by: Keerthy Reviewed-by: Sebastian

[PATCH v11 01/10] clocksource: dmtimer: Remove all the exports

Remove all the unwanted exports from the driver Signed-off-by: Keerthy Reviewed-by: Sebastian Reichel Tested-by: Ladislav Michl --- arch/arm/plat-omap/dmtimer.c | 27 --- 1 file changed, 27

[PATCH v11 05/10] arm: OMAP: Move dmtimer driver out of plat-omap to drivers under clocksource

Move the dmtimer driver out of plat-omap to clocksource. So that non-omap devices also could use this. No Code changes done to the driver file only renamed to timer-ti-dm.c. Also removed the config dependencies for OMAP_DM_TIMER. Signed-off-by: Keerthy Reviewed-by: Sebastian Reichel Tested-by:

[PATCH v11 01/10] clocksource: dmtimer: Remove all the exports

Remove all the unwanted exports from the driver Signed-off-by: Keerthy Reviewed-by: Sebastian Reichel Tested-by: Ladislav Michl --- arch/arm/plat-omap/dmtimer.c | 27 --- 1 file changed, 27 deletions(-) diff --git a/arch/arm/plat-omap/dmtimer.c

[PATCH v11 03/10] arm: omap: Move dmtimer.h out of plat-omap

The header file is currently under plat-omap directory under arch/omap. Move this out to an accessible place. No Code changes done to the header file and renamed to timer-ti-dm.h. Signed-off-by: Keerthy Reviewed-by: Sebastian Reichel

[PATCH v11 03/10] arm: omap: Move dmtimer.h out of plat-omap

The header file is currently under plat-omap directory under arch/omap. Move this out to an accessible place. No Code changes done to the header file and renamed to timer-ti-dm.h. Signed-off-by: Keerthy Reviewed-by: Sebastian Reichel Tested-by: Ladislav Michl --- arch/arm/mach-omap1/pm.c

[PATCH v11 07/10] clocksource: timer-ti-dm: Populate the timer ops to the pdata

Add the timer ops to the platform data Signed-off-by: Keerthy Reviewed-by: Sebastian Reichel Tested-by: Ladislav Michl --- drivers/clocksource/timer-ti-dm.c | 25 + 1 file changed, 25

[PATCH v11 07/10] clocksource: timer-ti-dm: Populate the timer ops to the pdata

Add the timer ops to the platform data Signed-off-by: Keerthy Reviewed-by: Sebastian Reichel Tested-by: Ladislav Michl --- drivers/clocksource/timer-ti-dm.c | 25 + 1 file changed, 25 insertions(+) diff --git a/drivers/clocksource/timer-ti-dm.c

[PATCH v11 04/10] clocksource: timer-ti-dm: Replace architecture

Replace architecture specific guard with clocksource guard. Signed-off-by: Keerthy Replace architecture specific defines with clocksource --- include/clocksource/timer-ti-dm.h | 8 +++- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git

[PATCH v11 04/10] clocksource: timer-ti-dm: Replace architecture

Replace architecture specific guard with clocksource guard. Signed-off-by: Keerthy Replace architecture specific defines with clocksource --- include/clocksource/timer-ti-dm.h | 8 +++- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/include/clocksource/timer-ti-dm.h

[PATCH v11 00/10] omap: dmtimer: Move driver out of plat-omap

The series moves dmtimer out of plat-omap to drivers/clocksource. The series also does a bunch of changes to pwm-omap-dmtimer code to adapt to the driver migration and clean up plat specific pdata-quirks and use the dmtimer platform data. Boot tested on DRA7-EVM and AM437X-GP-EVM. Compile tested

[PATCH v11 00/10] omap: dmtimer: Move driver out of plat-omap

The series moves dmtimer out of plat-omap to drivers/clocksource. The series also does a bunch of changes to pwm-omap-dmtimer code to adapt to the driver migration and clean up plat specific pdata-quirks and use the dmtimer platform data. Boot tested on DRA7-EVM and AM437X-GP-EVM. Compile tested

Re: [GIT PULL] x86 PTI and Spectre related fixes and updates

On Wed, Feb 14, 2018 at 05:17:25PM -0800, Linus Torvalds wrote: > On Wed, Feb 14, 2018 at 4:38 PM, Ingo Molnar wrote: > > > >This tree generates two relatively simple conflicts with your tree: > > So what annoys me about these conflicts is that I'm not convinced that > the

Re: [GIT PULL] x86 PTI and Spectre related fixes and updates

On Wed, Feb 14, 2018 at 05:17:25PM -0800, Linus Torvalds wrote: > On Wed, Feb 14, 2018 at 4:38 PM, Ingo Molnar wrote: > > > >This tree generates two relatively simple conflicts with your tree: > > So what annoys me about these conflicts is that I'm not convinced that > the stable tree

Re: [PATCH] x86/mm/kaiser: avoid 32-bit/PAE build warning

On Wed, Feb 14, 2018 at 11:12:24PM +0100, Arnd Bergmann wrote: > On Wed, Dec 6, 2017 at 4:08 PM, Dave Hansen > wrote: > > On 12/06/2017 07:03 AM, Arnd Bergmann wrote: > >> On Wed, Dec 6, 2017 at 3:15 PM, Arnd Bergmann wrote: > >> > >>> This changes

Re: [PATCH] x86/mm/kaiser: avoid 32-bit/PAE build warning

On Wed, Feb 14, 2018 at 11:12:24PM +0100, Arnd Bergmann wrote: > On Wed, Dec 6, 2017 at 4:08 PM, Dave Hansen > wrote: > > On 12/06/2017 07:03 AM, Arnd Bergmann wrote: > >> On Wed, Dec 6, 2017 at 3:15 PM, Arnd Bergmann wrote: > >> > >>> This changes the type to u64 in the

[PATCH v3 4/4] of: improve reporting invalid overlay target path

From: Frank Rowand Errors while developing the patch to create of_overlay_fdt_apply() exposed inadequate error messages to debug problems when overlay devicetree fragment nodes contain an invalid target path. Improve the messages in find_target_node() to remedy this.

[PATCH v3 4/4] of: improve reporting invalid overlay target path

From: Frank Rowand Errors while developing the patch to create of_overlay_fdt_apply() exposed inadequate error messages to debug problems when overlay devicetree fragment nodes contain an invalid target path. Improve the messages in find_target_node() to remedy this. Signed-off-by: Frank

[PATCH v3 2/4] of: Documentation: of_overlay_apply() replaced by of_overlay_fdt_apply()

From: Frank Rowand Signed-off-by: Frank Rowand --- Documentation/devicetree/overlay-notes.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/devicetree/overlay-notes.txt

[PATCH v3 1/4] of: change overlay apply input data from unflattened to FDT

From: Frank Rowand Move duplicating and unflattening of an overlay flattened devicetree (FDT) into the overlay application code. To accomplish this, of_overlay_apply() is replaced by of_overlay_fdt_apply(). The copy of the FDT (aka "duplicate FDT") now belongs to

[PATCH v3 2/4] of: Documentation: of_overlay_apply() replaced by of_overlay_fdt_apply()

From: Frank Rowand Signed-off-by: Frank Rowand --- Documentation/devicetree/overlay-notes.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/devicetree/overlay-notes.txt b/Documentation/devicetree/overlay-notes.txt index c4aa0adf13ec..5175a24d387e 100644

[PATCH v3 1/4] of: change overlay apply input data from unflattened to FDT

From: Frank Rowand Move duplicating and unflattening of an overlay flattened devicetree (FDT) into the overlay application code. To accomplish this, of_overlay_apply() is replaced by of_overlay_fdt_apply(). The copy of the FDT (aka "duplicate FDT") now belongs to devicetree code, which is thus

[PATCH v3 3/4] of: convert unittest overlay devicetree source to sugar syntax

From: Frank Rowand The unittest-data overlays have been pulled into proper overlay devicetree source files without changing their format. The next step is to convert them to use sugar syntax instead of hand coding overlay fragments structure. A few of the overlays can

[PATCH v3 0/4] of: change overlay apply input data from unflattened

From: Frank Rowand Move duplicating and unflattening of an overlay flattened devicetree (FDT) into the overlay application code. To accomplish this, of_overlay_apply() is replaced by of_overlay_fdt_apply(). The copy of the FDT (aka "duplicate FDT") now belongs to

[PATCH v3 3/4] of: convert unittest overlay devicetree source to sugar syntax

From: Frank Rowand The unittest-data overlays have been pulled into proper overlay devicetree source files without changing their format. The next step is to convert them to use sugar syntax instead of hand coding overlay fragments structure. A few of the overlays can not be converted because

[PATCH v3 0/4] of: change overlay apply input data from unflattened

From: Frank Rowand Move duplicating and unflattening of an overlay flattened devicetree (FDT) into the overlay application code. To accomplish this, of_overlay_apply() is replaced by of_overlay_fdt_apply(). The copy of the FDT (aka "duplicate FDT") now belongs to devicetree code, which is thus

Re: linux-next: build failure after merge of the mmc tree

Hi, On Thursday 15 February 2018 06:19 AM, Stephen Rothwell wrote: > Hi Ulf, > > After merging the mmc tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > drivers/mmc/host/sdhci-omap.c: In function 'sdhci_omap_set_timing': > drivers/mmc/host/sdhci-omap.c:466:8: error:

Re: linux-next: build failure after merge of the mmc tree

Hi, On Thursday 15 February 2018 06:19 AM, Stephen Rothwell wrote: > Hi Ulf, > > After merging the mmc tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > drivers/mmc/host/sdhci-omap.c: In function 'sdhci_omap_set_timing': > drivers/mmc/host/sdhci-omap.c:466:8: error:

Re: [PATCH] Build: Scripts/Makefile: Remove Repeated Lines

On 02/14/2018 09:05 PM, Stephen Rothwell wrote: > Hi Progyan, > > On Thu, 15 Feb 2018 09:50:03 +0530 Progyan Bhattacharya > wrote: >> > >> PS: I have another question, Is use of range expression within case >> statements allowed in Kernel? If not, are we using If-Else

Re: [PATCH] Build: Scripts/Makefile: Remove Repeated Lines

On 02/14/2018 09:05 PM, Stephen Rothwell wrote: > Hi Progyan, > > On Thu, 15 Feb 2018 09:50:03 +0530 Progyan Bhattacharya > wrote: >> > >> PS: I have another question, Is use of range expression within case >> statements allowed in Kernel? If not, are we using If-Else ladder for that? > > I

[PATCH] drm/amdgpu_gem: fix error handling path in amdgpu_gem_va_update_vm

Currently, if amdgpu_vm_bo_update() fails, the returned error is being ignored. Fix this by properly checking _r_ after calling amdgpu_vm_bo_update. Also, remove redundant code just before label _error_. Addresses-Coverity-ID: 1464280 ("Unused value") Fixes: 0abc6878fc2d ("drm/amdgpu: update VM

[PATCH] drm/amdgpu_gem: fix error handling path in amdgpu_gem_va_update_vm

Currently, if amdgpu_vm_bo_update() fails, the returned error is being ignored. Fix this by properly checking _r_ after calling amdgpu_vm_bo_update. Also, remove redundant code just before label _error_. Addresses-Coverity-ID: 1464280 ("Unused value") Fixes: 0abc6878fc2d ("drm/amdgpu: update VM

Re: [PATCH v3 3/3] arm64: dts: sdm845: Add serial console support

On 02/15/2018 12:41 AM, Bjorn Andersson wrote: > [..] >>> + >>> + qup_1: geni-se@ac { >> Color me confused. So you're saying here that this is "qup_1". >> ...but above you turn the pinmux for pins "GPIO4" and "GPIO5" to >> "qup9", right? So UART2 is on "qup 1" and "qup 9"? >>

Re: [PATCH v3 3/3] arm64: dts: sdm845: Add serial console support

On 02/15/2018 12:41 AM, Bjorn Andersson wrote: > [..] >>> + >>> + qup_1: geni-se@ac { >> Color me confused. So you're saying here that this is "qup_1". >> ...but above you turn the pinmux for pins "GPIO4" and "GPIO5" to >> "qup9", right? So UART2 is on "qup 1" and "qup 9"? >>

Re: [PATCH] Build: Scripts/Makefile: Remove Repeated Lines

Hi Progyan, On Thu, 15 Feb 2018 10:04:18 +0530 Progyan Bhattacharya wrote: > > I did some ground work and found this particular commit that causing the > error. > > Commit Hash: d96977a8c2266792397ed9814bb84b5129a278ad That hash does not appear in linux-next (or Linus'

Re: [PATCH] Build: Scripts/Makefile: Remove Repeated Lines

Hi Progyan, On Thu, 15 Feb 2018 10:04:18 +0530 Progyan Bhattacharya wrote: > > I did some ground work and found this particular commit that causing the > error. > > Commit Hash: d96977a8c2266792397ed9814bb84b5129a278ad That hash does not appear in linux-next (or Linus' tree). > Commit Body:

Re: [PATCH 00/17] Add kexec_file_load support to s390

Hi, On Wed, Feb 14, 2018 at 10:54:49AM +0100, Philipp Rudo wrote: > Hi Dave, > > I just browsed AKASHI's patches (v7). The way I see it the common code changes > are on different areas of kexec_file and shouldn't get in conflict. Only in > the > arch code (s390 and arm64) some function calls

Re: [PATCH 00/17] Add kexec_file_load support to s390

Hi, On Wed, Feb 14, 2018 at 10:54:49AM +0100, Philipp Rudo wrote: > Hi Dave, > > I just browsed AKASHI's patches (v7). The way I see it the common code changes > are on different areas of kexec_file and shouldn't get in conflict. Only in > the > arch code (s390 and arm64) some function calls

Re: [PATCH] Build: Scripts/Makefile: Remove Repeated Lines

Hi Progyan, On Thu, 15 Feb 2018 09:50:03 +0530 Progyan Bhattacharya wrote: > > The last commit I have in here: > > 8396647363e1 (origin/next, next) Add linux-next specific files for 20180206 I don't know where you got that from, as my copy of that commit has SHA1

Re: [PATCH] Build: Scripts/Makefile: Remove Repeated Lines

Hi Progyan, On Thu, 15 Feb 2018 09:50:03 +0530 Progyan Bhattacharya wrote: > > The last commit I have in here: > > 8396647363e1 (origin/next, next) Add linux-next specific files for 20180206 I don't know where you got that from, as my copy of that commit has SHA1

Re: [PATCH 2/3] PCI: dwc: pci-dra7xx: Improve MSI IRQ handling

Hi, On Monday 12 February 2018 11:28 PM, Lorenzo Pieralisi wrote: > On Fri, Feb 09, 2018 at 05:34:14PM +0530, Vignesh R wrote: >> We need to ensure that there are no pending MSI IRQ vector set (i.e >> PCIE_MSI_INTR0_STATUS reads 0 at least once) before exiting >> dra7xx_pcie_msi_irq_handler().

Re: [PATCH 2/3] PCI: dwc: pci-dra7xx: Improve MSI IRQ handling

Hi, On Monday 12 February 2018 11:28 PM, Lorenzo Pieralisi wrote: > On Fri, Feb 09, 2018 at 05:34:14PM +0530, Vignesh R wrote: >> We need to ensure that there are no pending MSI IRQ vector set (i.e >> PCIE_MSI_INTR0_STATUS reads 0 at least once) before exiting >> dra7xx_pcie_msi_irq_handler().

Re: [PATCH V2] lib/scatterlist: Add SG_CHAIN and SG_END macros for LSB encodings

On 2/14/18 8:33 PM, Anshuman Khandual wrote: > This replaces scatterlist->page_link LSB encodings with SG_CHAIN and > SG_END definitions without any functional change. Looks good to me, I'll add it for 4.17. -- Jens Axboe

Re: [PATCH V2] lib/scatterlist: Add SG_CHAIN and SG_END macros for LSB encodings

On 2/14/18 8:33 PM, Anshuman Khandual wrote: > This replaces scatterlist->page_link LSB encodings with SG_CHAIN and > SG_END definitions without any functional change. Looks good to me, I'll add it for 4.17. -- Jens Axboe

Re: [PATCH v7 6/6] drm/msm: iommu: Replace runtime calls with runtime suppliers

On Thu, Feb 15, 2018 at 12:17 PM, Tomasz Figa wrote: > On Thu, Feb 15, 2018 at 1:03 AM, Robin Murphy wrote: >> On 14/02/18 10:33, Vivek Gautam wrote: >>> >>> On Wed, Feb 14, 2018 at 2:46 PM, Tomasz Figa wrote: >>> >>> Adding Jordan

Re: [PATCH v7 6/6] drm/msm: iommu: Replace runtime calls with runtime suppliers

On Thu, Feb 15, 2018 at 12:17 PM, Tomasz Figa wrote: > On Thu, Feb 15, 2018 at 1:03 AM, Robin Murphy wrote: >> On 14/02/18 10:33, Vivek Gautam wrote: >>> >>> On Wed, Feb 14, 2018 at 2:46 PM, Tomasz Figa wrote: >>> >>> Adding Jordan to this thread as well. >>> On Wed, Feb 14, 2018 at 6:13

Re: [Freedreno] [PATCH v7 6/6] drm/msm: iommu: Replace runtime calls with runtime suppliers

On Thu, Feb 15, 2018 at 1:12 AM, Rob Clark wrote: > On Wed, Feb 14, 2018 at 10:48 AM, Jordan Crouse > wrote: >> On Wed, Feb 14, 2018 at 12:31:29PM +0900, Tomasz Figa wrote: >>> >>> - When submitting commands to the GPU, the GPU driver will >>>

Re: [Freedreno] [PATCH v7 6/6] drm/msm: iommu: Replace runtime calls with runtime suppliers

On Thu, Feb 15, 2018 at 1:12 AM, Rob Clark wrote: > On Wed, Feb 14, 2018 at 10:48 AM, Jordan Crouse > wrote: >> On Wed, Feb 14, 2018 at 12:31:29PM +0900, Tomasz Figa wrote: >>> >>> - When submitting commands to the GPU, the GPU driver will >>> pm_runtime_get_sync() on the GPU device, which will

Re: [PATCH v9 2/3] arm: dts: add Nuvoton NPCM750 device tree

On February 14, 2018 6:28:51 PM PST, Joel Stanley wrote: >On Tue, Feb 13, 2018 at 4:52 PM, Joel Stanley wrote: >> Hi Brendan, >> >> On Tue, Feb 6, 2018 at 10:27 AM, Brendan Higgins >> wrote: >>> Add a common device tree for all Nuvoton

Re: [PATCH v9 2/3] arm: dts: add Nuvoton NPCM750 device tree

On February 14, 2018 6:28:51 PM PST, Joel Stanley wrote: >On Tue, Feb 13, 2018 at 4:52 PM, Joel Stanley wrote: >> Hi Brendan, >> >> On Tue, Feb 6, 2018 at 10:27 AM, Brendan Higgins >> wrote: >>> Add a common device tree for all Nuvoton NPCM750 BMCs and a board >>> specific device tree for the

Re: [RFC PATCH ghak21 0/4] audit: address ANOM_LINK excess records

On 2018-02-14 11:49, Steve Grubb wrote: > On Wednesday, February 14, 2018 11:18:20 AM EST Richard Guy Briggs wrote: > > Audit link denied events were being unexpectedly produced in a disjoint > > way when audit was disabled, and when they were expected, there were > > duplicate PATH records. This

Re: [RFC PATCH ghak21 0/4] audit: address ANOM_LINK excess records

On 2018-02-14 11:49, Steve Grubb wrote: > On Wednesday, February 14, 2018 11:18:20 AM EST Richard Guy Briggs wrote: > > Audit link denied events were being unexpectedly produced in a disjoint > > way when audit was disabled, and when they were expected, there were > > duplicate PATH records. This

Re: [PATCH] namei: fix hardlink speeling error

On Wed, Feb 14, 2018 at 09:28:54PM -0500, Richard Guy Briggs wrote: >* This ensures that not everyone will be able to create > - * handlink using the passed filedescriptor. > + * hardlink using the passed filedescriptor. >*/ You're changing this line and you didn't feel

Re: [PATCH] namei: fix hardlink speeling error

On Wed, Feb 14, 2018 at 09:28:54PM -0500, Richard Guy Briggs wrote: >* This ensures that not everyone will be able to create > - * handlink using the passed filedescriptor. > + * hardlink using the passed filedescriptor. >*/ You're changing this line and you didn't feel

Re: [PATCH v2 2/8] mm: Add kvmalloc_ab_c and kvzalloc_struct

On Wed, Feb 14, 2018 at 03:58:33PM -0800, Andrew Morton wrote: > On Wed, 14 Feb 2018 13:12:03 -0800 Matthew Wilcox wrote: > > If C macros had decent introspection, I'd like it to be: > > > > sev = kvzalloc_struct(elems, GFP_KERNEL); > > > > and have the macro examine

Re: [PATCH v2 2/8] mm: Add kvmalloc_ab_c and kvzalloc_struct

On Wed, Feb 14, 2018 at 03:58:33PM -0800, Andrew Morton wrote: > On Wed, 14 Feb 2018 13:12:03 -0800 Matthew Wilcox wrote: > > If C macros had decent introspection, I'd like it to be: > > > > sev = kvzalloc_struct(elems, GFP_KERNEL); > > > > and have the macro examine the structure pointed

linux-next: Tree for Feb 15

Hi all, Changes since 20180214: The sound-asoc tree gained a build failure so I used the version from next-20180214. The mmc tree gained a build failure so I used the version from next-20180214. Non-merge commits (relative to Linus' tree): 1794 2149 files changed, 75703 insertions(+), 44258

linux-next: Tree for Feb 15

Hi all, Changes since 20180214: The sound-asoc tree gained a build failure so I used the version from next-20180214. The mmc tree gained a build failure so I used the version from next-20180214. Non-merge commits (relative to Linus' tree): 1794 2149 files changed, 75703 insertions(+), 44258

[PATCH V2] lib/scatterlist: Add SG_CHAIN and SG_END macros for LSB encodings

This replaces scatterlist->page_link LSB encodings with SG_CHAIN and SG_END definitions without any functional change. Signed-off-by: Anshuman Khandual --- Changes in V2: - Changed SG_EMARK as SG_END as per Johannes and Tvrtko - Added 'UL' to the constants as per

[PATCH V2] lib/scatterlist: Add SG_CHAIN and SG_END macros for LSB encodings

This replaces scatterlist->page_link LSB encodings with SG_CHAIN and SG_END definitions without any functional change. Signed-off-by: Anshuman Khandual --- Changes in V2: - Changed SG_EMARK as SG_END as per Johannes and Tvrtko - Added 'UL' to the constants as per Bart

RE: [Intel-wired-lan] [PATCH net-queue 3/3] e1000e: Avoid missed interrupts following ICR read.

> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@osuosl.org] On > Behalf Of Benjamin Poirier > Sent: Wednesday, February 7, 2018 10:47 PM > To: Kirsher, Jeffrey T > Cc: net...@vger.kernel.org; intel-wired-...@lists.osuosl.org; linux- > ker...@vger.kernel.org >

RE: [Intel-wired-lan] [PATCH net-queue 3/3] e1000e: Avoid missed interrupts following ICR read.

> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@osuosl.org] On > Behalf Of Benjamin Poirier > Sent: Wednesday, February 7, 2018 10:47 PM > To: Kirsher, Jeffrey T > Cc: net...@vger.kernel.org; intel-wired-...@lists.osuosl.org; linux- > ker...@vger.kernel.org > Subject: [Intel-wired-lan]

RE: [Intel-wired-lan] [PATCH net-queue 1/3] Partial revert "e1000e: Avoid receiver overrun interrupt bursts"

> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@osuosl.org] On > Behalf Of Benjamin Poirier > Sent: Wednesday, February 7, 2018 10:47 PM > To: Kirsher, Jeffrey T > Cc: net...@vger.kernel.org; intel-wired-...@lists.osuosl.org; linux- > ker...@vger.kernel.org >

RE: [Intel-wired-lan] [PATCH net-queue 2/3] e1000e: Fix queue interrupt re-raising in Other interrupt.

> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@osuosl.org] On > Behalf Of Benjamin Poirier > Sent: Wednesday, February 7, 2018 10:47 PM > To: Kirsher, Jeffrey T > Cc: net...@vger.kernel.org; intel-wired-...@lists.osuosl.org; linux- > ker...@vger.kernel.org >

RE: [Intel-wired-lan] [PATCH net-queue 1/3] Partial revert "e1000e: Avoid receiver overrun interrupt bursts"

> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@osuosl.org] On > Behalf Of Benjamin Poirier > Sent: Wednesday, February 7, 2018 10:47 PM > To: Kirsher, Jeffrey T > Cc: net...@vger.kernel.org; intel-wired-...@lists.osuosl.org; linux- > ker...@vger.kernel.org > Subject: [Intel-wired-lan]

RE: [Intel-wired-lan] [PATCH net-queue 2/3] e1000e: Fix queue interrupt re-raising in Other interrupt.

> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@osuosl.org] On > Behalf Of Benjamin Poirier > Sent: Wednesday, February 7, 2018 10:47 PM > To: Kirsher, Jeffrey T > Cc: net...@vger.kernel.org; intel-wired-...@lists.osuosl.org; linux- > ker...@vger.kernel.org > Subject: [Intel-wired-lan]

  1   2   3   4   5   6   7   8   9   10   >