[PATCH 04/10] ASoC: fsl_sai: Update Tx/Rx channel enable mask

Tx channel enable (TCE) / Rx channel enable (RCE) bits enable corresponding data channel for Tx/Rx operation. Because SAI supports up the 8 channels TCE/RCE occupy up the 8 bits inside TCR3/RCR3 registers we need to extend the mask to reflect this. Signed-off-by: Daniel Baluta ---

[PATCH 02/10] ASoC: fsl_sai: derive TX FIFO watermark from FIFO depth

From: Lucas Stach The DMA request schould be triggered as soon as the FIFO has space for another burst. As different versions of the SAI block have different FIFO sizes, the watrmark level needs to be derived from version specific data. Signed-off-by: Lucas Stach --- sound/soc/fsl/fsl_sai.c |

[PATCH 06/10] ASoC: dt-bindings: Document dl_mask property

SAI supports up to 8 data lines. This property let the user configure how many data lines should be used per transfer direction (Tx/Rx). Signed-off-by: Daniel Baluta --- Documentation/devicetree/bindings/sound/fsl-sai.txt | 5 + 1 file changed, 5 insertions(+) diff --git

[PATCH 05/10] ASoC: fsl_sai: Add support to enable multiple data lines

SAI supports up to 8 Rx/Tx data lines which can be enabled using TCE/RCE bits of TCR3/RCR3 registers. Data lines to be enabled are read from DT fsl,dl_mask property. By default (if no DT entry is provided) only data line 0 is enabled. Note: We can only enable consecutive data lines starting with

[PATCH 09/10] ASoC: fsl_sai: Add support for SAI new version

New IP version introduces Version ID and Parameter registers and optionally added Timestamp feature. VERID and PARAM registers are placed at the top of registers address space and some registers are shifted according to the following table: Tx/Rx data registers and Tx/Rx FIFO registers keep

[PATCH 07/10] ASoC: fsl_sai: Add support for FIFO combine mode

FIFO combining mode allows the separate FIFOs for multiple data channels to be used as a single FIFO for either software accesses or a single data channel or both. FIFO combined mode is described in chapter 13.10.3.5.4 from i.MX8MQ reference manual [1]. For each direction (RX/TX) fifo combine

[PATCH 08/10] ASoC: dt-bindings: Document fcomb_mode property

This allows combining multiple-data-line FIFOs into a single-data-line FIFO. Signed-off-by: Daniel Baluta --- Documentation/devicetree/bindings/sound/fsl-sai.txt | 4 1 file changed, 4 insertions(+) diff --git a/Documentation/devicetree/bindings/sound/fsl-sai.txt

[PATCH 03/10] ASoC: fsl_sai: Add registers definition for multiple datalines

SAI IP supports up to 8 data lines. The configuration of supported number of data lines is decided at SoC integration time. This patch adds definitions for all related data TX/RX registers: * TDR0..7, Transmit data register * TFR0..7, Transmit FIFO register * RDR0..7,

[PATCH 10/10] ASoC: fsl_sai: Add support for imx7ulp/imx8mq

SAI module on imx7ulp/imx8m features 2 new registers (VERID and PARAM) at the beginning of register address space. On imx7ulp FIFOs can held up to 16 x 32 bit samples. On imx8mq FIFOs can held up to 128 x 32 bit samples. Signed-off-by: Daniel Baluta --- sound/soc/fsl/fsl_sai.c | 14

[PATCH 01/10] ASoC: fsl_sai: add of_match data

From: Lucas Stach New revisions of the SAI IP block have even more differences that need be taken into account by the driver. To avoid sprinking compatible checks all over the driver move the current differences into of_match_data. Signed-off-by: Lucas Stach --- sound/soc/fsl/fsl_sai.c | 22

[PATCH 00/10] Add support for new SAI IP version

So far SAI IPs integrated with imx6 only supported one data line. Starting with imx7 and imx8 SAI integration support up to 8 data lines and multiple ways of combining the fifos for each data line. New SAI IP version introduces two new registers (Version and Parmeter registers) which are placed

[PATCH 0/4][V3] iio: imu: Add support for the ADIS16460 IMU

This changeset adds support for the ADIS16460. Support for this chip, requires changes in both IIO & SPI, in order to support configurable/longer CS change delays. The default CS change delay is 10 uS, while the ADIS16460 requires a minimum of 16 uS. In order to accomodate this, the SPI transfer

[PATCH 3/4][V3] iio: imu: Add support for the ADIS16460 IMU

The ADIS16460 device is a complete inertial system that includes a triaxial gyroscope and a triaxial accelerometer. It's more simplified design than that of the ADIS16480, and does not offer the triaxial magnetometers & pressure sensors. It does also have a temperature sensor (like the ADIS16480).

