[lkp-robot] [irda] 66d98e78e4: BUG:unable_to_handle_kernel

FYI, we noticed the following commit: commit: 66d98e78e44ccb969cb3196995759d200e64b49b ("irda: move net/irda/ to drivers/staging/irda/net/") url: https://github.com/0day-ci/linux/commits/Greg-Kroah-Hartman/irda-move-it-to-drivers-staging-so-we-can-delete-it/20170829-090816 in testcase: trinity

Re: [lkp-robot] [irda] 66d98e78e4: BUG:unable_to_handle_kernel

On 08/30, Greg Kroah-Hartman wrote: >On Wed, Aug 30, 2017 at 02:04:11PM +0800, kernel test robot wrote: >> FYI, we noticed the following commit: >> >> commit: 66d98e78e44ccb969cb3196995759d200e64b49b ("irda: move net/irda/ to >> drivers/staging/irda/net/") >> url: >>

Re: [lkp-robot] [irda] 66d98e78e4: BUG:unable_to_handle_kernel

On Wed, Aug 30, 2017 at 02:04:11PM +0800, kernel test robot wrote: > FYI, we noticed the following commit: > > commit: 66d98e78e44ccb969cb3196995759d200e64b49b ("irda: move net/irda/ to > drivers/staging/irda/net/") > url: >

Re: [PATCH] staging: r8822be: Fix typo for CONFIG_RTLWIFI_DEBUG

Indeed, sorry I missed that as well. So what should we make of that #ifdef? The code inside it doesn't compile (anymore? I didn't find any development history for that patch except the original mail), as there is no definition of struct submit_ctx in the headers (for other rtl drivers - 8188eu,

Re: [PATCH v3 1/6] android: binder: Refactor prev and next buffer into a helper function

On Tue, Aug 29, 2017 at 05:46:57PM -0700, Sherry Yang wrote: > Use helper functions buffer_next and buffer_prev instead > of list_entry to get the next and previous buffers. > > Signed-off-by: Sherry Yang > --- > drivers/android/binder_alloc.c | 24 +++-

[PATCH 08/28] staging: unisys: visorbus: Convert macros to functions.

Several macros in visorchannel.c were doing complex arithmetic, converted them to functions so that valid type checking could be done. Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/visorbus/visorchannel.c | 25

[PATCH 04/28] staging: unisys: visornic: Fix up existing function comments.

From: David Binder Refactors existing static function comments to increase code readability. Signed-off-by: David Binder Signed-off-by: David Kershner Reviewed-by: Tim Sell ---

[PATCH 12/28] staging: unisys: visorbus: Consolidate controlvm channel creation.

The functions to create the controlvm channel were disjointed and ignoring information that was available. This patch consolidates it so it clearer what is happening. Signed-off-by: David Kershner Reviewed-by: Tim Sell ---

[PATCH 11/28] staging: unisys: include: Add comment next to mutex.

Checkpatch reports an error that no comment was next to the mutex lock. Add an appropriate message for the lock. Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/include/visorbus.h | 6 +++--- 1 file changed, 3

[PATCH 07/28] staging: unisys: visorbus: Fix parameter alignment.

Fixed the following checkpatch warning: visorchannel.c:443: CHECK: Alignment should match open parenthesis Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/visorbus/visorchannel.c | 2 +- 1 file changed, 1

[PATCH 10/28] staging: unisys: Don't check for null before getting driver device.

The macro to convert to the driver object was giving a checkpatch warning when it ateempted to check for a null driver. It would return NULL if it found it, but only one location was checking to see if it was NULL. Remove the check in the MACRO and do it prior to calling the macro if required.

[PATCH 05/28] staging: unisys: visornic: Fix miscellaneous block comment format issues.

From: David Binder Fixes miscellaneous formatting issues with several block comments throughout visornic_main.c. Signed-off-by: David Binder Signed-off-by: David Kershner Reviewed-by: Tim Sell

[PATCH 22/28] staging: unisys: visorbus: use all 80 characters for multi-line messages

The file visorchipset had a bunch of comments that were not using the full screen before they wrapped, update the comments to wrap at 80 characters instead. Signed-off-by: David Kershner Reviewed-by: Tim Sell ---

