[PATCH v2 08/15] staging: fbtft: Adjust some empty-line problems - Style

Erases some blank lines. Signed-off-by: Leonardo Brás --- drivers/staging/fbtft/fb_s6d02a1.c | 1 - drivers/staging/fbtft/fb_s6d1121.c | 1 + drivers/staging/fbtft/fb_ssd1289.c | 1 + drivers/staging/fbtft/fbtft_device.c | 2 -- 4 files changed, 2 insertions(+), 3 deletions(-) diff --git

[PATCH v2 10/15] staging: fbtft: Fixes some defines styles - Style

Fixing some styles as recommended by checkpatch.pl. Signed-off-by: Leonardo Brás --- drivers/staging/fbtft/fbtft-bus.c | 10 ++ drivers/staging/fbtft/fbtft-core.c | 6 -- drivers/staging/fbtft/fbtft.h | 4 ++-- 3 files changed, 12 insertions(+), 8 deletions(-) diff --git a/d

[PATCH v2 11/15] staging: fbtft: Includes description to mutex and spinlock - Style

Includes description to mutex and spinlocks, as recommended by checkpatch.pl. Signed-off-by: Leonardo Brás --- drivers/staging/fbtft/fbtft.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/fbtft/fbtft.h b/drivers/staging/fbtft/fbtft.h index 6ee9ff320567..

[PATCH v2 09/15] staging: fbtft: Erases some repetitive usage of function name - Style

Changes this functions to avoid using "blank" on debug twice. Improves log readability. Signed-off-by: Leonardo Brás --- drivers/staging/fbtft/fb_sh1106.c | 2 +- drivers/staging/fbtft/fb_ssd1306.c | 2 +- drivers/staging/fbtft/fb_ssd1325.c | 2 +- drivers/staging/fbtft/fb_ssd1331.c | 2 +- dr

[PATCH v2 12/15] staging: fbtft: Add spaces around / - Style

Puts spaces around the /. Signed-off-by: Leonardo Brás --- drivers/staging/fbtft/fbtft-core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/fbtft/fbtft-core.c b/drivers/staging/fbtft/fbtft-core.c index 8b79353c722a..83076eca9760 100644 --- a/drivers/staging

[PATCH v2 05/15] staging: fbtft: A bit more information on dev_err.

Adds a bit more information on debug. The line break was to avoid obfuscating the parameters on the end of a large line. Signed-off-by: Leonardo Brás --- drivers/staging/fbtft/fb_ssd1351.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/drivers/staging/fbtft/fb_ssd135

[PATCH v2 06/15] staging: fbtft: Changes gamma table to define.

Most of other "Gamma Tables" were already boxed on a define, just did the same to PIOLED. Signed-off-by: Leonardo Brás --- drivers/staging/fbtft/fbtft_device.c | 13 + 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/drivers/staging/fbtft/fbtft_device.c b/drivers/stagi

[PATCH v2 07/15] staging: fbtft: Removes one nesting level to help readability - Style

This nesting level was removed to improve readability. Signed-off-by: Leonardo Brás --- drivers/staging/fbtft/flexfb.c | 27 +++ 1 file changed, 15 insertions(+), 12 deletions(-) diff --git a/drivers/staging/fbtft/flexfb.c b/drivers/staging/fbtft/flexfb.c index af6c330c

[PATCH v2 04/15] staging: fbtft: Fixes some lines long lines (>80) - Style

Trying to keep the code in the 80-char line limit. Signed-off-by: Leonardo Brás diff --git a/drivers/staging/fbtft/fb_ssd1306.c b/drivers/staging/fbtft/fb_ssd1306.c index 9276be499303..f5e0ec1c01dc 100644 --- a/drivers/staging/fbtft/fb_ssd1306.c +++ b/drivers/staging/fbtft/fb_ssd1306.c @@ -184,

[PATCH v2 01/15] staging: fbtft: Changes udelay(n) to usleep_range(n, n + x). - Style

Changes some udelay(n) for n >= 10 to usleep_range(n, n+x) as recommended by checkpatch.pl. Signed-off-by: Leonardo Brás --- drivers/staging/fbtft/fb_agm1264k-fl.c | 2 +- drivers/staging/fbtft/fb_ra8875.c | 4 ++-- drivers/staging/fbtft/fb_tinylcd.c | 2 +- drivers/staging/fbtft/fb

[PATCH v2 03/15] staging: fbtft: Fixes some alignment issues - Style

Fixes (most) alignment issues pointed by checkpatch.pl. Signed-off-by: Leonardo Brás --- drivers/staging/fbtft/fb_ssd1289.c | 6 ++--- drivers/staging/fbtft/fb_ssd1351.c | 31 ++ drivers/staging/fbtft/fb_st7735r.c | 13 +++--- drivers/staging/fbtft/fb_st7789v.c |

[PATCH v2 02/15] staging: fbtft: Puts macro arguments in parenthesis to avoid precedence issues - Style

Puts macro arguments in parenthesis to avoid precedence issues. Some large lines were broken to fit the 80-char limit. Signed-off-by: Leonardo Brás --- drivers/staging/fbtft/fb_hx8347d.c | 2 +- drivers/staging/fbtft/fb_ili9163.c | 2 +- drivers/staging/fbtft/fb_ili9320.c | 2 +- driver