[PATCH 4/4][V3] dt-bindings: iio: imu: add bindings for ADIS16460

This change adds device-tree bindings for the ADIS16460. Reviewed-by: Rob Herring Signed-off-by: Alexandru Ardelean --- .../bindings/iio/imu/adi,adis16460.yaml | 53 +++ MAINTAINERS | 1 + 2 files changed, 54 insertions(+) create mode

Re: [PATCH 1/3] printk: Allow architecture-specific timestamping function

On 22/07/2019 12:25, Petr Mladek wrote: > On Mon 2019-07-22 11:33:28, Marc Zyngier wrote: >> printk currently relies on local_clock to time-stamp the kernel >> messages. In order to allow the timestamping (and only that) >> to be overridden by architecture-specific code, let's declare >> a new

[PATCH 2/4][V3] iio: imu: adis: Add support for SPI transfer cs_change_delay

The ADIS16460 requires a higher delay before the next transfer. Since the SPI framework supports configuring the delay before the next transfer, this driver will become the first user of it. The support for this functionality in ADIS16460 requires an addition to the ADIS lib to support the

[PATCH 1/4][V3] spi: Add optional stall delay between cs_change transfers

Some devices like the ADIS16460 IMU require a longer period between transfers, i.e. between when the CS is de-asserted and re-asserted. The default value of 10us is not enough. This change makes the delay configurable for when the next CS change goes active, allowing the default to remain 10us is

[PATCH 3/3] [v2] dmaengine: dw-edma: fix endianess confusion

When building with 'make C=1', sparse reports an endianess bug: drivers/dma/dw-edma/dw-edma-v0-debugfs.c:60:30: warning: cast removes address space of expression drivers/dma/dw-edma/dw-edma-v0-debugfs.c:86:24: warning: incorrect type in argument 1 (different address spaces)

[PATCH 2/3] [v2] dmaengine: dw-edma: fix __iomem type confusion

The new driver mixes up dma_addr_t and __iomem pointers, which results in warnings on some 32-bit architectures, like: drivers/dma/dw-edma/dw-edma-v0-core.c: In function '__dw_regs': drivers/dma/dw-edma/dw-edma-v0-core.c:28:9: error: cast to pointer from integer of different size

[PATCH 1/3] [v2] dmaengine: dw-edma: fix unnecessary stack usage

Putting large constant data on the stack causes unnecessary overhead and stack usage: drivers/dma/dw-edma/dw-edma-v0-debugfs.c:285:6: error: stack frame size of 1376 bytes in function 'dw_edma_v0_debugfs_on' [-Werror,-Wframe-larger-than=] Mark the variable 'static const' in order for the

Pershendetje e dashur,

Pershendetje e dashur, A mund të trajtoni një projekt themeli? ju lutemi të përgjigjeni për më shumë hollësi dhe informacion. Zonja Karin

Re: [PATCH net-next 0/3] net: stmmac: Convert to phylink

Hello Jose, On Tue, Jun 11, 2019 at 05:18:44PM +0200, Jose Abreu wrote: > [ Hope this diff looks better (generated with --minimal) ] > > This converts stmmac to use phylink. Besides the code redution this will > allow to gain more flexibility. I'm testing 5.3-rc1 and on Orange Pi 3 (uses

Re: [for-next][PATCH 12/16] kprobes: Initialize kprobes at postcore_initcall

Hi Steve, On Tue, Jul 09, 2019 at 11:15:20AM -0400, Steven Rostedt wrote: > On Wed, 3 Jul 2019 15:08:32 +0100 > Catalin Marinas wrote: > > > diff --git a/kernel/kprobes.c b/kernel/kprobes.c > > > index 5471efbeb937..0ca6f53c8505 100644 > > > --- a/kernel/kprobes.c > > > +++ b/kernel/kprobes.c >

Re: [PATCH v2 2/2] gpio: em: use a helper variable for >dev

czw., 11 lip 2019 o 10:48 Geert Uytterhoeven napisał(a): > > On Thu, Jul 11, 2019 at 10:29 AM Bartosz Golaszewski wrote: > > From: Bartosz Golaszewski > > > > Instead of always dereferencing >dev, just assign a helper local > > variable of type struct device * and use it where applicable. > > >

Re: [PATCH 23/79] libperf: Make libperf.a part of the build

Em Sun, Jul 21, 2019 at 01:24:10PM +0200, Jiri Olsa escreveu: > Adding empty libperf.a under toos/perf/lib and > linking it with perf. So, I noticed you created a subdirectory under tools/perf/, while I first thought you would have it in tools/lib/perf/, why not move it there? - Arnaldo > It

Re: [PATCH] [v2] kasan: remove clang version check for KASAN_STACK

