Re: [PATCH 030/124] staging: lustre: llite: Replace write mutex with range lock

On Sun, Sep 18, 2016 at 04:37:29PM -0400, James Simmons wrote: > + * Range lock is used to allow multiple threads writing a single shared > + * file given each thread is writing to a non-overlapping portion of the > + * file. > + * > + * Refer to the possible upstream kernel version of range lock b

Re: [PATCH 070/124] staging: lustre: statahead: small fixes and cleanup

On Sun, Sep 18, 2016 at 04:38:09PM -0400, James Simmons wrote: > From: Lai Siyao > > small fixes: > * when 'unplug' is set for ll_statahead(), sa_put() shouldn't kill >the entry found, because its inflight RPC may not finish yet. > * remove 'sai_generation', add 'lli_sa_generation' because

Re: [PATCH 000/124] missing patches from Lustre 2.7 release

On Sun, Sep 18, 2016 at 04:36:59PM -0400, James Simmons wrote: > This batch of patches includes various cleanups and fixes from > the Lustre 2.7 release. Most of these patches are removal of > cruft and unsigned to signed comparsion fixes. Also added in > the latest LNet fixes as well. All now que

Re: [lustre-devel] [PATCH 030/124] staging: lustre: llite: Replace write mutex with range lock

On Sep 19, 2016, at 09:28, Greg Kroah-Hartman wrote: > > On Sun, Sep 18, 2016 at 04:37:29PM -0400, James Simmons wrote: >> + * Range lock is used to allow multiple threads writing a single shared >> + * file given each thread is writing to a non-overlapping portion of the >> + * file. >> + * >>

Re: [lustre-devel] [PATCH 030/124] staging: lustre: llite: Replace write mutex with range lock

On Mon 19-09-16 09:25:48, Dilger, Andreas wrote: > On Sep 19, 2016, at 09:28, Greg Kroah-Hartman > wrote: > > > > On Sun, Sep 18, 2016 at 04:37:29PM -0400, James Simmons wrote: > >> + * Range lock is used to allow multiple threads writing a single shared > >> + * file given each thread is writin

Re: Good to finally reach you

Hello How are you? i hope all is well with you. I have tried reachiny you without luck. My client is looking for a good business to invest in your country. If you have any good business in mind please get back to me urgently so i can give you more update. We are looking at Real Estate, Spa & fit

Re: Good to finally reach you

Hello How are you? i hope all is well with you. I have tried reachiny you without luck. My client is looking for a good business to invest in your country. If you have any good business in mind please get back to me urgently so i can give you more update. We are looking at Real Estate, Spa & fit

HELLO

Hello How are you? i hope all is well with you. I have tried reachiny you without luck. My client is looking for a good business to invest in your country. If you have any good business in mind please get back to me urgently so i can give you more update. We are looking at Real Estate, Spa & fit

[PATCH] staging: rtl8192u: r8192U_core: fix checkpatch permission warnings

Fix the following warnings: Symbolic permissions are not preferred. Consider using octal permissions. Signed-off-by: Xavier Roumegue --- drivers/staging/rtl8192u/r8192U_core.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/staging/rtl8192u/r8192U_core.c b/driv

Re: [PATCH v2] stagging:iio:ad9834: add devicetree property support

On 09/18/2016 10:52 AM, Gwenhael Goavec-Merou wrote: [...] > +#if defined(CONFIG_OF) > +static struct ad9834_platform_data *ad9834_parse_dt(struct spi_device *spi) > +{ > + struct ad9834_platform_data *pdata; > + struct device_node *np = spi->dev.of_node; > + > + pdata = devm_kzalloc(&s

[PATCH 0/4] staging: most: fix issues of hdm-usb

This patch set is needed to fix issues of the HDM USB module of the MOST driver. Christian Gromm (4): staging: most: hdm-usb: remove proprietary urb anchoring staging: most: hdm-usb: remove redundant spinlocks staging: most: hdm-usb: remove calls to usb_unachor_urb staging: most: hdm-usb:

[PATCH 3/4] staging: most: hdm-usb: remove calls to usb_unachor_urb

This patch removes the calls to usb_unanchor_urb() from the completion routines, since disassociation of the URBs is already handles by the USB subsystem. Signed-off-by: Christian Gromm --- drivers/staging/most/hdm-usb/hdm_usb.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/stagin

[PATCH 1/4] staging: most: hdm-usb: remove proprietary urb anchoring

This patch removes the propietary tracking of URBs. Instead the structure usb_anchor of the USB subsystem is used. Signed-off-by: Christian Gromm --- drivers/staging/most/hdm-usb/hdm_usb.c | 75 ++ 1 file changed, 21 insertions(+), 54 deletions(-) diff --git a/dr