[PATCH v2 00/15] staging: fbtft: Fixes some issues found with checkpatch.pl

Fixes some issues found with checkpatch.pl, and other issues found browsing the code. Leonardo Brás (15): staging: fbtft: Changes udelay(n) to usleep_range(n, n + x). - Style staging: fbtft: Puts macro arguments in parenthesis to avoid precedence issues - Style staging: fbtft: Fixes som

Re: [PATCH v2] proc: add percpu populated pages count to meminfo

On Tue, 7 Aug 2018, Dennis Zhou wrote: > From: "Dennis Zhou (Facebook)" > > Currently, percpu memory only exposes allocation and utilization > information via debugfs. This more or less is only really useful for > understanding the fragmentation and allocation information at a > per-chunk level

[PATCH] dma/direct: Use true and false for boolean values

Return statements in functions returning bool should use true or false instead of an integer value. This code was detected with the help of Coccinelle. Signed-off-by: Gustavo A. R. Silva --- arch/arm/include/asm/dma-direct.h | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --

Re: [PATCH 4.4 000/124] 4.4.146-stable review

On Mon, Aug 6, 2018 at 11:35 AM Greg Kroah-Hartman wrote: > > On Sun, Aug 05, 2018 at 03:19:33PM +, Dan Rue wrote: > > On Sun, Aug 05, 2018 at 03:49:52PM +0200, Greg Kroah-Hartman wrote: > > > On Sun, Aug 05, 2018 at 05:24:21PM +0530, Naresh Kamboju wrote: > > > > On 4 August 2018 at 14:29, Gr

[PATCH] arm64: alternative: Use true and false for boolean values

Return statements in functions returning bool should use true or false instead of an integer value. This code was detected with the help of Coccinelle. Signed-off-by: Gustavo A. R. Silva --- arch/arm64/kernel/alternative.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/a

Re: [PATCH v12 3/3] tracing: Centralize preemptirq tracepoints and unify their usage

On August 7, 2018 7:45:15 PM EDT, Steven Rostedt wrote: >On Tue, 07 Aug 2018 11:24:13 -0400 >Joel Fernandes wrote: > >> On August 7, 2018 11:09:06 AM EDT, Steven Rostedt > wrote: >> >On Tue, 07 Aug 2018 10:48:05 -0400 >> >Joel Fernandes wrote: >> > >> >> >You mean if someone add a tracepoin

Re: [PATCH v12 3/3] tracing: Centralize preemptirq tracepoints and unify their usage

On Tue, 07 Aug 2018 11:24:13 -0400 Joel Fernandes wrote: > On August 7, 2018 11:09:06 AM EDT, Steven Rostedt wrote: > >On Tue, 07 Aug 2018 10:48:05 -0400 > >Joel Fernandes wrote: > > > >> >You mean if someone add a tracepoint callback to the irq disable > >> >tracepoint, and did a lockdep ass

[PATCH] tracing/irqsoff: Handle preempt_count for different configs

From: "Steven Rostedt (VMware)" I was hitting the following warning: WARNING: CPU: 0 PID: 1 at kernel/trace/trace_irqsoff.c:631 tracer_hardirqs_off+0x15/0x2a Modules linked in: CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.18.0-rc6-test+ #13 Hardware name: MSI MS-7823/CSM-H87M-G43 (MS-7823), B

[PATCH 1/2] ARM: dts: sunxi: Don't use cd-inverted in sun8i-r40-bananapi-m2-ultra

Another user of cd-inverted seems to have crept in. Switch it away from cd-inverted to be consistent with other sunxi boards. Signed-off-by: Tuomas Tynkkynen --- arch/arm/boot/dts/sun8i-r40-bananapi-m2-ultra.dts | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/arch/arm/boot/

[PATCH 2/2] arm64: dts: sunxi: Don't use cd-inverted in sun50i-a64-pinebook

Another user of cd-inverted seems to have crept in. Switch it away from cd-inverted to be consistent with other sunxi boards. Signed-off-by: Tuomas Tynkkynen --- arch/arm64/boot/dts/allwinner/sun50i-a64-pinebook.dts | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/arch/arm64

[PATCH] NFS: Use an appropriate work queue for direct-write completion

When a direct-write completes, a work_struct is schedule to handle the completion. When NFS is being used for swap, the direct write might be a swap-out, so memory allocation can block until the write completes. The work queue currently used is not WQ_MEM_RECLAIM, so tasks can block waiting for me

Re: [PATCH v2] perf map: optimize maps__fixup_overlappings()

On Tue, Aug 07, 2018 at 05:02:37PM -0300, Arnaldo Carvalho de Melo wrote: > Em Tue, Aug 07, 2018 at 05:24:54PM +0300, Konstantin Khlebnikov escreveu: > > This function splits and removes overlapping areas. > > > > Maps in tree are ordered by start address thus we could find > > first overlap and s

Re: [PATCH] nvme: fabrics: fix ctrl_loss_tmo < 0 to reconnect forever