[PATCH 19/28] staging: unisys: visorbus: remove uneeded initializations

Several variables were initialized when not needed. Remove the extraneous initializations. Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/visorbus/visorchipset.c | 4 ++-- 1 file changed, 2 insertions(+), 2

[PATCH 20/28] staging: unisys: visorbus: Move parser functions location in file.

The parser functions were defined at the top of the file even though they were not referenced until later in the file. This patch moves them closer to where they are defined so they can be easily referenced. Signed-off-by: David Kershner Reviewed-by: Tim Sell

[PATCH 28/28] staging: unisys: change pr_err to dev_err in visor_check_channel

From: Sameer Wadgaonkar Changing pr_err to dev_err in visor_check_channel. Added device as an argument to visor_check_channel to pass into dev_err. Signed-off-by: Sameer Wadgaonkar Signed-off-by: David Kershner

[PATCH 14/28] staging: unisys: visorbus: Remove useless initialization.

The variable ctx was allocated with kzalloc, so all the data inside is zero, no need to reset it to 0. Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/visorbus/visorchipset.c | 3 --- 1 file changed, 3

[PATCH 23/28] staging: unisys: visornic: Remove unnecessary return values

From: David Binder Removes unnecessary return value in send_rcv_posts_if_needed(), since NAPI polling functions do not return errors. Signed-off-by: David Binder Signed-off-by: David Kershner Reviewed-by: Tim Sell

[PATCH 13/28] staging: unisys: visorbus: Remove useless comment.

Currently setting it in the right location, so no longer not sure. Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/visorbus/visorchipset.c | 2 -- 1 file changed, 2 deletions(-) diff --git

[PATCH 15/28] staging: unisys: visorbus: Remove check for valid parm_addr.

The variable parm_addr will never be null, so no need to check for it. Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/visorbus/visorchipset.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 16/28] staging: unisys: visorbus: Split else if blocks into multiple if.

Visorbus_configure had a block of "else if" clauses at the beginning of the function. Simplify this to just being "if" clauses since each code block ended with a goto. Signed-off-by: David Kershner Reviewed-by: Tim Sell ---

[PATCH 18/28] staging: unisys: visorbus: Remove useless else clause in visorutil_spar_detect.

The function visorutil_spar_detect had an if clause that returns from the function, no need to do the rest of the code in an else clause. Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/visorbus/visorchipset.c |

[PATCH 17/28] staging: unisys: Change data to point to visor_controlvm_parameters_header.

The data field was being defined as a character array and then casted into a visor_controlvm_parameters_header structure. This patch converts it to just point to the visor_controlvm_parameters_header structure. The data following the header is still behind the header_info. Reported-by: Greg

[PATCH 00/28] staging: unisys: More updates to make the code more readable.

Checkpatch cleanups and other misc cleanups. David Binder (3): staging: unisys: visornic: Fix up existing function comments. staging: unisys: visornic: Fix miscellaneous block comment format issues. staging: unisys: visornic: Remove unnecessary return values David Kershner (21): staging:

[PATCH 27/28] staging: unisys: visorbus: remove EXPORT_SYMBOL_GPL for visor_check_channel

From: Sameer Wadgaonkar Removing EXPORT_SYMBOL_GPU from visor_check_channel since it is used only in visorbus. Signed-off-by: Sameer Wadgaonkar Signed-off-by: David Kershner Reviewed-by: Tim Sell

[PATCH 26/28] staging: unisys: visorbus: Fix up GUID definition

Fix up the GUID definition to remove some checkpatch warnings as well as using the whole width of the screen. Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/visorbus/visorchipset.c | 5 ++--- 1 file changed, 2

[PATCH 09/28] staging: unisys: visorbus: Use __func__ instead of name.

The dev_err was using the hardcoded function name, as reported by checkpatch, it should be using __func__. Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/visorbus/visorchipset.c | 2 +- 1 file changed, 1

Re: [PATCH] staging: r8822be: Fix typo for CONFIG_RTLWIFI_DEBUG