On Fri, Jul 19, 2019 at 10:03:31PM +0200, Arnd Bergmann wrote: > asan-stack mode still uses dangerously large kernel stacks of > tens of kilobytes in some drivers, and it does not seem that anyone > is working on the clang bug. Reviewed-by: Mark Brown signature.asc Description: PGP signature

[PATCH 2/5] arm64: dts: qcom: sdm845: remove unnecessary properties for dsi nodes

We get a warning about unnecessary properties of arch/arm64/boot/dts/qcom/sdm845.dtsi:2211.22-2257.6: Warning (avoid_unnecessary_addr_size): /soc/mdss@ae0/dsi@ae94000: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property

[PATCH 4/5] arm64: dts: qcom: sdm845: remove macro from unit name

Unit name is supposed to be a number, using a macro with hex value is not recommended, so add the value in unit name. arch/arm64/boot/dts/qcom/pm8998.dtsi:81.18-84.6: Warning (unit_address_format): /soc/spmi@c44/pmic@0/adc@3100/adc-chan@0x06: unit name should not have leading "0x"

[PATCH 5/5] arm64: dts: qcom: sdm845-cheza: remove macro from unit name

Unit name is supposed to be a number, using a macro with hex value is not recommended, so add the value in unit name. arch/arm64/boot/dts/qcom/sdm845-cheza.dtsi:966.16-969.4: Warning (unit_address_format): /soc@0/spmi@c44/pmic@0/adc@3100/adc-chan@0x4d: unit name should not have leading "0x"

[PATCH 0/5] arm64: dts: qcom: sdm845: Fix DTS warnings

So this is an attempt to fix some warns on sdm845 dts. We still have bunch of warnings to fix after this series (dupplicate adress and node names having underscores etc). lets get long hanging ones fixed, we can see the warns with W=1 or W=2 Vinod Koul (5): arm64: dts: qcom: sdm845: Add unit

[PATCH 3/5] arm64: dts: qcom: sdm845: remove unit name for thermal trip points

The thermal trip points have unit name but no reg property, so we can remove them arch/arm64/boot/dts/qcom/sdm845.dtsi:2824.31-2828.7: Warning (unit_address_vs_reg): /thermal-zones/cpu0-thermal/trips/trip-point@0: node has a unit name, but no reg property

[PATCH 1/5] arm64: dts: qcom: sdm845: Add unit name to soc node

We get a warning about missing unit name for soc node, so add it. arch/arm64/boot/dts/qcom/sdm845.dtsi:623.11-2814.4: Warning (unit_address_vs_reg): /soc: node has a reg or ranges property, but no unit name Signed-off-by: Vinod Koul --- arch/arm64/boot/dts/qcom/sdm845.dtsi | 2 +- 1 file

Re: [for-next][PATCH 12/16] kprobes: Initialize kprobes at postcore_initcall

On Tue, Jul 09, 2019 at 09:30:49PM +0900, Masami Hiramatsu wrote: > On Wed, 3 Jul 2019 10:02:05 -0400 Steven Rostedt > wrote: > > On Tue, 2 Jul 2019 17:50:09 +0100 Mark Rutland > > wrote: > > > On Sun, May 26, 2019 at 03:18:40PM -0400, Steven Rostedt wrote: > > > > Signed-off-by: Masami

Re: [PATCH] s390: use __u{16,32,64} instead of uint{16,32,64}_t in uapi header

On Sun, Jul 21, 2019 at 11:20:08PM +0900, Masahiro Yamada wrote: > When CONFIG_UAPI_HEADER_TEST=y, exported headers are compile-tested to > make sure they can be included from user-space. > > Currently, zcrypt.h is excluded from the test coverage. To make it > join the compile-test, we need to

Re: [PATCH v9 4/8] sched/deadline: Fix bandwidth accounting at all levels after offline migration

On 22/07/19 13:07, Dietmar Eggemann wrote: > On 7/19/19 3:59 PM, Juri Lelli wrote: > > [...] > > > @@ -557,6 +558,38 @@ static struct rq *dl_task_offline_migration(struct rq > > *rq, struct task_struct *p > > double_lock_balance(rq, later_rq); > > } > > > > + if

Re: [PATCH] firmware: fix build errors in paged buffer handling code

On Mon, 22 Jul 2019 14:12:02 +0200, Greg Kroah-Hartman wrote: > > On Mon, Jul 22, 2019 at 01:55:20PM +0200, Takashi Iwai wrote: > > On Mon, 22 Jul 2019 07:55:36 +0200, > > Takashi Iwai wrote: > > > > > > From: Mauro Rossi > > > > > > fw_{grow,map}_paged_buf() need to be defined as static

Re: [PATCH] [v2] kasan: remove clang version check for KASAN_STACK