Looks good to me. Just 's/supplics/supplies/'. Without looking into the entire code, If we can change the type of max_reconnect and nr_reconnects to unsigned int then we can just get away with the one comparison (ctrl->nr_reconnects < ctrl->opts->max_reconnects). Reviewed-by: Chaitanya Kulkarn

Re: [PATCH] firmware: Fix security issue with request_firmware_into_buf()

On 2018-08-02 14:58, Luis Chamberlain wrote: On Wed, Aug 1, 2018, 4:26 PM Rishabh Bhatnagar wrote: When calling request_firmware_into_buf() with the FW_OPT_NOCACHE flag it is expected that firmware is loaded into buffer from memory. But inside alloc_lookup_fw_priv every new firmware that is lo

Re: [PATCH v5 05/12] PM / devfreq: Add support for policy notifiers

Hi Chanwoo, On Tue, Aug 07, 2018 at 10:35:37AM +0900, Chanwoo Choi wrote: > Hi Matthias, > > On 2018년 08월 07일 09:23, Matthias Kaehlcke wrote: > > Hi Chanwoo, > > > > On Tue, Aug 07, 2018 at 07:31:16AM +0900, Chanwoo Choi wrote: > >> Hi Matthias, > >> > >> On 2018년 08월 07일 04:21, Matthias Kaehlck

Re: [PATCH 0/3] introduce memory.oom.group

On Mon, 6 Aug 2018, Roman Gushchin wrote: > > In a cgroup-aware oom killer world, yes, we need the ability to specify > > that the usage of the entire subtree should be compared as a single > > entity with other cgroups. That is necessary for user subtrees but may > > not be necessary for top-

Re: [PATCH 3.18 00/85] 3.18.118-stable review

On Tue, Aug 07, 2018 at 08:51:02PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 3.18.118 release. > There are 85 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 kno

Re: [PATCH 4.4 00/12] 4.4.147-stable review

On Tue, Aug 07, 2018 at 08:52:04PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.147 release. > There are 12 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

Re: [PATCH 4.9 00/17] 4.9.119-stable review

On Tue, Aug 07, 2018 at 08:51:36PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.119 release. > There are 17 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

Re: [RFC PATCH 1/2] x86: WARN() when uaccess helpers fault on kernel addresses

> On Aug 7, 2018, at 2:17 PM, Jann Horn wrote: > > On Tue, Aug 7, 2018 at 4:55 AM Andy Lutomirski wrote: >>> On Aug 6, 2018, at 6:22 PM, Jann Horn wrote: >>> >>> There have been multiple kernel vulnerabilities that permitted userspace to >>> pass completely unchecked pointers through to us

[PATCH] x86/spectre: Expand test for vulnerability to empty RSB exploits

Skylake-era Intel CPUs are vulnerable to exploits of empty RSB conditions. On hardware, platform vulnerability can be determined simply by checking the processor's DisplayModel/DisplayFamily signature. However, when running in a VM, the operating system should also query IA32_ARCH_CAPABILITIES.RSB

Re: [PATCH 4.14 222/246] ext4: fix check to prevent initializing reserved inodes

On 08/01/2018 06:52 PM, Greg Kroah-Hartman wrote: > 4.14-stable review patch. If anyone has any objections, please let me know. It seems this patch is still missing from the 4.4.y and 4.9.y branches. Matthias > > -- > > From: Theodore Ts'o > > commit 5012284700775a4e6e3fbe7

Re: [PATCH 0/1] rseq/selftests: add __rseq_abi misalignment check

- On Aug 6, 2018, at 7:47 AM, gor g...@linux.ibm.com wrote: > While implementing rseq selftest for s390 a glibc problem with tls > variables alignment has been discovered. It turned out to be a general > problem affecting several architectures. The bug opened for this problem: > > https://sou

Re: [PATCH] x86/cpu: Rename Denverton and Gemini Lake

> Which simply does not work. Look at Goldmont Fam 6 Model 5C. The SoCs > with that Fam/Model combination are: > > - Apollo Lake > - Broxton (has two platforms: Morganfield and Willowtrail) Right pick one. The others are the same for software purposes and can be handled in the same way. > > I

Re: [RFC PATCH 2/3] mm/memory_hotplug: Create __shrink_pages and move it to offline_pages

On Tue, Aug 07, 2018 at 10:48:34PM +0200, Oscar Salvador wrote: > On Tue, Aug 07, 2018 at 04:54:57PM +0200, David Hildenbrand wrote: > > I wonder if we could instead forward from the callers whether we are > > dealing with ZONE_DEVICE memory (is_device ...), at least that seems > > feasible in hmm

Re: [PATCH] Revert "cpufreq: intel_pstate: Fix ->set_policy() interface for no_turbo"

On 07/08/2018 23:22, Srinivas Pandruvada wrote: > On Tue, 2018-08-07 at 22:12 +0200, Gabriele Mazzotta wrote: >> On 07/08/2018 00:11, Srinivas Pandruvada wrote: >>> On Mon, 2018-08-06 at 23:50 +0200, Gabriele Mazzotta wrote: On 06/08/2018 18:49, Srinivas Pandruvada wrote: > On Mon, 2018-08