On 08/30/2017 02:58 AM, Andreas Ziegler wrote: Indeed, sorry I missed that as well. So what should we make of that #ifdef? The code inside it doesn't compile (anymore? I didn't find any development history for that patch except the original mail), as there is no definition of struct submit_ctx

Re: [PATCH v3 08/11] power: supply: bq24190_charger: Export 5V boost converter as regulator

Hi, On Wed, Aug 30, 2017 at 07:46:50AM -0700, Tony Lindgren wrote: > * Hans de Goede [170830 02:49]: > > Register the 5V boost converter as a regulator named "usb_otg_vbus". > > > > This commit also adds support for bq24190_platform_data, through which > > non device-tree

Re: [PATCH v3 09/11] power: supply: bq24190_charger: Get input_current_limit from our supplier

Hi, On Wed, Aug 30, 2017 at 07:47:46AM -0700, Tony Lindgren wrote: > * Hans de Goede [170830 02:49]: > > 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

[PATCH 25/28] staging: unisys: visorbus: just check for GUID

Every channel_type must have a valid GUID, checking for the name was just redundant. Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/visorbus/visorbus_main.c | 4 +--- 1 file changed, 1 insertion(+), 3

[PATCH 24/28] staging: unisys: Use size of channel defined in the channel.

The size of the channel should be pulled from the channel header, not from the message. All channels must be at least the size of the channel_header. Signed-off-by: David Kershner Reviewed-by: Tim Sell ---

[PATCH 21/28] staging: unisys: visorchipset: Shorten parser_init_byte_stream.

Shorten the name of the function parser_init_byte_stream to just parser_init_stream. Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/visorbus/visorchipset.c | 7 +++ 1 file changed, 3 insertions(+), 4

[PATCH 03/28] staging: unisys: visorbus: visorbus_main.c: Fix return values for checks in visorbus_register_visor_driver.

From: Sameer Wadgaonkar The error return values for the drv->probe, drv->remove, drv->pause and drv->resume checks should be -EINVAL instead of -ENODEV. Reported-by: Greg Kroah-Hartman Signed-off-by: Sameer Wadgaonkar

[PATCH 06/28] staging: unisys: visorbus: Clean up vmcall address function.

The function vmcall address needed to be cleaned up. The structure vmcall_controlvm_addr was not needed so it was removed and was replaced with vmcall_io_controlvm_addr_params since it needs to be allocated on the heap for DMA access. With the structure removed and the fields as local variables,

[PATCH 01/28] staging: unisys: use the kernel min define

The kernel already provides a min function, we should be using that instead of creating our own MINNUM. Reviewed-by: Sameer Wadgaonkar Signed-off-by: David Kershner Reviewed-by: Tim Sell ---

[PATCH 02/28] staging: unisys: visorbus: visorchipset.c: Fix bug in parser_init_byte_stream.

From: Sameer Wadgaonkar This patch fixes a bug in the function parser_init_byte_stream() by removing the call to parser_done from goto err_finish_ctx. The function parser_done() decrements chipset_dev->controlvm_payload_bytes_buffered which is not incremented before

[PATCH 2/4] staging: fsl-mc: dpio: add congestion notification support

Add support for Congestion State Change Notifications (CSCN), which allow DPIO users to be notified when a congestion group changes its state (due to hitting the entrance / exit threshold). Signed-off-by: Ioana Radulescu Signed-off-by: Radu Alexe

[PATCH 4/4] staging: fsl-dpaa2/eth: move generic FD defines to DPIO

Previous commits: 6e2387e8f19e ("staging: fsl-dpaa2/eth: Add Freescale DPAA2 Ethernet driver") 39163c0ce0f4 ("staging: fsl-dpaa2/eth: Errors checking update") have added bits that are not specific to the WRIOP accelerator. Move these where they belong (in DPIO) such that other accelerators can

[PATCH 1/4] staging: fsl-mc: dpio: add frame list format support