On 7/19/19 11:03 PM, Arnd Bergmann wrote: > asan-stack mode still uses dangerously large kernel stacks of > tens of kilobytes in some drivers, and it does not seem that anyone > is working on the clang bug. > > Turn it off for all clang versions to prevent users from > accidentally enabling it

Re: [PATCH v2] leds: apu: fix error message on probing failure

On Mon 2019-07-22 14:08:51, Enrico Weigelt, metux IT consult wrote: > From: Enrico Weigelt > > The current error message on failed probing tends to be a bit > misleading. Fix it to tell exactly that an APU v1 was not found. > > Signed-off-by: Enrico Weigelt Acked-by: Pavel Machek --

Re: [PATCH] [v3] page flags: prioritize kasan bits over last-cpuid

On 7/22/19 2:55 PM, Arnd Bergmann wrote: > ARM64 randdconfig builds regularly run into a build error, especially > when NUMA_BALANCING and SPARSEMEM are enabled but not SPARSEMEM_VMEMMAP: > > #error "KASAN: not enough bits in page flags for tag" > > The last-cpuid bits are already

Re: [PATCH] ubsan: build ubsan.c more conservatively

On 7/22/19 12:10 PM, Arnd Bergmann wrote: > objtool points out several conditions that it does not like, depending > on the combination with other configuration options and compiler > variants: > > stack protector: > lib/ubsan.o: warning: objtool: __ubsan_handle_type_mismatch()+0xbf: call to

Applied "SoC: rockchip: rockchip_max98090: Enable MICBIAS for headset keypress detection" to the asoc tree

