Re: [PATCH] Allow automatic kernel taint on unsigned module load to be disabled

Matthew Garrett writes: > Distributions may wish to provide kernels that permit loading of > unsigned modules based on certain policy decisions. Sorry, that's way too vague to accept this patch. So I'm guessing a binary module is behind this vagueness. If you want some other

[PATCH 0/2] constify usb_device_id.

usb_device_id are not supposed to change at runtime. All functions working with usb_device_id provided by work with const usb_device_id. So mark the non-const structs as const. Arvind Yadav (2): [PATCH 1/2] video: fbdev: smscufx: constify usb_device_id. [PATCH 2/2] video: fbdev: udlfb:

[PATCH 2/2] video: fbdev: udlfb: constify usb_device_id.

usb_device_id are not supposed to change at runtime. All functions working with usb_device_id provided by work with const usb_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/video/fbdev/udlfb.c | 2 +- 1 file changed, 1

[PATCH 1/2] video: fbdev: smscufx: constify usb_device_id.

usb_device_id are not supposed to change at runtime. All functions working with usb_device_id provided by work with const usb_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/video/fbdev/smscufx.c | 2 +- 1 file changed, 1

[PATCH 1/8] Input: iforce: constify usb_device_id and fix space before '[' error:

usb_device_id are not supposed to change at runtime. All functions working with usb_device_id provided by work with const usb_device_id. So mark the non-const structs as const. Fix checkpatch.pl error: ERROR: space prohibited before open square bracket '['. Signed-off-by: Arvind Yadav

[PATCH] media: ddbridge: make ddb_info const

Make ddb_info structures const as they are only used during a copy operation. Signed-off-by: Bhumika Goyal --- drivers/media/pci/ddbridge/ddbridge-core.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/media/pci/ddbridge/ddbridge-core.c

[PATCH] ATM-lanai: Delete an error message for a failed memory allocation in lanai_init_one()

From: Markus Elfring Date: Sun, 6 Aug 2017 09:42:52 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Link:

[PATCH] drm/amd/powerplay: fix semicolon.cocci warnings

drivers/gpu/drm/amd/amdgpu/../powerplay/hwmgr/vega10_hwmgr.c:2273:61-62: Unneeded semicolon Remove unneeded semicolon. Generated by: scripts/coccinelle/misc/semicolon.cocci Fixes: bdb8cd10b99d ("drm/amd/powerplay: enable ACG feature on vega10.") CC: Rex Zhu Signed-off-by:

[PATCH 1/3] ATM-iphase: Adjust 11 function calls together with a variable assignment

From: Markus Elfring Date: Sat, 5 Aug 2017 21:39:06 +0200 The script "checkpatch.pl" pointed information out like the following. ERROR: do not use assignment in if condition Thus fix affected source code places. Signed-off-by: Markus Elfring

[PATCH 2/3] ATM-iphase: Delete five error messages for a failed memory allocation

From: Markus Elfring Date: Sat, 5 Aug 2017 22:10:41 +0200 Omit extra messages for a memory allocation failure in these functions. This issue was detected by using the Coccinelle software. Link:

[PATCH 2/7] ALSA: bcd2000: constify usb_device_id.

usb_device_id are not supposed to change at runtime. All functions working with usb_device_id provided by work with const usb_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- sound/usb/bcd2000/bcd2000.c | 2 +- 1 file changed, 1

[PATCH 6/7] ALSA: us122l: constify usb_device_id.

usb_device_id are not supposed to change at runtime. All functions working with usb_device_id provided by work with const usb_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- sound/usb/usx2y/us122l.c | 2 +- 1 file changed, 1

[PATCH] can: c_can_pci: make c_can_pci_data const

Make c_can_pci_data structures const as they are only used during a copy operation. Signed-off-by: Bhumika Goyal --- drivers/net/can/c_can/c_can_pci.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/net/can/c_can/c_can_pci.c

[PATCH 1/7] ALSA: 6fire: constify usb_device_id.

usb_device_id are not supposed to change at runtime. All functions working with usb_device_id provided by work with const usb_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- sound/usb/6fire/chip.c | 2 +- 1 file changed, 1

[PATCH 2/8] Input: xpad: constify usb_device_id.

usb_device_id are not supposed to change at runtime. All functions working with usb_device_id provided by work with const usb_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/input/joystick/xpad.c | 2 +- 1 file changed, 1