[PATCH v2 3/4] ARM64: dts: meson-gx: add dmcbus and canvas nodes.

Wrap the canvas node in a syscon node. Signed-off-by: Maxime Jourdan --- arch/arm64/boot/dts/amlogic/meson-gx.dtsi | 17 + 1 file changed, 17 insertions(+) diff --git a/arch/arm64/boot/dts/amlogic/meson-gx.dtsi b/arch/arm64/boot/dts/amlogic/meson-gx.dtsi index b8dc4dbb391b..c98

[PATCH v2 2/4] dt-bindings: soc: amlogic: add meson-canvas documentation

DT bindings doc for amlogic,meson-canvas Signed-off-by: Maxime Jourdan --- .../soc/amlogic/amlogic,meson-canvas.txt | 36 +++ 1 file changed, 36 insertions(+) create mode 100644 Documentation/devicetree/bindings/soc/amlogic/amlogic,meson-canvas.txt diff --git a/Documenta

[PATCH v2 1/4] soc: amlogic: add meson-canvas driver

Amlogic SoCs have a repository of 256 canvas which they use to describe pixel buffers. They contain metadata like width, height, block mode, endianness [..] Many IPs within those SoCs like vdec/vpu rely on those canvas to read/write pixels. Signed-off-by: Maxime Jourdan Tested-by: Neil Armstron

Dobrodelna loterija zmagovalec.

Dobrodelna loterija zmagovalec. Vaš e-poštni naslov je pravkar zmaga (One Hundred in petdeset tisoč. Evrov) € 150.000,00 v programu UPLIFT International Charity. Zap: SP / 229 / 0-01 / 07 / 5-02 / EC. Lucky št: 9/11/13/24/40. Za dodatne informacije in zahtevek stiku postopku; CAPITAL CLAIM A

[PATCH v2 4/4] drm/meson: convert to the new canvas module

This removes the meson_canvas files within the meson/drm layer and makes use of the new canvas module that is referenced in the dts. Canvases can be used by different IPs and modules, and it is as such preferable to rely on a module that can safely dispatch canvases on demand. Signed-off-by: Maxi

Re: [PATCH] Input: cros_ec_keyb: Remove check before calling pm_wakeup_event.

hi Merek, I tried booting a snow device and could not get it to boot it to the console. I assume i don't have right kernel config. Can you share your config if possible. Thanks, RaviOn Mon, Aug 6, 2018 at 4:05 PM Ravi Chandra Sadineni wrote: > > Hi Merek, > > Thanks for the info. Lemme understan

Re: [PATCH v5 1/2] leds: core: Introduce LED pattern trigger

Hi Baolin, Thank you for addressing the review remarks. Since the patch set is targeted for 4.19, then we have three weeks before it will be merged to the for-next anyway. That said, I propose one more modification, please take a look below. On 08/06/2018 02:05 PM, Baolin Wang wrote: > Some LED c

[tip:x86/pti] x86/mm/pti: Don't clear permissions in pti_clone_pmd()

Commit-ID: 30514effc9206d4e084ec32239ae221db157d43a Gitweb: https://git.kernel.org/tip/30514effc9206d4e084ec32239ae221db157d43a Author: Joerg Roedel AuthorDate: Tue, 7 Aug 2018 12:24:30 +0200 Committer: Thomas Gleixner CommitDate: Tue, 7 Aug 2018 23:36:02 +0200 x86/mm/pti: Don't clear

[tip:x86/pti] x86/mm/pti: Clone kernel-image on PTE level for 32 bit

Commit-ID: 16a3fe634f6a568c6234b8747e5d50487fed3526 Gitweb: https://git.kernel.org/tip/16a3fe634f6a568c6234b8747e5d50487fed3526 Author: Joerg Roedel AuthorDate: Tue, 7 Aug 2018 12:24:31 +0200 Committer: Thomas Gleixner CommitDate: Tue, 7 Aug 2018 23:36:02 +0200 x86/mm/pti: Clone kernel

Re: [PATCH] firmware: coreboot: Let OF core populate platform device