The patch SoC: rockchip: rockchip_max98090: Enable MICBIAS for headset keypress detection has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.3 All being well this means that it will be integrated into the linux-next tree (usually

Applied "SoC: rockchip-max98090: Remove MICBIAS as supply of input pin IN34" to the asoc tree

The patch SoC: rockchip-max98090: Remove MICBIAS as supply of input pin IN34 has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.4 All being well this means that it will be integrated into the linux-next tree (usually sometime in

Applied "regulator: lm363x: Fix off-by-one n_voltages for lm3632 ldo_vpos/ldo_vneg" to the regulator tree

The patch regulator: lm363x: Fix off-by-one n_voltages for lm3632 ldo_vpos/ldo_vneg has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.4 All being well this means that it will be integrated into the linux-next tree

Applied "regulator: lm363x: Fix n_voltages setting for lm36274" to the regulator tree

The patch regulator: lm363x: Fix n_voltages setting for lm36274 has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.4 All being well this means that it will be integrated into the linux-next tree (usually sometime in the

Applied "ASoC: wcd9335: Fix misuse of GENMASK macro" to the asoc tree

The patch ASoC: wcd9335: Fix misuse of GENMASK macro has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.4 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

Applied "ASoC: codecs: ad193x: Use regmap_multi_reg_write() when initializing" to the asoc tree

The patch ASoC: codecs: ad193x: Use regmap_multi_reg_write() when initializing has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.4 All being well this means that it will be integrated into the linux-next tree (usually sometime in

Applied "ASoC: fsl_esai: Wrap some operations to be functions" to the asoc tree

The patch ASoC: fsl_esai: Wrap some operations to be functions has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.4 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

Applied "sound: soc: codecs: wcd9335: add irqflag IRQF_ONESHOT flag" to the asoc tree

The patch sound: soc: codecs: wcd9335: add irqflag IRQF_ONESHOT flag has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.4 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next

Applied "ASoC: SOF: use __u32 instead of uint32_t in uapi headers" to the asoc tree

The patch ASoC: SOF: use __u32 instead of uint32_t in uapi headers has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.3 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

Applied "ASoC: max98383: fix i2c probe failure" to the asoc tree

The patch ASoC: max98383: fix i2c probe failure has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.4 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Applied "ASoC: dapm: Fix handling of custom_stop_condition on DAPM graph walks" to the asoc tree

The patch ASoC: dapm: Fix handling of custom_stop_condition on DAPM graph walks has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.3 All being well this means that it will be integrated into the linux-next tree (usually sometime

Applied "sound: soc: codecs: mt6358: change return type of mt6358_codec_init_reg" to the asoc tree

The patch sound: soc: codecs: mt6358: change return type of mt6358_codec_init_reg has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.4 All being well this means that it will be integrated into the linux-next tree (usually sometime

Applied "sound: soc: bcm: cygnus-pcm: Unneeded variable: "ret"." to the asoc tree

The patch sound: soc: bcm: cygnus-pcm: Unneeded variable: "ret". has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.4 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

Applied "regulator: rk808: Return REGULATOR_MODE_INVALID for invalid mode" to the regulator tree

The patch regulator: rk808: Return REGULATOR_MODE_INVALID for invalid mode has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.4 All being well this means that it will be integrated into the linux-next tree (usually

Applied "ASoC: cs42xx8: Fix MFREQ selection issue for async mode" to the asoc tree

The patch ASoC: cs42xx8: Fix MFREQ selection issue for async mode has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.3 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

Applied "spi: pxa2xx: Balance runtime PM enable/disable on error" to the spi tree

The patch spi: pxa2xx: Balance runtime PM enable/disable on error has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-5.3 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24

[PATCH A] scsi: fdomain: fix building pcmcia front-end

We get a warning when CONFIG_SCSI_LOWLEVEL is disabled here: WARNING: unmet direct dependencies detected for SCSI_FDOMAIN Depends on [n]: SCSI_LOWLEVEL [=n] && SCSI [=y] Selected by [m]: - PCMCIA_FDOMAIN [=m] && SCSI_LOWLEVEL_PCMCIA [=y] && SCSI [=y] && PCMCIA [=y] && m && MODULES [=y]

[PATCH B] scsi: fdomain: fix building pcmcia front-end

We get a warning when CONFIG_SCSI_LOWLEVEL is disabled here: WARNING: unmet direct dependencies detected for SCSI_FDOMAIN Depends on [n]: SCSI_LOWLEVEL [=n] && SCSI [=y] Selected by [m]: - PCMCIA_FDOMAIN [=m] && SCSI_LOWLEVEL_PCMCIA [=y] && SCSI [=y] && PCMCIA [=y] && m && MODULES [=y]

[v5.3-rc1 regression] Hitting a kernel BUG() when trying to load a module on DaVinci SoC

Hi, with v5.3-rc1 I'm hitting the following BUG() when trying to load the gpio-backlight module: kernel BUG at kernel/module.c:1919! Internal error: Oops - BUG: 0 [#1] PREEMPT ARM Modules linked in: CPU: 0 PID: 1 Comm: systemd Tainted: GW 5.2.0-rc2-5-g7dabaa5ce05a #19 Hardware name:

Re: [PATCH] firmware: fix build errors in paged buffer handling code

On Mon, Jul 22, 2019 at 01:55:20PM +0200, Takashi Iwai wrote: > On Mon, 22 Jul 2019 07:55:36 +0200, > Takashi Iwai wrote: > > > > From: Mauro Rossi > > > > fw_{grow,map}_paged_buf() need to be defined as static inline > > when CONFIG_FW_LOADER_PAGED_BUF is not enabled, > > infact

Re: [PATCH v10 0/6] Introduced new Cadence USBSS DRD Driver.

On Mon, Jul 22, 2019 at 01:56:45PM +0200, Pavel Machek wrote: > Hi! > > > > >> This patch introduce new Cadence USBSS DRD driver to linux kernel. > > > >> > > > >> The Cadence USBSS DRD Controller is a highly configurable IP Core which > > > >> can be instantiated as Dual-Role Device (DRD),

[PATCH] anon_inodes: remove redundant file->f_mapping initialization

In anon_inode_getfile(), file->f_mapping is redundantly initialized to anon_inode_inode->i_mapping, since it has already been initialized in alloc_file_pseudo() -> alloc_file(), so remove the initialization in anon_inode_getfile(). Signed-off-by: Kai Huang --- fs/anon_inodes.c | 2 -- 1 file

Re: [git pull] habanalabs fixes for 5.3-rc2

On Mon, Jul 22, 2019 at 10:26:21AM +0300, Oded Gabbay wrote: > Hello Greg, > > This is habanalabs fixes pull request for 5.3-rc2. > It contains two minor fixes, nothing too exciting. > > Thanks, > Oded > > The following changes since commit c8917b8ff09e8a4d6ef77e32ce0052f7158baa1f: > >

[PATCH v2] leds: apu: fix error message on probing failure

From: Enrico Weigelt The current error message on failed probing tends to be a bit misleading. Fix it to tell exactly that an APU v1 was not found. Signed-off-by: Enrico Weigelt --- drivers/leds/leds-apu.c | 10 +++--- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git

VERRY VERRY URGENT

FROM Mr.ABDELLATIFE JOUAHRI AUDIT& ACCOUNT MANAGER BANK OF AFRICA (B.O.A) OUAGADOUGOU BURKINA FASO WEST AFRICA. Dear Friend, With due respect, I have decided to contact you on a business transaction that will be beneficial to both of us. At the bank last account and auditing evaluation, my staffs

Re: [PATCH v2 4/4] arm64: Remove unneeded rcu_read_lock from debug handlers

On Mon, Jul 22, 2019 at 04:49:11PM +0900, Masami Hiramatsu wrote: > Remove rcu_read_lock()/rcu_read_unlock() from debug exception > handlers since we are sure those are not preemptible and > interrupts are off. > > Signed-off-by: Masami Hiramatsu > Cc: Paul E. McKenney >From an RCU viewpoint:

Re: [PATCH v2 18/30] virtio_fs, dax: Set up virtio_fs dax_device

On 22.07.19 14:00, Christian Borntraeger wrote: > > > On 22.07.19 13:43, Cornelia Huck wrote: >> On Mon, 22 Jul 2019 13:20:18 +0200 >> Christian Borntraeger wrote: >> >>> On 22.07.19 12:56, Dr. David Alan Gilbert wrote: * Christian Borntraeger (borntrae...@de.ibm.com) wrote: > >

Re: [PATCH v2 3/4] arm64: Make debug exception handlers visible from RCU

On Mon, Jul 22, 2019 at 04:48:58PM +0900, Masami Hiramatsu wrote: > Make debug exceptions visible from RCU so that synchronize_rcu() > correctly track the debug exception handler. > > This also introduces sanity checks for user-mode exceptions as same > as x86's ist_enter()/ist_exit(). > > The

Re: [PATCH net-next 3/3] net: stmmac: Introducing support for Page Pool

On 22/07/2019 12:39, Jose Abreu wrote: > From: Lars Persson > Date: Jul/22/2019, 12:11:50 (UTC+00:00) > >> On Mon, Jul 22, 2019 at 12:18 PM Ilias Apalodimas >> wrote: >>> >>> On Thu, Jul 18, 2019 at 07:48:04AM +, Jose Abreu wrote: From: Jon Hunter Date: Jul/17/2019, 19:58:53

Re: [PATCH] mm/Kconfig: additional help text for HMM_MIRROR option

On Mon, Jul 22, 2019 at 08:58:04AM -0300, Jason Gunthorpe wrote: > No one has given me a satisfactory answer about the restriction > either. > > The only thing this kconfig controls that could possibly be arch > specific is the page walking code in hmm_range_snapshot and > related. > > Maybe

Re: [PATCH] mm: vmscan: check if mem cgroup is disabled or not before calling memcg slab shrinker

On Thu 18-07-19 01:45:26, Yang Shi wrote: > Shakeel Butt reported premature oom on kernel with > "cgroup_disable=memory" since mem_cgroup_is_root() returns false even > though memcg is actually NULL. The drop_caches is also broken. > > It is because commit aeed1d325d42 ("mm/vmscan.c: generalize

Re: [PATCH v2 18/30] virtio_fs, dax: Set up virtio_fs dax_device

On 22.07.19 13:43, Cornelia Huck wrote: > On Mon, 22 Jul 2019 13:20:18 +0200 > Christian Borntraeger wrote: > >> On 22.07.19 12:56, Dr. David Alan Gilbert wrote: >>> * Christian Borntraeger (borntrae...@de.ibm.com) wrote: On 18.07.19 16:30, Dan Williams wrote: > On Thu,

[GIT PULL for v5.3-rc1] media updates

Hi Linus, Please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media tags/media/v5.3-2 For two regressions at media core: - v4l2-subdev: fix regression in check_pad() - videodev2.h: change V4L2_PIX_FMT_BGRA444 define: fourcc was already in use Regards, Mauro

Re: [PATCH] mm/Kconfig: additional help text for HMM_MIRROR option

On Fri, Jul 19, 2019 at 01:38:28PM -0700, John Hubbard wrote: > On 7/19/19 5:04 AM, Pavel Machek wrote: > > On Fri 2019-07-19 05:00:43, Christoph Hellwig wrote: > >> On Fri, Jul 19, 2019 at 08:48:53AM -0300, Jason Gunthorpe wrote: > >>> It is like MMU_NOTIFIERS, if something needs it, then it will

Re: RFC: call_rcu_outstanding (was Re: WARNING in __mmdrop)

On Mon, Jul 22, 2019 at 03:56:22AM -0400, Michael S. Tsirkin wrote: > On Sun, Jul 21, 2019 at 12:28:41PM -0700, Paul E. McKenney wrote: > > On Sun, Jul 21, 2019 at 01:53:23PM -0400, Michael S. Tsirkin wrote: > > > On Sun, Jul 21, 2019 at 06:17:25AM -0700, Paul E. McKenney wrote: > > > > On Sun,

Re: [PATCH v10 0/6] Introduced new Cadence USBSS DRD Driver.

Hi! > > >> This patch introduce new Cadence USBSS DRD driver to linux kernel. > > >> > > >> The Cadence USBSS DRD Controller is a highly configurable IP Core which > > >> can be instantiated as Dual-Role Device (DRD), Peripheral Only and > > >> Host Only (XHCI)configurations. > > > > > >I see you

[PATCH v2] leds: apu: fix error message on probing failure

From: Enrico Weigelt The current error message on failed probing tends to be a bit misleading. Fix it to tell exactly that an APU v1 was not found. Signed-off-by: Enrico Weigelt --- drivers/leds/leds-apu.c | 10 +++--- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git

[PATCH v2] firmware: fix build errors in paged buffer handling code

From: Mauro Rossi fw_{grow,map}_paged_buf() need to be defined as static inline when CONFIG_FW_LOADER_PAGED_BUF is not enabled, infact fw_free_paged_buf() is also defined as static inline when CONFIG_FW_LOADER_PAGED_BUF is not enabled. Fixes the following mutiple definition building errors for

[PATCH] Revert "kvm: x86: Use task structs fpu field for user"

This reverts commit 240c35a3783ab9b3a0afaba0dde7291295680a6b ("kvm: x86: Use task structs fpu field for user", 2018-11-06). The commit is broken and causes QEMU's FPU state to be destroyed when KVM_RUN is preempted. Fixes: 240c35a3783a ("kvm: x86: Use task structs fpu field for user") Cc:

[PATCH] [v3] page flags: prioritize kasan bits over last-cpuid

ARM64 randdconfig builds regularly run into a build error, especially when NUMA_BALANCING and SPARSEMEM are enabled but not SPARSEMEM_VMEMMAP: #error "KASAN: not enough bits in page flags for tag" The last-cpuid bits are already contitional on the available space, so the result of the

Re: [PATCH] firmware: fix build errors in paged buffer handling code

On Mon, 22 Jul 2019 07:55:36 +0200, Takashi Iwai wrote: > > From: Mauro Rossi > > fw_{grow,map}_paged_buf() need to be defined as static inline > when CONFIG_FW_LOADER_PAGED_BUF is not enabled, > infact fw_free_paged_buf() is also defined as static inline > when CONFIG_FW_LOADER_PAGED_BUF is

Re: [PATCH v4] mmc: host: sdhci-sprd: Fix the incorrect soft reset operation when runtime resuming

On Wed, 17 Jul 2019 at 04:29, Baolin Wang wrote: > > In sdhci_runtime_resume_host() function, we will always do software reset > for all, which will cause Spreadtrum host controller work abnormally after > resuming. What does "software reset for all" means? > > Thus for Spreadtrum platform that

Re: RFC: call_rcu_outstanding (was Re: WARNING in __mmdrop)

On Mon, Jul 22, 2019 at 03:52:05AM -0400, Michael S. Tsirkin wrote: > On Sun, Jul 21, 2019 at 04:31:13PM -0700, Paul E. McKenney wrote: > > On Sun, Jul 21, 2019 at 02:08:37PM -0700, Matthew Wilcox wrote: > > > On Sun, Jul 21, 2019 at 06:17:25AM -0700, Paul E. McKenney wrote: > > > > Also, the

[PATCH] [RESEND] mfd: davinci_voicecodec: remove pointless #include

When building davinci as multiplatform, we get a build error in this file: drivers/mfd/davinci_voicecodec.c:22:10: fatal error: 'mach/hardware.h' file not found The header is only used to access the io_v2p() macro, but the result is already known because that comes from the resource a little

Re: [PATCH v2 18/30] virtio_fs, dax: Set up virtio_fs dax_device

On Mon, 22 Jul 2019 13:20:18 +0200 Christian Borntraeger wrote: > On 22.07.19 12:56, Dr. David Alan Gilbert wrote: > > * Christian Borntraeger (borntrae...@de.ibm.com) wrote: > >> > >> > >> On 18.07.19 16:30, Dan Williams wrote: > >>> On Thu, Jul 18, 2019 at 6:15 AM Vivek Goyal wrote: >

[PATCH] [RESEND v2] structleak: disable STRUCTLEAK_BYREF in combination with KASAN_STACK

The combination of KASAN_STACK and GCC_PLUGIN_STRUCTLEAK_BYREF leads to much larger kernel stack usage, as seen from the warnings about functions that now exceed the 2048 byte limit: drivers/media/i2c/tvp5150.c:253:1: error: the frame size of 3936 bytes is larger than 2048 bytes

[PATCH] cgroup: remove redundant assignment in while loop of cgroup_calc_subtree_ss_mask()

new_ss_mask is always not less than cur_ss_mask. We don not need to update it with cur_ss_mask's value. Signed-off-by: Peng Wang --- kernel/cgroup/cgroup.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/kernel/cgroup/cgroup.c b/kernel/cgroup/cgroup.c index

RE: [PATCH net-next 3/3] net: stmmac: Introducing support for Page Pool

From: Lars Persson Date: Jul/22/2019, 12:11:50 (UTC+00:00) > On Mon, Jul 22, 2019 at 12:18 PM Ilias Apalodimas > wrote: > > > > On Thu, Jul 18, 2019 at 07:48:04AM +, Jose Abreu wrote: > > > From: Jon Hunter > > > Date: Jul/17/2019, 19:58:53 (UTC+00:00) > > > > > > > Let me know if you have

[PATCH] platform/x86/pcengines-apuv2: use KEY_RESTART for front button

From: Enrico Weigelt The keycode KEY_RESTART is more appropriate for the front button, as most people use it for things like restart or factory reset. Signed-off-by: Enrico Weigelt --- drivers/platform/x86/pcengines-apuv2.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] selinux: convert struct sidtab count to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: NitinGote --- security/selinux/ss/sidtab.c | 16

Re: [PATCH glibc] Linux: Include in under __USE_MISC

On Mon, Jul 22, 2019 at 1:31 PM Florian Weimer wrote: > > Historically, (which is included from ) > provided ioctl operations for sockets. User code accessed them > through . The kernel UAPI headers have removed these > definitions in favor of . This commit makes them > available via again.

[PATCH] media: marvell-ccic: mmp: add MODULE_DEVICE_TABLE

This fixes autoloading the module by the OF compatible string. Fixes: 83c40e6611ec ("media: marvell-ccic/mmp: add devicetree support") Signed-off-by: Lubomir Rintel --- drivers/media/platform/marvell-ccic/mmp-driver.c | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH glibc] Linux: Include in under __USE_MISC

Historically, (which is included from ) provided ioctl operations for sockets. User code accessed them through . The kernel UAPI headers have removed these definitions in favor of . This commit makes them available via again. [[[ This is related to this thread: From: Sergei Trofimovich

[PATCH] [v2 net-next] ipvs: reduce kernel stack usage

With the new CONFIG_GCC_PLUGIN_STRUCTLEAK_BYREF_ALL option, the stack usage in the ipvs debug output grows because each instance of IP_VS_DBG_BUF() now has its own buffer of 160 bytes that add up rather than reusing the stack slots: net/netfilter/ipvs/ip_vs_core.c: In function

Re: [PATCH 3/3] platform//x86/pcengines-apuv2: update gpio button definition

On 04.07.19 11:02, Florian Eckert wrote: * Add the gpio number, so the button subsystem can find the right gpio. * Change also the keycode from KEY_SETUP to KEY_RESTART, because it seems more expressive to me and in the Alix-Board, which is the predecessor, there isthis keycode defined

Re: [PATCH 1/3] platform/x86/pcengines-apuv2: add mpcie reset gpio export

On 04.07.19 11:02, Florian Eckert wrote: On APUx we have also mpcie2/mpcie3 reset pins. To make it possible to reset the ports from the userspace, add the definition to this platform device. The gpio can then be exported by the legancy gpio subsystem to toggle the mpcie reset pin.

Re: [PATCH 1/3] printk: Allow architecture-specific timestamping function

On Mon 2019-07-22 11:33:28, Marc Zyngier wrote: > printk currently relies on local_clock to time-stamp the kernel > messages. In order to allow the timestamping (and only that) > to be overridden by architecture-specific code, let's declare > a new timestamp_clock() function, which gets used by

Re: [PATCH v2 18/30] virtio_fs, dax: Set up virtio_fs dax_device

On 22.07.19 12:56, Dr. David Alan Gilbert wrote: > * Christian Borntraeger (borntrae...@de.ibm.com) wrote: >> >> >> On 18.07.19 16:30, Dan Williams wrote: >>> On Thu, Jul 18, 2019 at 6:15 AM Vivek Goyal wrote: On Wed, Jul 17, 2019 at 07:27:25PM +0200, Halil Pasic wrote: > On Wed,

Re: [PATCH net-next 3/3] net: stmmac: Introducing support for Page Pool

On Mon, Jul 22, 2019 at 12:18 PM Ilias Apalodimas wrote: > > On Thu, Jul 18, 2019 at 07:48:04AM +, Jose Abreu wrote: > > From: Jon Hunter > > Date: Jul/17/2019, 19:58:53 (UTC+00:00) > > > > > Let me know if you have any thoughts. > > > > Can you try attached patch ? > > > > The log says

Re: [PATCH v2 1/3] mm: document zone device struct page field usage

On Sun, Jul 21, 2019 at 10:13:45PM -0700, Ira Weiny wrote: > On Sun, Jul 21, 2019 at 09:02:04AM -0700, Matthew Wilcox wrote: > > On Fri, Jul 19, 2019 at 12:29:53PM -0700, Ralph Campbell wrote: > > > Struct page for ZONE_DEVICE private pages uses the page->mapping and > > > and page->index fields

<    4   5   6   7   8   9   10   11   12   >