[PATCH 5/8] Input: appletouch: constify usb_device_id.

usb_device_id are not supposed to change at runtime. All functions working with usb_device_id provided by work with const usb_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/input/mouse/appletouch.c | 2 +- 1 file changed, 1

[PATCH 6/8] Input: synaptics_usb: constify usb_device_id.

usb_device_id are not supposed to change at runtime. All functions working with usb_device_id provided by work with const usb_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/input/mouse/synaptics_usb.c | 2 +- 1 file

[PATCH 8/8] Input: kbtab: constify usb_device_id.

usb_device_id are not supposed to change at runtime. All functions working with usb_device_id provided by work with const usb_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/input/tablet/kbtab.c | 2 +- 1 file changed, 1

[PATCH 4/8] Input: powermate: constify usb_device_id and fix space before '[' error.

usb_device_id are not supposed to change at runtime. All functions working with usb_device_id provided by work with const usb_device_id. So mark the non-const structs as const. Fix checkpatch.pl error: ERROR: space prohibited before open square bracket '['. Signed-off-by: Arvind Yadav

[PATCH 7/8] Input: acecad: constify usb_device_idi and fix space before '[' error.

usb_device_id are not supposed to change at runtime. All functions working with usb_device_id provided by work with const usb_device_id. So mark the non-const structs as const. Fix checkpatch.pl error: ERROR: space prohibited before open square bracket '['. Signed-off-by: Arvind Yadav

[PATCH 3/8] Input: keyspan_remote: constify usb_device_id.

usb_device_id are not supposed to change at runtime. All functions working with usb_device_id provided by work with const usb_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/input/misc/keyspan_remote.c | 2 +- 1 file

[PATCH 0/8] constify input usb_device_id.

usb_device_id are not supposed to change at runtime. All functions working with usb_device_id provided by work with const usb_device_id. So mark the non-const structs as const. Fix checkpatch.pl error in patch 1,3 and 7: ERROR: space prohibited before open square bracket '['. Arvind Yadav (8):

[PATCH] ATM-nicstar: Delete an error message for a failed memory allocation in ns_init_card()

From: Markus Elfring Date: Sun, 6 Aug 2017 10:10:21 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Link:

Re: [PATCH V2] staging: ccree: Fix format/argument mismatches