Hi Stephen, Although I already 'Reviewed' this, I noticed another problem when I went to look again: On Mon, Aug 06, 2018 at 10:10:47AM -0700, Stephen Boyd wrote: > Now that the /firmware/coreboot node in DT is populated by the core DT > platform code with commit 3aa0582fdb82 ("of: platform: popu

Re: [PATCH] parisc: prefer _THIS_IP_ and _RET_IP_ statement expressions

On Tue, Aug 7, 2018 at 1:30 PM Helge Deller wrote: > > On 07.08.2018 20:11, Nick Desaulniers wrote: > > On Fri, Aug 3, 2018 at 3:34 PM Helge Deller wrote: > >> So, your patch is basically OK and doesn't break anything. > >> But I agree with Dave and Andrew, that THIS_IP is ugly. > > > > I don't d

Re: [PATCH] Revert "cpufreq: intel_pstate: Fix ->set_policy() interface for no_turbo"

On Tue, 2018-08-07 at 22:12 +0200, Gabriele Mazzotta wrote: > On 07/08/2018 00:11, Srinivas Pandruvada wrote: > > On Mon, 2018-08-06 at 23:50 +0200, Gabriele Mazzotta wrote: > > > On 06/08/2018 18:49, Srinivas Pandruvada wrote: > > > > On Mon, 2018-08-06 at 10:30 +0200, Rafael J. Wysocki wrote: > >

Re: [RFC PATCH 1/2] x86: WARN() when uaccess helpers fault on kernel addresses

On Tue, Aug 7, 2018 at 4:55 AM Andy Lutomirski wrote: > > On Aug 6, 2018, at 6:22 PM, Jann Horn wrote: > > > > There have been multiple kernel vulnerabilities that permitted userspace to > > pass completely unchecked pointers through to userspace accessors: > > > > - the waitid() bug - commit 96c

[PATCH 07/17] staging:rtl8192u: Rename __pTa - Style

The macro parameter __pTa causes a checkpatch issue because of its use of CamelCase naming. The parameter has this been renamed to addr. This is a coding style change which should have no impact on runtime code execution. Signed-off-by: John Whitmore --- drivers/staging/rtl8192u/ieee80211/dot11

[PATCH 01/17] staging:rtl8192u: Remove stale comment - Style

Remove a comment which appears to be from a previous version of code. This is a coding style change which should have no impact on runtime code execution. Signed-off-by: John Whitmore --- drivers/staging/rtl8192u/ieee80211/dot11d.h | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/st

[PATCH 05/17] staging:rtl8192u: Rename cpMacAddr Macro - Style

Rename the Macro cpMacAddr(des, src), as it causes a checkpatch issue due its use of CamelCase naming, to cp_mac_addr(des, src). This is a coding style change so should have no impact on runtime code execution. Signed-off-by: John Whitmore --- drivers/staging/rtl8192u/ieee80211/dot11d.h |

[PATCH 13/17] staging:rtl8192u: Rename DOT11D_GetMaxTxPwrInDbm - Style

The function DOT11D_GetMaxTxPwrInDbm causes a checkpatch issue due to its use of CamelCase naming. The function has been renamed to dot11d_get_max_tx_pwr_in_dbm. This is a coding style change which should have no impact on runtime code execution. Signed-off-by: John Whitmore --- drivers/staging

[PATCH 12/17] staging:rtl8192u: Rename dot11d_update_country_ie() parameters - Style

The function dot11d_update_country_ie() uses parameter names which cause a checkpatch issue de to the use of CamelCase naming. This is a coding style change which should have no impact on runtime code execution. Signed-off-by: John Whitmore --- drivers/staging/rtl8192u/ieee80211/dot11d.h | 6 ++

[PATCH 15/17] staging:rtl8192u: Rename DOT11D_ScanComplete - Style

The function DOT11D_ScanComplete causes a checkpatch issue due to its use of CamelCase naming. The function has been renamed to dot11d_scan_complete. This is a coding style change which should have no impact on runtime code execution. Signed-off-by: John Whitmore --- drivers/staging/rtl8192u/ie

Re: [RFC 5/5] powerpc/fsl: Add supported-irq-ranges for P2020

On Fri, 2018-07-27 at 15:18 +0530, Bharat Bhushan wrote: > MPIC on NXP (Freescale) P2020 supports following irq > ranges: > > 0 - 11 (External interrupt) > > 16 - 79 (Internal interrupt) > > 176 - 183 (Messaging interrupt) > > 224 - 231 (Shared message signaled interrupt) Why

[PATCH 09/17] staging:rtl8192u: Rename Dot11d_Init - Style

The function Dot11d_Init() causes a checkpatch issue due to its use of CamelCase naming. The function has been renamed to dot11d_init. This is a coding style change which should have no impact on runtime code execution. Signed-off-by: John Whitmore --- drivers/staging/rtl8192u/ieee80211/dot11d.

[PATCH 11/17] staging:rtl8192u: Rename Dot11d_UpdateCountryIe - Style

The function Dot11d_UpdateCountryIe causes a checkpatch issue due to its use of CamelCase naming, the function has been renamed to dot11d_update_country_ie. This is a coding style change which should have no impact on runtime code execution. Signed-off-by: John Whitmore --- drivers/staging/rtl8

[PATCH 14/17] staging:rtl8192u: Rename Channel - Style

The function dot11d_get_max_tx_pwr_in_dbm() uses a parameter name, Channel, which causes a checkpatch issue with CamelCase naming. The parameter has been renamed to channel. The change is a coding style change which should have no impact on runtime code execution. Signed-off-by: John Whitmore --

[PATCH 17/17] staging:rtl8192u: Rename ToLegalChannel - Style

Rename the function ToLegalChannel, which causes a checkpatch issue due to its use of CamelCase naming. The function has been renamed to to_legal_channel. This is a coding style change which should have no impact on runtime code execution. Signed-off-by: John Whitmore --- drivers/staging/rtl819

[PATCH 16/17] staging:rtl8192u: Rename IsLegalChannel - Style

The function IsLegalChannel causes a checkpatch issue due to its use of CamelCase naming. The function has been renamed to is_legal_channel. This is a coding style change which should have no impact on runtime code execution. Signed-off-by: John Whitmore --- drivers/staging/rtl8192u/ieee80211/d

[PATCH 03/17] staging:rtl8192u: Remove unused macro definitions - Style

Removed unused macro definitions as they add nothing to the code. This is a coding style change which should have no impact on runtime code execution. Signed-off-by: John Whitmore --- drivers/staging/rtl8192u/ieee80211/dot11d.h | 8 1 file changed, 8 deletions(-) diff --git a/drivers/

[PATCH 02/17] staging:rtl8192u: Add spaces around '+' operator - Style

Add spaces around '+' operator as required by the coding standard. This clears the checkpatch issue. This change is purely coding style in nature and should have not effect on runtime code execution. Signed-off-by: John Whitmore --- drivers/staging/rtl8192u/ieee80211/dot11d.h | 4 ++-- 1 file c

[PATCH 08/17] staging:rtl8192u: Lines should not end with a '(' - Style

A number of function prototypes cause a checkpatch issue - "Lines should not end with a '(' ". This issue has been cleared by moving function prototype parameters to the same line as the function name. This is a coding style change which should have no impact on runtime code execution. Signed-off

[PATCH 10/17] staging:rtl8192u: Rename Dot11d_Reset - Style

The function Dot11d_Reset causes a checkpatch issue due to its use of CamelCase naming, so has been rename to dot11d_reset. This is a coding style change which should have no impact on runtime code execution. Signed-off-by: John Whitmore --- drivers/staging/rtl8192u/ieee80211/dot11d.c

[PATCH 06/17] staging:rtl8192u: Rename macro parameter __pIeeeDev - Style

Multiple macros, defined in dot11d.h, use the variable __pIeeeDev as a parameter. This name causes a checkpatch issue due to its use of CamelCase naming. The parameter name has been changed to ieee_dev to clear this issue. This is a coding style change which should have no impact on runtime code e

[PATCH 04/17] staging:rtl8192u: Rename eqMacAddr macro - Style

The eqMacAddr(a, b) macro causes a checkpatch issue, due to CamelCase naming, so has been renamed to eq_mac_addr(a, b). This is a coding style change which should not impact on runtime code execution. Signed-off-by: John Whitmore --- drivers/staging/rtl8192u/ieee80211/dot11d.h | 4 ++-- drivers

[PATCH 00/17] staging:rtl8192u: Coding style changes

This series includes a number of simple coding style changes. There are a number of patches which rename symbols which are exported with EXPORT_SYMBOL. This may be a problem, as code using those symbols will have to be changed accordingly. John Whitmore (17): staging:rtl8192u: Remove stale comm

Re: [PATCH] x86/cpu: Rename Denverton and Gemini Lake

On Tue, 7 Aug 2018, Andi Kleen wrote: > On Tue, Aug 07, 2018 at 07:48:51PM +0200, Peter Zijlstra wrote: > > On Tue, Aug 07, 2018 at 10:35:42AM -0700, Dave Hansen wrote: > > > On 08/07/2018 10:17 AM, kan.li...@linux.intel.com wrote: > > > > Denverton and Gemini Lake are platform names and should not

Re: [PATCH] memcg, oom: be careful about races when warning about no reclaimable task

On Tue, Aug 07, 2018 at 10:23:32PM +0200, Michal Hocko wrote: > On Tue 07-08-18 16:02:47, Johannes Weiner wrote: > > On Tue, Aug 07, 2018 at 09:25:53AM +0200, Michal Hocko wrote: > > > From: Michal Hocko > > > > > > "memcg, oom: move out_of_memory back to the charge path" has added a > > > warnin

Re: [RFC PATCH 2/3] mm/memory_hotplug: Create __shrink_pages and move it to offline_pages

On Tue, Aug 07, 2018 at 04:54:57PM +0200, David Hildenbrand wrote: > I wonder if we could instead forward from the callers whether we are > dealing with ZONE_DEVICE memory (is_device ...), at least that seems > feasible in hmm code. Not having looked at details yet. Yes, this looks like the most s

[PATCH] nvme: fabrics: fix ctrl_loss_tmo < 0 to reconnect forever

When the user supplics ctrl_loss_tmo < 0, we warn them that this will cause the fabrics layer to attempt reconnection forever. However, in reality the fabrics layer never attempts to reconnect because the condition to test whether we should reconnect is backwards in this case. Signed-off-by: Tal S

Re: [PATCH] memcg, oom: be careful about races when warning about no reclaimable task

On 2018/08/08 5:19, Johannes Weiner wrote: > On Tue, Aug 07, 2018 at 07:15:11PM +0900, Tetsuo Handa wrote: >> On 2018/08/07 16:25, Michal Hocko wrote: >>> @@ -1703,7 +1703,8 @@ static enum oom_status mem_cgroup_oom(struct >>> mem_cgroup *memcg, gfp_t mask, int >>> return OOM_ASYNC; >>>

Re: [PATCH] parisc: prefer _THIS_IP_ and _RET_IP_ statement expressions

On 07.08.2018 20:11, Nick Desaulniers wrote: > On Fri, Aug 3, 2018 at 3:34 PM Helge Deller wrote: >> So, your patch is basically OK and doesn't break anything. >> But I agree with Dave and Andrew, that THIS_IP is ugly. > > I don't disagree, and other maintainers have remarked on _THIS_IP_ > being

Re: [PATCH 2/3] x86/mm/pti: Don't clear permissions in pti_clone_pmd()

On Tue, Aug 7, 2018 at 1:21 PM, Thomas Gleixner wrote: > On Tue, 7 Aug 2018, Andy Lutomirski wrote: > >> On Tue, Aug 7, 2018 at 11:34 AM, Dave Hansen wrote: >> > On 08/07/2018 03:24 AM, Joerg Roedel wrote: >> >> The function sets the global-bit on cloned PMD entries, >> >> which only makes sense

[PATCH v4 1/2] tpm: add ptr to the tpm_space struct to file_priv

Add a ptr to struct tpm_space to the file_priv to have an easy access to it in the async job without the need to allocate memory. This also allows to consolidate of the write operations for the two interfaces. Tested-by: Philip Tricca Signed-off-by: Tadeusz Struk --- drivers/char/tpm/tpm-dev-co

[PATCH v4 2/2] tpm: add support for nonblocking operation

Currently the TPM driver only supports blocking calls, which doesn't allow asynchronous IO operations to the TPM hardware. This patch changes it and adds support for nonblocking write and a new poll function to enable applications, which want to take advantage of this. Tested-by: Philip Tricca Si

[PATCH v4 0/2] tpm: add support for nonblocking operation

The TCG SAPI specification [1] defines a set of functions, which allow applications to use the TPM device in either blocking or non-blocking fashion. Each command defined by the specification has a corresponding Tss2_Sys__Prepare() and Tss2_Sys__Complete() call, which together with Tss2_Sys_Execute

Re: [PATCH] memcg, oom: be careful about races when warning about no reclaimable task

On Tue 07-08-18 16:02:47, Johannes Weiner wrote: > On Tue, Aug 07, 2018 at 09:25:53AM +0200, Michal Hocko wrote: > > From: Michal Hocko > > > > "memcg, oom: move out_of_memory back to the charge path" has added a > > warning triggered when the oom killer cannot find any eligible task > > and so t

Re: [PATCH v2] ASoC: rt5677: Fix initialization of rt5677_of_match.data

On Tue, Aug 07, 2018 at 10:13:47PM +0300, Andy Shevchenko wrote: > On Tue, 2018-08-07 at 10:19 -0700, Matthias Kaehlcke wrote: > > The driver expects to find the device id in rt5677_of_match.data, > > however > > it is currently assigned to rt5677_of_match.type. Fix this. > > > > The problem was f

Re: [PATCH 2/3] x86/mm/pti: Don't clear permissions in pti_clone_pmd()

On Tue, 7 Aug 2018, Andy Lutomirski wrote: > On Tue, Aug 7, 2018 at 11:34 AM, Dave Hansen wrote: > > On 08/07/2018 03:24 AM, Joerg Roedel wrote: > >> The function sets the global-bit on cloned PMD entries, > >> which only makes sense when the permissions are identical > >> between the user and th

Re: [PATCH] Use Kconfig flag to remove support of deprecated BE2/BE3 adapters

From: Ivan Vecera Date: Tue, 7 Aug 2018 13:44:52 +0200 > This patch is practically the same as "a1b8714593b6 ("net/mlx4: Use > Kconfig flag to remove support of old gen2 Mellanox devices")" for > mlx4 and that was accepted without any objections. Ok, please resubmit this patch then. Please add

Re: [PATCH] memcg, oom: be careful about races when warning about no reclaimable task

On Tue, Aug 07, 2018 at 07:15:11PM +0900, Tetsuo Handa wrote: > On 2018/08/07 16:25, Michal Hocko wrote: > > @@ -1703,7 +1703,8 @@ static enum oom_status mem_cgroup_oom(struct > > mem_cgroup *memcg, gfp_t mask, int > > return OOM_ASYNC; > > } > > > > - if (mem_cgroup_out_of_mem

Re: [PATCH] Revert "cpufreq: intel_pstate: Fix ->set_policy() interface for no_turbo"

On 07/08/2018 00:11, Srinivas Pandruvada wrote: > On Mon, 2018-08-06 at 23:50 +0200, Gabriele Mazzotta wrote: >> On 06/08/2018 18:49, Srinivas Pandruvada wrote: >>> On Mon, 2018-08-06 at 10:30 +0200, Rafael J. Wysocki wrote: On Sat, Aug 4, 2018 at 7:31 PM, Gabriele Mazzotta wrote: >

Re: [PATCH v2] proc: add percpu populated pages count to meminfo

On Tue, Aug 07, 2018 at 11:47:23AM -0700, Dennis Zhou wrote: > From: "Dennis Zhou (Facebook)" > > Currently, percpu memory only exposes allocation and utilization > information via debugfs. This more or less is only really useful for > understanding the fragmentation and allocation information at

Re: [PATCH v2] perf map: optimize maps__fixup_overlappings()

Em Tue, Aug 07, 2018 at 05:24:54PM +0300, Konstantin Khlebnikov escreveu: > This function splits and removes overlapping areas. > > Maps in tree are ordered by start address thus we could find > first overlap and stop if next map does not overlap. > > Signed-off-by: Konstantin Khlebnikov Jiri,

Re: [PATCH] x86/cpu: Rename Denverton and Gemini Lake

On Tue, Aug 07, 2018 at 11:37:36AM -0700, Andi Kleen wrote: > On Tue, Aug 07, 2018 at 07:48:51PM +0200, Peter Zijlstra wrote: > > On Tue, Aug 07, 2018 at 10:35:42AM -0700, Dave Hansen wrote: > > > On 08/07/2018 10:17 AM, kan.li...@linux.intel.com wrote: > > > > Denverton and Gemini Lake are platfor

Re: [PATCH] memcg, oom: be careful about races when warning about no reclaimable task

On Tue, Aug 07, 2018 at 09:25:53AM +0200, Michal Hocko wrote: > From: Michal Hocko > > "memcg, oom: move out_of_memory back to the charge path" has added a > warning triggered when the oom killer cannot find any eligible task > and so there is no way to reclaim the oom memcg under its hard limit.

[PATCH v2] android: binder: Rate-limit debug and userspace triggered err msgs

Use rate-limited debug messages where userspace can trigger excessive log spams. Acked-by: Arve Hjønnevåg Signed-off-by: Sherry Yang --- v2: rebase onto char-misc-next to resolve include order difference from master drivers/android/binder.c | 5 +++-- drivers/android/binder_alloc.c | 41

Re: [PATCH RFC 4/4] arm64: dts: qcom: add wake up interrupts for GPIOs

On Tue, Jul 31, 2018 at 3:44 PM Lina Iyer wrote: > > GPIOs that are wakeup capable have interrupt lines that are routed to > the always-on interrupt controller (PDC) in parallel to the pinctrl. The > interrupts listed here are the wake up lines corresponding to GPIOs. > > Signed-off-by: Lina Iyer

[PATCH v2 2/2] spi-nor: add support for is25wp256

From: "Wesley W. Terpstra" This is used of the HiFive Unleashed development board, and follows the pattern of similar ISSI devices already listed. Signed-off-by: Wesley W. Terpstra Signed-off-by: Palmer Dabbelt --- drivers/mtd/spi-nor/spi-nor.c | 2 ++ 1 file changed, 2 insertions(+) diff --

[PATCH v2 1/2] spi-nor: add support for ISSI's block unlocking scheme

From: "Wesley W. Terpstra" ISSI uses a non-standard scheme to control block protection, with bit 5 of the status registerr controlling an additional block protection bit. This patch disables all the block protection bits whenever an ISSI chip is seen. We might also want to trigger an error when

[PATCH v2 0/2] spi-nor: add support for is25wp256

This adds support for the is25wp256 flash chip, which is on our HiFive Unleashed board. Additionally it adds support for ISSI's special unlocking scheme, which we need to unlock block protection on the whole chip. Changes since v1 [<20180804014947.24601-1-pal...@sifive.com>]: * There are now two

[PATCH] drm/vc4: Make sure to emit a tile coordinates between two MSAA loads.

The HW only executes a load once the tile coordinates packet happens, and only tracks one at a time, so by emitting our two MSAA loads back to back we would end up with an undefined color or Z buffer. Fixes dEQP-EGL.functional.render.multi_context.gles2.rgb888_window Signed-off-by: Eric Anholt C

Re: [PATCH] net: thunderx: check for failed allocation lmac->dmacs

From: Colin King Date: Mon, 6 Aug 2018 17:50:45 +0100 > From: Colin Ian King > > The allocation of lmac->dmacs is not being checked for allocation > failure. Add the check. > > Fixes: 3a34ecfd9d3f ("net: thunderx: add MAC address filter tracking for > LMAC") > Signed-off-by: Colin Ian King

Re: [PATCH 2/3] x86/mm/pti: Don't clear permissions in pti_clone_pmd()

On Tue, Aug 7, 2018 at 11:34 AM, Dave Hansen wrote: > On 08/07/2018 03:24 AM, Joerg Roedel wrote: >> The function sets the global-bit on cloned PMD entries, >> which only makes sense when the permissions are identical >> between the user and the kernel page-table. >> >> Further, only write-permiss

Re: [PATCH v3 1/2] PM / devfreq: Generic CPU frequency to device frequency mapping governor

On 2018-08-07 09:41, Rob Herring wrote: On Wed, Aug 01, 2018 at 05:57:41PM -0700, Saravana Kannan wrote: Many CPU architectures have caches that can scale independent of the CPUs. Frequency scaling of the caches is necessary to make sure the cache is not a performance bottleneck that leads to p

Re: [PATCH v10 0/3] add support for Bluetooth on MT7622 SoC

Hi Sean, > v10 and changes since v9: > - Add a fixup that is __be16 is required instead of dlen1 + dlen2 in STP > header. > - Align a few one-line comments style as they're made in v9 > - Fix two warnings catched by checkpatch.pl > WARNING:TYPO_SPELLING: 'specifc' may be misspelled - perha

<    1   2   3   4   5   6   7   8   >