Add support for dpaa2_fd_list format, i.e. dpaa2_fl_entry structure and accessors. Frame list entries (FLEs) are similar, but not identical to frame descriptors (FDs): + "F" (final) bit - FMT[b'01] is reserved - DD, SC, DROPP bits (covered by "FD compatibility" field in FLE case) - FLC[5:0] not

[PATCH 0/4] staging: fsl-mc: dpio: add dpseci dependencies

This patch set adds support for functionalities needed by the upcoming dpseci (Data Path SEC Interface) object device driver: -Frame List Entries (FLEs) -Congestion State Change Notifications (CSCNs) -Order Preservation An RFC has been previously submitted:

Re: [PATCH v3 3/6] android: binder: Move buffer out of area shared with user space

On Tue, Aug 29, 2017 at 05:46:59PM -0700, Sherry Yang wrote: > Binder driver allocates buffer meta data in a region that is mapped > in user space. These meta data contain pointers in the kernel. > > This patch allocates buffer meta data on the kernel heap that is > not mapped in user space, and

[PATCH v3 11/11] 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 v3 00/11] Hookup typec power-negotation to the PMIC and charger

Hi All, Here is v3 of my typec power-negotation hookup series. New this version: - Drop a few patches merged into linux-power-supply.git/for-next - Drop the "power: supply: bq24190_charger: Remove extcon handling" patch *for now*, this can only be merged once all the other patches are in

[PATCH v3 01/11] i2c: Allow overriding dev_name through board_info

For devices not instantiated through ACPI the i2c-client's device-name gets set to - by default, e.g. "0-0022" this means that the device-name is dependent on the order in which the i2c-busses are enumerated. In some cases having a predictable constant device-name is desirable, for example on non

[PATCH v3 02/11] staging: typec: tcpm: Add get_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 in this case, through e.g. BC1.2 detection. This commit adds an optional get_current_limit

[PATCH v3 04/11] 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 for now. We may want to revisit this and replace these with properties which are part of a (to be written) generic type-c

[PATCH v3 03/11] 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. Cc: "Yueyao (Nathan) Zhu"

[PATCH v3 10/11] i2c-cht-wc: Add device-properties for fusb302 integration

Add device-properties to make the bq24292i charger 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, as well as regulator_init_data for the 5V boost converter on the bq24292i. Since this means we now hook-up the

[PATCH v3 08/11] power: supply: bq24190_charger: Export 5V boost converter as regulator

Register the 5V boost converter as a regulator named "usb_otg_vbus". This commit also adds support for bq24190_platform_data, through which non device-tree platforms can pass the regulator_init_data (containing mappings for the consumer amongst other things). Signed-off-by: Hans de Goede

[PATCH v3 05/11] 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. Cc: "Yueyao (Nathan) Zhu" Signed-off-by: Hans de Goede --- drivers/staging/typec/fusb302/fusb302.c | 10 +++--- 1 file

[PATCH v3 09/11] 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 v3 06/11] 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. Rather

[PATCH v3 07/11] staging: typec: fusb302: Export current-limit through a power_supply class dev

The fusb302 Type-C port-controller cannot control the current-limit directly, so we need to exported the limit so that another driver (e.g. the charger driver) can pick the limit up and configure the system accordingly. The power-supply subsys already provides infrastructure for this,

Re: [PATCH v2] staging: ks7010: Fix coding style and remove checkpatch.pl warnings.

On Tue, Aug 29, 2017 at 08:57:34PM -0600, Jonathan Whitaker wrote: > It is prefered to use '"%s...", __func__ instead of function names for > logging. This commit replaces hardcoded function name strings to the > more preferred '"%s...", __func__' style. These warnings were reported > by

[PATCH 3/4] staging: fsl-mc: dpio: add order preservation support

From: Radu Alexe Order preservation is a feature that will be supported in dpni, dpseci and dpci devices. This is a preliminary patch for the changes to be introduced in the corresponding drivers. Signed-off-by: Radu Alexe Signed-off-by: Horia Geantă

Re: [PATCH v3 1/6] android: binder: Refactor prev and next buffer into a helper function

On Tue, Aug 29, 2017 at 11:07 PM, Greg Kroah-Hartman wrote: > On Tue, Aug 29, 2017 at 05:46:57PM -0700, Sherry Yang wrote: >> Use helper functions buffer_next and buffer_prev instead >> of list_entry to get the next and previous buffers. >> >> Signed-off-by: Sherry