[PATCH 4/4] staging: most: hdm-usb: rename channel related spinlock

To increase comprehension this patch renames the channel related spinlock with a more fitting name. Signed-off-by: Christian Gromm --- drivers/staging/most/hdm-usb/hdm_usb.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/drivers/staging/most/hdm-usb/hdm_usb.c b

[PATCH 2/4] staging: most: hdm-usb: remove redundant spinlocks

This patch removes the spinlocks when accessing the usb_anchor list, because the struct usb_anchor is using its own lock. Signed-off-by: Christian Gromm --- drivers/staging/most/hdm-usb/hdm_usb.c | 13 - 1 file changed, 13 deletions(-) diff --git a/drivers/staging/most/hdm-usb/hdm_u

[PATCH V2] rtl8xxxu: Stop log spam from each successful interrupt

As soon as debugging is turned on, the logs are filled with messages reporting the interrupt status. As this quantity is usually zero, this output is not needed. In fact, there will be a report if the status is not zero, thus the debug line in question could probably be deleted. Rather than taking

Re: [RFC 3/3] phy,leds: add support for led triggers on phy link state change

On Wed, Sep 14, 2016 at 04:16:15PM -0700, Florian Fainelli wrote: > On 09/14/2016 02:55 PM, Zach Brown wrote: > > From: Josh Cartwright > > > > Create an option CONFIG_LED_TRIGGER_PHY (default n), which will > > create a set of led triggers for each instantiated PHY device. There is > > one LED

[PATCH] staging: lustre: ptlrpc: re-export lustre_swab_[lmv|lov]_mds_md

Being over zealous in removing unused EXPORT_SYMBOLs two functions lustre_swab_[lmv|lov]_mds_md exports were removed. They need to be exported so this patch restores those EXPORT_SYMBOLS. Same mistake was done when porting to the upstream client. Signed-off-by: James Simmons Reviewed-on: http://r

RE: [PATCH] hv: do not lose pending heartbeat vmbus packets

> -Original Message- > From: Long Li [mailto:lon...@exchange.microsoft.com] > Sent: Monday, September 12, 2016 11:31 PM > To: KY Srinivasan ; Haiyang Zhang > > Cc: de...@linuxdriverproject.org; linux-ker...@vger.kernel.org; Long Li > > Subject: [PATCH] hv: do not lose pending heartbeat vm

[staging:greybus-test 1/22] drivers/staging/greybus/bootrom.c:298:35-39: ERROR: fw is NULL but dereferenced.

tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git greybus-test head: 2bbadafbe4eacab57aa7bc8e50287c1366303807 commit: f44dd184634d401f5cf88a6d8b4a60d5ff4f417f [1/22] Merge greybus driver tree into 4.8-rc6 coccinelle warnings: (new ones prefixed by >>) >> drivers/stag

Re: [PATCH v2] staging: lustre: lustre/ldlm: Fixed sparse warnings

> Added __acquires / __releases sparse locking annotations > to lock_res_and_lock() and unlock_res_and_lock() functions > in l_lock.c, to fix below sparse warnings: > > l_lock.c:47:22: warning: context imbalance in 'lock_res_and_lock' - wrong > count at exit > l_lock.c:61:6: warning: context imb

[PATCH 00/22] staging: unisys: visorbus: Remove prototypes and other cleanups

This patchset removes unused crud from the visorbus driver, which includes shuffling a lot of code around so function prototypes could be deleted. David Kershner (18): staging: unisys: visorbus: reorder controlvm_periodic_work staging: unisys: visorbus: move handle_command staging: unisys: v

[PATCH 02/22] staging: unisys: visorbus: remove unused long long bus_count

From: Jon Frisch This patch removes the unused long long bus_count. Signed-off-by: Jon Frisch Signed-off-by: David Kershner --- drivers/staging/unisys/visorbus/visorbus_main.c | 5 - 1 file changed, 5 deletions(-) diff --git a/drivers/staging/unisys/visorbus/visorbus_main.c b/drivers/st

[PATCH 03/22] staging: unisys: visorbus: remove unused dump_vhba_bus

From: Jon Frisch This patch removes the unused u32 dump_vhba_bus. Signed-off-by: Jon Frisch Signed-off-by: David Kershner Reported-by: Greg Kroah-Hartman --- drivers/staging/unisys/visorbus/visorchipset.c | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/drivers/staging

[PATCH 08/22] staging: unisys: visorbus: move read_controlvm_event