On Thu, Aug 3, 2017 at 4:49 PM, Joe Perches wrote: > On Thu, 2017-08-03 at 17:09 +0800, kbuild test robot wrote: >> Hi Joe, >> >> [auto build test WARNING on staging/staging-testing] >> [also build test WARNING on next-20170803] >> [cannot apply to v4.13-rc3] >> [if your patch

[PATCH 0/3] ATM-iphase: Adjustments for some function implementations

From: Markus Elfring Date: Sun, 6 Aug 2017 08:18:28 +0200 A few update suggestions were taken into account from static source code analysis. Markus Elfring (3): Adjust 11 function calls together with a variable assignment Delete five error messages for a

[PATCH 3/3] ATM-iphase: Adjust four checks for null pointers

From: Markus Elfring Date: Sat, 5 Aug 2017 22:30:04 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The script “checkpatch.pl” pointed information out like the following. Comparison to NULL could be written !… Thus

[PATCH 4/7] ALSA: usb-audio: constify usb_device_id.

usb_device_id are not supposed to change at runtime. All functions working with usb_device_id provided by work with const usb_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- sound/usb/card.c | 4 ++-- 1 file changed, 2

[PATCH 7/7] ALSA: usbusx2y: constify usb_device_id.

usb_device_id are not supposed to change at runtime. All functions working with usb_device_id provided by work with const usb_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- sound/usb/usx2y/usbusx2y.c | 2 +- 1 file changed, 1

[PATCH 3/7] ALSA: snd-usb-caiaq: constify usb_device_id.

usb_device_id are not supposed to change at runtime. All functions working with usb_device_id provided by work with const usb_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- sound/usb/caiaq/device.c | 2 +- 1 file changed, 1

[PATCH 0/7] constify ALSA usb_device_id.

usb_device_id are not supposed to change at runtime. All functions working with usb_device_id provided by work with const usb_device_id. So mark the non-const structs as const. Arvind Yadav (7): [PATCH 1/7] ALSA: 6fire: constify usb_device_id. [PATCH 2/7] ALSA: bcd2000: constify

[PATCH 5/7] ALSA: ua101: constify usb_device_id.

usb_device_id are not supposed to change at runtime. All functions working with usb_device_id provided by work with const usb_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- sound/usb/misc/ua101.c | 2 +- 1 file changed, 1

[PATCH] atm: solos-pci: Delete an error message for a failed memory allocation in fpga_probe()

From: Markus Elfring Date: Sun, 6 Aug 2017 10:37:31 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Link:

[PATCH 09/12] [media] media: mx2-emmaprp: constify v4l2_m2m_ops structures

The v4l2_m2m_ops structures are only passed as the only argument to v4l2_m2m_init, which is declared as const. Thus the v4l2_m2m_ops structures themselves can be const. Done with the help of Coccinelle. // @r disable optional_qualifier@ identifier i; position p; @@ static struct v4l2_m2m_ops

[PATCH 10/12] [media] vim2m: constify v4l2_m2m_ops structures

The v4l2_m2m_ops structures are only passed as the only argument to v4l2_m2m_init, which is declared as const. Thus the v4l2_m2m_ops structures themselves can be const. Done with the help of Coccinelle. // @r disable optional_qualifier@ identifier i; position p; @@ static struct v4l2_m2m_ops

[PATCH 08/12] [media] m2m-deinterlace: constify v4l2_m2m_ops structures

The v4l2_m2m_ops structures are only passed as the only argument to v4l2_m2m_init, which is declared as const. Thus the v4l2_m2m_ops structures themselves can be const. Done with the help of Coccinelle. // @r disable optional_qualifier@ identifier i; position p; @@ static struct v4l2_m2m_ops

[PATCH] ATM-ENI: Delete an error message for a failed memory allocation in eni_start()

From: Markus Elfring Date: Sun, 6 Aug 2017 11:15:17 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Link:

Re: [PATCH v2] mmc: mmci_qcom_dml: include mmci_qcom_dml.h and fix #ifdef

On Sun, Aug 6, 2017 at 4:58 AM, Masahiro Yamada wrote: > 2017-08-05 7:10 GMT+09:00 Arnd Bergmann : >> On Fri, Aug 4, 2017 at 3:34 PM, Masahiro Yamada >> wrote: >>> Include mmci_qcom_dml.h from mmci_qcom_dml.c to fix the

RE: [PATCH] i2c: mux: rename files to not have superfluous prefixes

> -Original Message- > From: Peter Rosin [mailto:p...@axentia.se] > Sent: Friday, August 04, 2017 12:08 PM > To: linux-kernel@vger.kernel.org > Cc: Peter Rosin ; Wolfram Sang ; > linux-...@vger.kernel.org; Peter Korsgaard ; >

Re: [PATCH 4/5] mtd: block2mtd: Add support for deleting block2mtd mapping

Pali, Am 25.07.2017 um 16:24 schrieb Pali Rohár: > On Friday 21 July 2017 21:56:41 Richard Weinberger wrote: >> Pali, >> >> On Fri, Jun 2, 2017 at 5:43 PM, Pali Rohár wrote: >>> This patch allows user to delete block2mtd mapping via parameters file >>>

drivers/gpu/drm/i915/selftests/i915_gem_request.c:344: error: 'request' may be used uninitialized in this function

Hi Jan, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 0fdd951c9bef93637d5af036851e7a5632fbd6c3 commit: 7e6091209f7f73e2a81943020793b5ad26d645c6 x86/build: Permit building with old make versions date: 2 months

Re: [PATCH v3 3/5] ACPI: Introduce DMA ranges parsing

On Sun, Aug 06, 2017 at 01:12:55PM +0800, kbuild test robot wrote: > Hi Lorenzo, > > [auto build test ERROR on pm/linux-next] > [also build test ERROR on v4.13-rc3 next-20170804] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] > > url:

Re: [PATCH 5/5] ubi: Allow to use read-only UBI volume with not enough PEBs

Pali, Am 25.07.2017 um 16:27 schrieb Pali Rohár: >> I fear this is not correct, it will disable a legit self-check of UBI >> volumes. >> If the read-only volume is corrupted/truncated and you miss PEBs, this >> check will no longer >> trigger. >> >> Especially when dealing with nanddumps,