Re: [PATCH v3 3/6] android: binder: Move buffer out of area shared with user space

On Wed, Aug 30, 2017 at 2:29 AM, Dan Carpenter wrote: > On Tue, Aug 29, 2017 at 05:46:59PM -0700, Sherry Yang wrote: >> Binder driver allocates buffer meta data in a region that is mapped >> in user space. These meta data contain pointers in the kernel. >> >> This patch

Re: [PATCH v3 1/6] android: binder: Refactor prev and next buffer into a helper function

On Wed, Aug 30, 2017 at 12:46:38PM -0700, Sherry Yang wrote: > I used --compose and put what changed from v2 to v3 in the > introductory message [patch 0/6]. Hm... I never got [patch 0/6] (I'm on de...@driverdev.osuosl.org). regards, dan carpenter

Re: [PATCH v3 3/6] android: binder: Move buffer out of area shared with user space

On Wed, Aug 30, 2017 at 01:04:31PM -0700, Arve Hjønnevåg wrote: > On Wed, Aug 30, 2017 at 2:29 AM, Dan Carpenter > wrote: > > On Tue, Aug 29, 2017 at 05:46:59PM -0700, Sherry Yang wrote: > >> Binder driver allocates buffer meta data in a region that is mapped > >> in

[PATCH 0/2] staging: r8822be: Remove some left-over debug code

Some useless debugging code from the initial writing of the driver was not removed before it was submitted. That oversight is now fixed and the remaining code in routine deinit_priv() is simplified. Larry Larry Finger (2): staging: r8822be: Remove some dead code staging: r8822be: Simplify

[PATCH 1/2] staging: r8822be: Remove some dead code

The code found inside an #ifdef CONFIG_RTL_DEBUG ... #endif section is left over from debugging of the original driver, and should be deleted. Reported by: Andreas Ziegler Signed-off-by: Larry Finger Cc: Ping-Ke Shih Cc:

[PATCH 2/2] staging: r8822be: Simplify deinit_priv()

Now that the extraneous debugging code is removed, routine deinit_priv() clearly contains code that serves no useful purpose. A null test before a call to kfree() and a spurious cast are also removed. Signed-off-by: Larry Finger Cc: Ping-Ke Shih

Re: [PATCH 13/14] vme: tsi148: Improve 17 size determinations

On 26 August 2017 at 08:00, SF Markus Elfring wrote: >>> @@ -2363,5 +2364,5 @@ static int tsi148_probe(struct pci_dev *pdev, const >>> struct pci_device_id *id) >>> master_num--; >>> >>> tsi148_device->flush_image = >>> -

Re: [PATCH v3 3/6] android: binder: Move buffer out of area shared with user space

I just went back through it -- turns out my email bounced back from linux-ker...@vger.kernel.org (reason was "may contain a virus"). Sorry I didn't notice that and resend. On Wed, Aug 30, 2017 at 1:20 PM, Dan Carpenter wrote: > On Wed, Aug 30, 2017 at 01:04:31PM -0700,

Re: [PATCH v3 net-next] staging: irda: fix init level for irda core

From: Greg KH Date: Wed, 30 Aug 2017 13:16:49 +0200 > When moving the IRDA code out of net/ into drivers/staging/irda/net, the > link order changes when IRDA is built into the kernel. That causes a > kernel crash at boot time as netfilter isn't initialized yet. > >

Re: [PATCH 13/14] vme: tsi148: Improve 17 size determinations

@@ -2363,5 +2364,5 @@ static int tsi148_probe(struct pci_dev *pdev, const struct pci_device_id *id) master_num--; tsi148_device->flush_image = -kmalloc(sizeof(struct vme_master_resource), GFP_KERNEL); +

[PATCH] staging: goldfish: (Coding Style) Fixed parenthesis alignment.

From: Edvard Holst Fixed paranthesis alignment for compliance with checkpatch. Signed-off-by: Edvard Holst --- drivers/staging/goldfish/goldfish_nand.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

Re: [PATCH 2/2] mmc: Add mmc_force_detect_change_begin / _end functions

On 30 August 2017 at 14:44, Hans de Goede wrote: > Hi, > > > On 21-07-17 16:35, Quentin Schulz wrote: >> >> From: Hans de Goede >> >> Some sdio devices have a multiple stage bring-up process. Specifically >> the esp8089 (for which an out of tree driver

Re: [PATCH v3 05/11] staging: typec: fusb302: Use client->irq as irq if set

On 08/30/2017 02:48 AM, Hans de Goede wrote: 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. Cc: "Yueyao (Nathan) Zhu" Signed-off-by: Hans de Goede Reviewed-by: Guenter

Re: [PATCH v3 06/11] staging: typec: fusb302: Add support for USB2 charger detection through extcon

On 08/30/2017 02:48 AM, Hans de Goede wrote: 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

Re: [PATCH v3 04/11] staging: typec: fusb302: Get max snk mv/ma/mw from device-properties

On 08/30/2017 02:48 AM, Hans de Goede wrote: 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 for now. We may want to revisit this and replace these with properties which are

Re: [PATCH v1 6/6] device property: Switch to use new generic UUID API

On Wednesday, August 30, 2017 2:41:41 PM CEST Christoph Hellwig wrote: > On Wed, Jul 26, 2017 at 02:27:44AM +0200, Rafael J. Wysocki wrote: > > > >> > Cc: "Rafael J. Wysocki" > > > >> > Cc: Mika Westerberg > > > >> > > > >> Acked-by: Mika

Re: [PATCH v1 6/6] device property: Switch to use new generic UUID API

On Wed, Aug 30, 2017 at 03:46:34PM +0200, Rafael J. Wysocki wrote: > 3689d3d69072 ACPI: device property: Switch to use new generic UUID API > > in my linux-next branch. Isn't it this one? Yes, that should be it. Somehow my linux-next tree seems to be a mess through or my git log skills aren't

Re: [PATCH v3 07/11] staging: typec: fusb302: Export current-limit through a power_supply class dev

On 08/30/2017 02:48 AM, Hans de Goede wrote: The fusb302 Type-C port-controller cannot control the current-limit directly, so we need to exported the limit so that another driver (e.g. the charger driver) can pick the limit up and configure the system accordingly. The power-supply subsys

Re: [PATCH v3 03/11] staging: typec: fusb302: Set max supply voltage to 5V

On 08/30/2017 02:48 AM, Hans de Goede wrote: 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

[PATCH] staging:rtl8188eu:core Fix Code Indent

This patch solves the code indentation issue inside the if block Signed-off-by: Janani Sankara Babu --- drivers/staging/rtl8188eu/core/rtw_cmd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/rtl8188eu/core/rtw_cmd.c

Re: [PATCH v1 3/6] staging: unisys: Switch to use new generic UUID API

On Mon, Jul 31, 2017 at 08:20:25PM +0300, Andy Shevchenko wrote: > Yep! There are so many conflicts that would be better just to push > through your tree. > > I have just sent a v2 of this patch separately. Greg, did you pick that patch up? ___ devel

Re: [PATCH v1 6/6] device property: Switch to use new generic UUID API

On Wed, Jul 26, 2017 at 02:27:44AM +0200, Rafael J. Wysocki wrote: > > >> > Cc: "Rafael J. Wysocki" > > >> > Cc: Mika Westerberg > > >> > > >> Acked-by: Mika Westerberg > > > > > > OK > > > > > > Andy, do you

Re: [PATCH v1 1/6] efi: Switch to use new generic UUID API

Thanks, applied to the uuid for-next tree. ___ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

Re: [PATCH v1 3/6] staging: unisys: Switch to use new generic UUID API

On Wed, 2017-08-30 at 14:38 +0200, Christoph Hellwig wrote: > On Mon, Jul 31, 2017 at 08:20:25PM +0300, Andy Shevchenko wrote: > > Yep! There are so many conflicts that would be better just to push > > through your tree. > > > > I have just sent a v2 of this patch separately. > > Greg, did you

[PATCH v3 net-next] staging: irda: fix init level for irda core

When moving the IRDA code out of net/ into drivers/staging/irda/net, the link order changes when IRDA is built into the kernel. That causes a kernel crash at boot time as netfilter isn't initialized yet. To fix this, move the init call level of the irda core to be device_initcall() as the link

Re: [PATCH 2/2] mmc: Add mmc_force_detect_change_begin / _end functions

Hi, On 21-07-17 16:35, Quentin Schulz wrote: From: Hans de Goede Some sdio devices have a multiple stage bring-up process. Specifically the esp8089 (for which an out of tree driver is available) loads firmware on the first call to its sdio-drivers' probe function and then

[PATCH][staging-next] staging: pi433: fix spelling mistake: "preample" -> "preamble"

From: Colin Ian King Trivial fix to spelling mistake in dev_dbg message Signed-off-by: Colin Ian King --- drivers/staging/pi433/rf69.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/pi433/rf69.c

Re: [PATCH v1 3/6] staging: unisys: Switch to use new generic UUID API

On Wed, Aug 30, 2017 at 02:38:45PM +0200, Christoph Hellwig wrote: > On Mon, Jul 31, 2017 at 08:20:25PM +0300, Andy Shevchenko wrote: > > Yep! There are so many conflicts that would be better just to push > > through your tree. > > > > I have just sent a v2 of this patch separately. > > Greg,

Re: [PATCH v3 08/11] power: supply: bq24190_charger: Export 5V boost converter as regulator

* Hans de Goede [170830 02:49]: > Register the 5V boost converter as a regulator named "usb_otg_vbus". > > This commit also adds support for bq24190_platform_data, through which > non device-tree platforms can pass the regulator_init_data (containing > mappings for the

Re: [PATCH v3 09/11] power: supply: bq24190_charger: Get input_current_limit from our supplier

* Hans de Goede [170830 02:49]: > 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

Re: [PATCH] storvsc: fix memory leak on ring buffer busy

On Tue, 29 Aug 2017 21:31:11 -0400 "Martin K. Petersen" wrote: > Long, > > > When storvsc is sending I/O to Hyper-v, it may allocate a bigger > > buffer descriptor for large data payload that can't fit into a > > pre-allocated buffer descriptor. This bigger buffer is

RE: [PATCH] storvsc: fix memory leak on ring buffer busy

> Long, > > >> Which kernel version is this patch aimed at? > > > > Martin, thanks for pointing this out. This should also go to stable > > trees. > > The reason I asked is that it didn't apply to neither fixes, nor for-next. > > I applied it to 4.13/scsi-fixes by hand and added a stable tag.

Re: [PATCH v3 1/6] android: binder: Refactor prev and next buffer into a helper function

On Wed, Aug 30, 2017 at 12:46:38PM -0700, Sherry Yang wrote: > On Tue, Aug 29, 2017 at 11:07 PM, Greg Kroah-Hartman > wrote: > > On Tue, Aug 29, 2017 at 05:46:57PM -0700, Sherry Yang wrote: > >> Use helper functions buffer_next and buffer_prev instead > >> of

Re: [PATCH 0/4] irda: move it to drivers/staging so we can delete it

On Tue, Aug 29, 2017 at 11:32:58PM +0200, Ondrej Zary wrote: > On Tuesday 29 August 2017 01:42:08 David Miller wrote: > > From: Greg Kroah-Hartman > > Date: Sun, 27 Aug 2017 17:03:30 +0200 > > > > > The IRDA code has long been obsolete and broken. So, to keep people >

Re: [PATCH] storvsc: fix memory leak on ring buffer busy

Long, >> Which kernel version is this patch aimed at? > > Martin, thanks for pointing this out. This should also go to stable > trees. The reason I asked is that it didn't apply to neither fixes, nor for-next. I applied it to 4.13/scsi-fixes by hand and added a stable tag. -- Martin K.

[PATCH v3] staging: ks7010: Fix coding style and remove checkpatch.pl warnings.

Removed printk statements for debugging. The same information can be acquired via ftrace, so these print statements are uneccessary. Signed-off-by: Jonathan Whitaker --- Changes in v2: - Wrapped the changelog text to 72 columns. - Fixed the commit subject to be