The function read_controlvm_event needs to be moved lower in the file to avoid extraneous function prototypes. Reported-by: Greg Kroah-Hartman Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/visorbus/visorchipset.c | 42 +- 1 file changed,

[PATCH 06/22] staging: unisys: visorbus: move handle_command

Handle_command gets moved lower in the file to avoid the need for extraneous function prototypes. Reported-by: Greg Kroah-Hartman Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/visorbus/visorchipset.c | 230 - 1 file changed, 115 insertio

[PATCH 04/22] staging: unisys: visorbus: move controlvm_payload_bytes_buffered

From: Jon Frisch This patch moves the unsigned long controlvm_payload_bytes_buffered from the module parameters location to a more appropriate location below the controlvm_payload_info. Signed-off-by: Jon Frisch Signed-off-by: David Kershner Reported-by: Greg Kroah-Hartman --- drivers/stagin

[PATCH 01/22] staging: unisys: visorbus remove unused module parameter

From: Jon Frisch This patch removes the unused module parameter visorchipset_visorbusregwait Signed-off-by: Jon Frisch Signed-off-by: David Kershner Reported-by: Greg Kroah-Hartman --- drivers/staging/unisys/visorbus/visorchipset.c | 4 1 file changed, 4 deletions(-) diff --git a/drive

[PATCH 05/22] staging: unisys: visorbus: reorder controlvm_periodic_work

Move controlvm_periodic_work lower in the file to avoid having to create function prototypes. Reported-by: Greg Kroah-Hartman Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/visorbus/visorchipset.c | 134 - 1 file changed, 67 insertions(+)

[PATCH 20/22] staging: unisys: visorbus move visorbus_type to remove prototypes

Move the struct visorbus_type down in the file to get rid of the function prototypes visorbus_uevent and visorbus_match. Reported-by: Greg Kroah-Hartman Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/visorbus/visorbus_main.c | 26 - 1 fil

[PATCH 11/22] staging: unisys: visorbus: remove controlvm_respond_chipset_init prototype

Remove the unneeded controlvm_respond_chipset_init prototype by moving the functions controlvm_init_response and controlvm_respond_chipset_init up in the file. Reported-by: Greg Kroah-Hartman Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/visorbus/visorchipset.c

[PATCH 14/22] staging: unisys: visorbus: move toolaction functions to remove prototypes

The toolchain functions show and store needed to be moved so the prototypes were no longer needed. Reported-by: Greg Kroah-Hartman Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/visorbus/visorchipset.c | 64 -- 1 file changed, 29 insertio

[PATCH 09/22] staging: unisys: visorbus: move parahotplug_process_list

The function parahotplug_process_list needs to be moved lower in the file to avoid extraneous function prototypes. Reported-by: Greg Kroah-Hartman Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/visorbus/visorchipset.c | 63 +- 1 file chan

[PATCH 15/22] staging: unisys: visorbus: move boottotool

Move the boottotool show and store functions so the function prototypes can be removed. Reported-by: Greg Kroah-Hartman Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/visorbus/visorchipset.c | 72 -- 1 file changed, 33 insertions(+), 39 d

[PATCH 16/22] staging: unisys: visorbus: move error store/show functions

Move the show and store functions for the error DEV_ATTR_RW so that the function prototypes can be removed. Reported-by: Greg Kroah-Hartman Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/visorbus/visorchipset.c | 61 -- 1 file changed, 28

[PATCH 10/22] staging: unisys: visorbus: remove prototype controlvm_respond

Remove the unneeded prototype for controlvm_respond. Reported-by: Greg Kroah-Hartman Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/visorbus/visorchipset.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/staging/unisys/visorbus/visorchipset.c b/dri

[PATCH 17/22] staging: unisys: visorbus: move textid store and show functions

The textid store and show functions were moved to allow us to remove the function prototypes. Reported-by: Greg Kroah-Hartman Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/visorbus/visorchipset.c | 63 -- 1 file changed, 29 insertions(+)

[PATCH 19/22] staging: unisys: visorbus: move deviceenabled/disabled store functions

Move the deviceenabled/devicedisabled store functions so that function prototypes can be removed. This caused us to move several of the structures farther down in the file as well. Reported-by: Greg Kroah-Hartman Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/v

[PATCH 18/22] staging: unisys: visorbus: move the remaining_steps_show/store functions

Moving the remaining_steps functions allows us to get rid of an unneeded prototype. Reported-by: Greg Kroah-Hartman Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/visorbus/visorchipset.c | 62 -- 1 file changed, 28 insertions(+), 34 delet