undefined reference to `_GLOBAL_OFFSET_TABLE_'

Hi Nicholas, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 0fdd951c9bef93637d5af036851e7a5632fbd6c3 commit: 799c43415442414b1032580c47684cb709dfed6d kbuild: thin archives make default for all archs date: 5

Re: [PATCH 0/7] cfag12864b: Fine-tuning for cfag12864b_init()

> Date: Sat, 10 Sep 2016 16:17:01 +0200 > > Some update suggestions were taken into account > from static source code analysis. > > Markus Elfring (7): > Use kmalloc_array() > Delete an error message for a failed kmalloc_array() call > Return directly if the driver "ks0108" was not

Re: [PATCH 00/30] ACPI-processor: Fine-tuning for several function implementations

> Date: Tue, 9 Sep 2016 20:15:05 +0200 > > Several update suggestions were taken into account > from static source code analysis. > > Markus Elfring (30): > Use kmalloc_array() in acpi_processor_get_performance_states() > Improve two size determinations in

Re: [PATCH v2] mmc: mmci_qcom_dml: include mmci_qcom_dml.h and fix #ifdef

On 6 August 2017 at 11:32, Arnd Bergmann wrote: > On Sun, Aug 6, 2017 at 4:58 AM, Masahiro Yamada > wrote: >> 2017-08-05 7:10 GMT+09:00 Arnd Bergmann : >>> On Fri, Aug 4, 2017 at 3:34 PM, Masahiro Yamada >>>

Re: [PATCH 00/13] DRBD-receiver: Fine-tuning for six function implementations

> Date: Sat, 10 Sep 2016 22:13:22 +0200 > > Several update suggestions were taken into account > from static source code analysis. > > Markus Elfring (13): > Use kmalloc_array() in receive_uuids() > Delete an error message for a failed kmalloc_array() call > Move an assignment in

Re: [PATCH] arm64: dts: rockchip: include opp dtsi for rk3399 firefly

Am Donnerstag, 3. August 2017, 15:02:00 CEST schrieb Jianqun Xu: > Add opp tables for cpu cluster0 and cluster1 by including > rk3399-opp.dtsi. > > Signed-off-by: Jianqun Xu applied for 4.14 Thanks Heiko

Re: [PATCH v2] mmc: mmci_qcom_dml: include mmci_qcom_dml.h and fix #ifdef

On 04/08/17 23:10, Arnd Bergmann wrote: How about linking the DML code into the mmci module and making that Kconfig option a 'bool'? Yes, I think making this bool and exporting the two symbols should fix this. It does not make sense to make dml helpers a module anyway. If it sounds okay,

[PATCH 04/12] [media] V4L2: platform: rcar_jpu: constify v4l2_m2m_ops structures

The v4l2_m2m_ops structures are only passed as the only argument to v4l2_m2m_init, which is declared as const. Thus the v4l2_m2m_ops structures themselves can be const. Done with the help of Coccinelle. // @r disable optional_qualifier@ identifier i; position p; @@ static struct v4l2_m2m_ops

[PATCH 01/12] [media] st-delta: constify v4l2_m2m_ops structures

The v4l2_m2m_ops structures are only passed as the only argument to v4l2_m2m_init, which is declared as const. Thus the v4l2_m2m_ops structures themselves can be const. Done with the help of Coccinelle. // @r disable optional_qualifier@ identifier i; position p; @@ static struct v4l2_m2m_ops

[PATCH] hamradio: baycom: make hdlcdrv_ops const

Make hdlcdrv_ops structures const as they are only passed to hdlcdrv_register function. The corresponding argument is of type const, so make the structures const. Signed-off-by: Bhumika Goyal --- drivers/net/hamradio/baycom_par.c | 2 +-

[PATCH 11/12] [media] exynos4-is: constify v4l2_m2m_ops structures

The v4l2_m2m_ops structures are only passed as the only argument to v4l2_m2m_init, which is declared as const. Thus the v4l2_m2m_ops structures themselves can be const. Done with the help of Coccinelle. // @r disable optional_qualifier@ identifier i; position p; @@ static struct v4l2_m2m_ops

[PATCH 00/12] constify v4l2_m2m_ops structures

The v4l2_m2m_ops structures are only passed as the only argument to v4l2_m2m_init, which is declared as const. Thus the v4l2_m2m_ops structures themselves can be const. Done with the help of Coccinelle. --- drivers/media/platform/exynos-gsc/gsc-m2m.c |2 +-

[PATCH 06/12] [media] exynos-gsc: constify v4l2_m2m_ops structures

The v4l2_m2m_ops structures are only passed as the only argument to v4l2_m2m_init, which is declared as const. Thus the v4l2_m2m_ops structures themselves can be const. Done with the help of Coccinelle. // @r disable optional_qualifier@ identifier i; position p; @@ static struct v4l2_m2m_ops

[PATCH 07/12] [media] bdisp: constify v4l2_m2m_ops structures

The v4l2_m2m_ops structures are only passed as the only argument to v4l2_m2m_init, which is declared as const. Thus the v4l2_m2m_ops structures themselves can be const. Done with the help of Coccinelle. // @r disable optional_qualifier@ identifier i; position p; @@ static struct v4l2_m2m_ops

[PATCH 05/12] [media] vcodec: mediatek: constify v4l2_m2m_ops structures

The v4l2_m2m_ops structures are only passed as the only argument to v4l2_m2m_init, which is declared as const. Thus the v4l2_m2m_ops structures themselves can be const. Done with the help of Coccinelle. // @r disable optional_qualifier@ identifier i; position p; @@ static struct v4l2_m2m_ops

[PATCH 12/12] [media] mtk-mdp: constify v4l2_m2m_ops structures

The v4l2_m2m_ops structures are only passed as the only argument to v4l2_m2m_init, which is declared as const. Thus the v4l2_m2m_ops structures themselves can be const. Done with the help of Coccinelle. // @r disable optional_qualifier@ identifier i; position p; @@ static struct v4l2_m2m_ops

[PATCH 02/12] [media] media: ti-vpe: vpe: constify v4l2_m2m_ops structures

The v4l2_m2m_ops structures are only passed as the only argument to v4l2_m2m_init, which is declared as const. Thus the v4l2_m2m_ops structures themselves can be const. Done with the help of Coccinelle. // @r disable optional_qualifier@ identifier i; position p; @@ static struct v4l2_m2m_ops

[PATCH 03/12] [media] s5p-g2d: constify v4l2_m2m_ops structures

The v4l2_m2m_ops structures are only passed as the only argument to v4l2_m2m_init, which is declared as const. Thus the v4l2_m2m_ops structures themselves can be const. Done with the help of Coccinelle. // @r disable optional_qualifier@ identifier i; position p; @@ static struct v4l2_m2m_ops

Re: [PATCH 1/2] arm64: dts: rockchip: Add cpu operating points for RK3328 SoC

Am Freitag, 4. August 2017, 11:33:37 CEST schrieb Finley Xiao: > This patch adds basic OPP entries for RK3328 SoC. > > Signed-off-by: Finley Xiao applied for 4.14 Thanks Heiko

Re: [PATCH 5/5] ubi: Allow to use read-only UBI volume with not enough PEBs

On Sunday 06 August 2017 11:43:25 Richard Weinberger wrote: > Pali, > > Am 25.07.2017 um 16:27 schrieb Pali Rohár: > >> I fear this is not correct, it will disable a legit self-check of > >> UBI volumes. If the read-only volume is corrupted/truncated and > >> you miss PEBs, this check will no

Re: [PATCH v2] ARM: dts: rockchip: rk322x: add spi node and spi pinctrl

Hi, Am Donnerstag, 3. August 2017, 10:36:49 CEST schrieb Huibin Hong: > Add spi node and spi pinctrl for rk322x > > Signed-off-by: Huibin Hong [...] > + }; > + > wdt: watchdog@110a { > compatible = "rockchip,rk322x-wdt", "snps,dw-wdt";

Re: [PATCH] ARM: dts: rockchip: rk3288 add more iommu nodes

Am Donnerstag, 3. August 2017, 10:04:03 CEST schrieb Simon Xue: > Add IEP/ISP/VPU/HEVC iommu nodes > > Signed-off-by: Simon Xue applied for 4.14 Thanks Heiko

Re: [PATCH 00/11] virtio-console: Fine-tuning for 14 function implementations

> Date: Wed, 14 Sep 2016 15:43:21 +0200 > > Several update suggestions were taken into account > from static source code analysis. > > Markus Elfring (11): > Use kmalloc_array() in init_vqs() > Less function calls in init_vqs() after error detection > Rename a jump label in init() >

Re: [PATCH] ARM: dts: rockchip: convert rk3288 device tree files to 64 bits

Am Donnerstag, 3. August 2017, 11:21:36 CEST schrieb Tao Huang: > In order to be able to use more than 4GB of RAM when the LPAE is > activated, the dts must be converted in 64 bits. > > Signed-off-by: Tao Huang applied for 4.14 Thanks Heiko

Re: [PATCH v2] mmc: mmci_qcom_dml: include mmci_qcom_dml.h and fix #ifdef

Hi Masahiro, [auto build test ERROR on linus/master] [also build test ERROR on v4.13-rc3 next-20170804] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] ARM: rockchip: select ARCH_DMA_ADDR_T_64BIT for LPAE

Am Dienstag, 1. August 2017, 17:55:55 CEST schrieb Tao Huang: > Rockchip RK3288 has some 64-bit capable DMA and therefore needs > dma_addr_t to be a 64-bit size. One user is the Mali GPU. > > Signed-off-by: Tao Huang applied for 4.14 Thanks Heiko

Re: [PATCH v3 3/5] ACPI: Introduce DMA ranges parsing

On Sun, Aug 6, 2017 at 11:42 AM, Lorenzo Pieralisi wrote: > On Sun, Aug 06, 2017 at 01:12:55PM +0800, kbuild test robot wrote: >> Hi Lorenzo, >> >> [auto build test ERROR on pm/linux-next] >> [also build test ERROR on v4.13-rc3 next-20170804] >> [if your patch is

Re: [PATCH v2] dma-mapping: skip USB devices when configuring DMA during probe

Hi Johan, [auto build test ERROR on driver-core/driver-core-testing] [also build test ERROR on v4.13-rc3 next-20170804] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH 03/18] staging: typec: tcpm: Split tcpm code into tcpm-core.c and tcpm-helpers.c

This is a preparation patch for adding more helpers. Signed-off-by: Hans de Goede --- drivers/staging/typec/Makefile| 2 + drivers/staging/typec/{tcpm.c => tcpm-core.c} | 40 -- drivers/staging/typec/tcpm-helpers.c | 60

[PATCH 07/18] staging: typec: fusb302: Use client->irq as irq if set

The fusb302 is also used on x86 systems where the platform code sets the irq in client->irq and there is no gpio named fcs,int_n. Signed-off-by: Hans de Goede --- drivers/staging/typec/fusb302/fusb302.c | 10 +++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff

[PATCH 05/18] staging: typec: fusb302: Set max supply voltage to 5V

Anything higher then 5V may damage hardware not capable of it, so the only sane default here is 5V. If a board is able to handle a higher voltage that should come from board specific data such as device-tree and not be hard coded into the fusb302 code. Signed-off-by: Hans de Goede

[PATCH 15/18] power: supply: bq24190_charger: Get input_current_limit from our supplier

On some devices the USB Type-C port power (USB PD 2.0) negotiation is done by a separate port-controller IC, while the current limit is controlled through another (charger) IC. It has been decided to model this by modelling the external Type-C power brick (adapter/charger) as a power-supply class

[PATCH 09/18] staging: typec: fusb302: Use tcpm_set_current_limit_psy

Register a power_supply and use tcpm_set_current_limit_psy as set_current_limit so that another driver (e.g. the charger driver) can pick the limit up and configure the system accordingly. Signed-off-by: Hans de Goede --- drivers/staging/typec/fusb302/fusb302.c | 18

[PATCH 11/18] power: supply: Fix power_supply_am_i_supplied to return -ENODEV when apropriate

Commit 2848e039c562 ("power: supply: Make power_supply_am_i_supplied return -ENODEV if there are no suppliers") was supposed to make power_supply_am_i_supplied() return -ENODEV when there are no supplies which supply the supply passed to it. But instead it will only return -ENODEV when there are

[PATCH 18/18] i2c-cht-wc: Add device-properties for fusb302 integration

Add device-properties to make the bq24292i controller connected to the bus get its input-current-limit from the fusb302 Type-C port controller which is used on boards with the cht-wc PMIC. Signed-off-by: Hans de Goede --- drivers/i2c/busses/Kconfig | 5 +

[PATCH 13/18] power: supply: bq24190_charger: Export 5V boost converter as regulator

Register the 5V boost converter as a regulator named "regulator-bq24190-usb-vbus". Note the name includes "bq24190" because the bq24190 family is also used on ACPI devices where there are no device-tree phandles, so regulator_get will fallback to the name and thus it must be unique on the system.

[PATCH 17/18] platform/x86: intel_cht_int33fe Update fusb302 type string, add properties

The fusb302 driver as merged in staging uses "typec_fusb302" as i2c-id rather then just "fusb302" and needs us to set a number of device- properties, adjust the intel_cht_int33fe driver accordingly. One of the properties set is max-snk-mv which makes the fusb302 driver negotiate up to 12V

[PATCH 12/18] power: supply: Add power_supply_set_input_current_limit_from_supplier helper

On some devices the USB Type-C port power (USB PD 2.0) negotiation is done by a separate port-controller IC, while the current limit is controlled through another (charger) IC. It has been decided to model this by modelling the external Type-C power brick (adapter/charger) as a power-supply class

[PATCH 06/18] staging: typec: fusb302: Get max snk mv/ma/mw from device-properties

This is board specific info so it should come from board config, such as devicetree. I've chosen to prefix these with "fcs," treating them as fusb302 driver specific. We may want to revisit to replace these with properties which are part of a (to be written) generic type-c controller devicetree

[PATCH 04/18] staging: typec: tcpm: Add helpers for exporting current-limit through a psy

Not all type-c port-controller can control the current-limit directly, in cases where the current limit can not be controlled directly it needs to be exported so that another driver (e.g. the charger driver) can pick the limit up and configure the system accordingly. The power-supply subsys

[PATCH 16/18] power: supply: bq24190_charger: Remove extcon handling

Now that drivers/i2c/busses/i2c-cht-wc.c uses "input-current-limit-from-supplier" instead of "extcon-name" the last user of the bq24190 extcon code is gone, remove it. Signed-off-by: Hans de Goede --- drivers/power/supply/bq24190_charger.c | 107

[PATCH 10/18] staging: typec: fusb302: Add support for fcs,vbus-regulator-name device-property

On devicetree platforms the fusb302 dt-node will have a vbus regulator property with a phandle to the regulator. On ACPI platforms, there are no phandles and we need to get the vbus by a system wide unique name. Add support for a new "fcs,vbus-regulator-name" device-property which ACPI platform

[PATCH 08/18] staging: typec: fusb302: Add support for USB2 charger detection through extcon

The fusb302 port-controller relies on an external device doing USB2 charger-type detection. The Intel Whiskey Cove PMIC with which the fusb302 is combined on some X86/ACPI platforms already has a charger-type detection driver which uses extcon to communicate the detected charger-type. This

[PATCH 14/18] power: supply: bq24190_charger: Add input_current_limit property

Export the input current limit of the charger as a POWER_SUPPLY_PROP_INPUT_CURRENT_LIMIT property on the charger power_supply class device. Signed-off-by: Hans de Goede --- drivers/power/supply/bq24190_charger.c | 35 ++ 1 file changed, 35

[PATCH 02/18] staging: typec: tcpm: Add extcon helper functions for USB2 current limit detect

Some type-c port-controllers, such as the fusb302 port-controller, rely on an external device doing USB2 charger-type detection. Existing PMIC (and charger) drivers already use extcon to communicate the detected charger-type from the PMIC (extcon) driver to the charger driver. Rather then

[PATCH 01/18] staging: typec: tcpm: Add get_usb2_current_limit tcpc_dev callback

A Rp signalling the default current limit indicates that we're possibly connected to an USB2 power-source. In some cases the type-c port-controller may provide the capability to detect the current-limit for USB2 power-sources (through e.g. BC1.2 detection). This commit adds an optional

[PATCH 00/18] Hookup typec power-negotation to the PMIC and charger

Hi All, This series implements a number of typec changes discussed a while back: - It exports the negotiated voltage and max-current in the form of a power-supply class device which represents the USB Type-C power-brick (adapter/charger) - It adds a

Re: [PATCH 09/18] staging: typec: fusb302: Use tcpm_set_current_limit_psy

On 08/06/2017 05:35 AM, Hans de Goede wrote: Register a power_supply and use tcpm_set_current_limit_psy as set_current_limit so that another driver (e.g. the charger driver) can pick the limit up and configure the system accordingly. Signed-off-by: Hans de Goede ---

Re: [PATCH 04/18] staging: typec: tcpm: Add helpers for exporting current-limit through a psy

On 08/06/2017 07:21 AM, Hans de Goede wrote: Hi, On 06-08-17 16:13, Guenter Roeck wrote: On 08/06/2017 05:35 AM, Hans de Goede wrote: Not all type-c port-controller can control the current-limit directly, in cases where the current limit can not be controlled directly it needs to be exported

Re: [PATCH 01/18] staging: typec: tcpm: Add get_usb2_current_limit tcpc_dev callback

On 08/06/2017 07:29 AM, Hans de Goede wrote: Hi, On 06-08-17 16:18, Guenter Roeck wrote: On 08/06/2017 05:35 AM, Hans de Goede wrote: A Rp signalling the default current limit indicates that we're possibly connected to an USB2 power-source. In some cases the type-c port-controller may provide

Re: [PATCH 10/18] staging: typec: fusb302: Add support for fcs,vbus-regulator-name device-property

Hi, On 06-08-17 16:30, Guenter Roeck wrote: On 08/06/2017 05:35 AM, Hans de Goede wrote: On devicetree platforms the fusb302 dt-node will have a vbus regulator property with a phandle to the regulator. On ACPI platforms, there are no phandles and we need to get the vbus by a system wide

Re: [PATCH 10/18] staging: typec: fusb302: Add support for fcs,vbus-regulator-name device-property

On 08/06/2017 07:52 AM, Hans de Goede wrote: Hi, On 06-08-17 16:30, Guenter Roeck wrote: On 08/06/2017 05:35 AM, Hans de Goede wrote: On devicetree platforms the fusb302 dt-node will have a vbus regulator property with a phandle to the regulator. On ACPI platforms, there are no phandles and

[PATCH v06 34/36] uapi: break dependency loop between and

Name structs in linux/hdlc/ioctl.h and forward declare and use them in linux/if.h. Then include linux/if.h in linux/hdlc/ioctl.h to fix user space compilation problem: hdlc/ioctl.h:73:14: error: ‘IFNAMSIZ’ undeclared here (not in a function) char master[IFNAMSIZ]; /* Name of master FRAD device

[PATCH v06 15/36] uapi linux/socket.h: include sys/socket.h in user space

This libc header has sockaddr definition in user space. Fixes user space compilation errors like these from kernel headers including only linux/socket.h: error: field ‘ifru_addr’ has incomplete type struct sockaddr ifru_addr; error: field ‘_sockaddr’ has incomplete type struct sockaddr

[PATCH v06 21/36] uapi linux/kexec.h: use __kernel_size_t instead of size_t

Fixes userspace compilation error: error: unknown type name ‘size_t’ size_t bufsz; Signed-off-by: Mikko Rapeli Cc: ke...@lists.infradead.org Cc: Eric Biederman --- include/uapi/linux/kexec.h | 4 ++-- 1 file changed, 2 insertions(+), 2

[PATCH v06 08/36] uapi asm-generic/shmbuf.h: include fixes

Include linux/types.h and asm/msgbuf.h and use __kernel_size_t instead of size_t. Fixes userspace compilation errors like: error: field ‘shm_perm’ has incomplete type struct ipc64_perm shm_perm; /* operation perms */ error: unknown type name ‘size_t’ error: unknown type name ‘__kernel_time_t’

[PATCH v06 04/36] uapi scsi/scsi_netlink_fc.h: use __u16, __u32 and __u64 from linux/types.h

Fixes userspace compilation errors like: scsi/scsi_netlink_fc.h:60:2: error: expected specifier-qualifier-list before ‘uint64_t’ Signed-off-by: Mikko Rapeli Cc: linux-s...@vger.kernel.org --- include/uapi/scsi/scsi_netlink_fc.h | 16 1 file changed, 8

[PATCH v06 23/36] uapi linux/coda.h: use __kernel_pid_t and add u_short etc definitions for userspace

Fixes userspace compilation errors about unknown pid_t, u_short etc types. Signed-off-by: Mikko Rapeli Cc: Jan Harkes Cc: codal...@coda.cs.cmu.edu --- include/uapi/linux/coda.h | 11 +-- 1 file changed, 9 insertions(+), 2 deletions(-) diff

  1   2   3   4   5   6   7   8   >