[PATCH 12/22] staging: unisys: visorbus: remove controlvm_respond_physdev_changestate

Remove the unneeded prototype declaration for function controlvm_respond_physdev_changestate. Reported-by: Greg Kroah-Hartman Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/visorbus/visorchipset.c | 4 1 file changed, 4 deletions(-) diff --git a/drivers/st

[PATCH 07/22] staging: unisys: visorbus: move parser_init_byte_stream

The function parser_init_byte_stream needs to be moved lower in the file to avoid extraneous function prototypes. Reported-by: Greg Kroah-Hartman Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/visorbus/visorchipset.c | 116 - 1 file chang

[PATCH 22/22] staging: unisys: visorbus: move parahotplug_request_list and related lock

parahotplug_request_list and parahotplug_request_list_lock should be defined closer to where we are actually using them. Reported-by: Greg Kroah-Hartman Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/visorbus/visorchipset.c | 6 +++--- 1 file changed, 3 insertio

[PATCH 21/22] staging: unisys: visorbus: remove fix_vbus_dev_info prototype

Move the visordriver_probe_device and visorbus_register_visor_driver functions lower in the file to get rid of the function prototype fix_vbus_dev_info. Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/visorbus/visorbus_main.c | 256 1 file

[PATCH 13/22] staging: unisys: visorbus: remove parser_done prototype

Remove the unneeded prototype parser_done. Reported-by: Greg Kroah-Hartman Signed-off-by: David Kershner Reviewed-by: Tim Sell --- drivers/staging/unisys/visorbus/visorchipset.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/drivers/staging/unisys/visorbus/visorchipset.c b/drivers/stag

Re: staging: vme_user: accept bus_num of zero

- Original Message - > From: "Martyn Welch" > Sent: Thursday, September 8, 2016 2:17:35 PM > On Fri, Sep 02, 2016 at 03:59:45PM -0500, Aaron Sierra wrote: >> The driver's bus_num parameter is used to select a VME bus during probe. >> This parameter is used both as a boolean to indicate th

[PATCH 1/3] staging: greybus: use preferred kernel type u8

As suggested by checkpatch.pl: CHECK: Prefer kernel type 'u8' over 'uint8_t' Signed-off-by: Chaehyun Lim --- drivers/staging/greybus/audio_codec.c | 6 +++--- drivers/staging/greybus/audio_codec.h | 18 +- drivers/staging/greybus/audio_gb.c| 16 3 files cha

[PATCH 3/3] staging: greybus: use preferred kernel type u32

As suggested by checkpatch.pl: CHECK: Prefer kernel type 'u32' over 'uint32_t' Signed-off-by: Chaehyun Lim --- drivers/staging/greybus/audio_codec.c | 6 ++-- drivers/staging/greybus/audio_codec.h | 10 +++ drivers/staging/greybus/audio_gb.c| 4 +-- drivers/sta

[PATCH 2/3] staging: greybus: use preferred kernel type u16

As suggested by checkpatch.pl: CHECK: Prefer kernel type 'u16' over 'uint16_t' Signed-off-by: Chaehyun Lim --- drivers/staging/greybus/audio_codec.c | 12 ++-- drivers/staging/greybus/audio_codec.h | 16 drivers/staging/greybus/audio_gb.c| 18 +- 3 f

Re: [PATCH 3/3] staging: greybus: use preferred kernel type u32

On Tue, Sep 20, 2016 at 09:47:31AM +0900, Chaehyun Lim wrote: > As suggested by checkpatch.pl: > > CHECK: Prefer kernel type 'u32' over 'uint32_t' > > Signed-off-by: Chaehyun Lim > --- > drivers/staging/greybus/audio_codec.c | 6 ++-- > drivers/staging/greybus/audio_codec.h | 1

Re: [PATCH 1/4] staging: most: hdm-usb: remove proprietary urb anchoring

On Mon, Sep 19, 2016 at 05:40:22PM +0200, Christian Gromm wrote: > This patch removes the propietary tracking of URBs. Instead the structure > usb_anchor of the USB subsystem is used. > > Signed-off-by: Christian Gromm Ah, nice job, glad to see these changes made. greg k-h _

Re: [PATCH] staging: lustre: ptlrpc: re-export lustre_swab_[lmv|lov]_mds_md

On Mon, Sep 19, 2016 at 01:27:05PM -0400, James Simmons wrote: > Being over zealous in removing unused EXPORT_SYMBOLs two functions > lustre_swab_[lmv|lov]_mds_md exports were removed. They need to be > exported so this patch restores those EXPORT_SYMBOLS. Same mistake > was done when porting to th