This fixes up a line over 80 characters issues found by
the checkpatch.pl tool.
Signed-off-by: Ravishankar Karkala Mallikarjunayya
---
Change log v1->v2
- No Change
---
drivers/staging/comedi/drivers/s626.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/sta
This fixes up a WARNING: Prefer 'unsigned int' to bare use of 'unsigned'
found by the checkpatch.pl tool
Signed-off-by: Ravishankar Karkala Mallikarjunayya
---
Change log v1->v2
- No Change
---
drivers/staging/comedi/drivers/s626.c | 8
1 file changed, 4 insertions(+), 4 deletio
This fixes up a type issues like
i.e Prefer kernel type 'u8' over 'uint8_t'
Prefer kernel type 'u16' over 'uint16_t'
Prefer kernel type 'u32' over 'uint32_t'
Prefer kernel type 's16' over 'int16_t'
Prefer kernel type 's32' over 'int32_t'
found by the checkpatch.pl tool.
Signed-off-
Current task selecting logic in LMK does not fully aware of the memory
pressure. It may select the task with maximum score adj, but with
least tasksize.
For example, if min_score_adj is 200, and there are 2 tasks in system:
task a: score adj 500, tasksize 200M
task b: score adj 1000, tasksiz
lowmem_count() should only count anon pages when we have swap device.
Signed-off-by: Ganesh Mahendran
---
drivers/staging/android/lowmemorykiller.c | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/android/lowmemorykiller.c
b/drivers/staging/androi
om_adj is deprecated, and in lowmemorykiller module, we use score adj
to do the comparing.
---
oom_score_adj = p->signal->oom_score_adj;
if (oom_score_adj < min_score_adj) {
task_unlock(p);
continue;
}
-
On Mon, 2016-06-20 at 12:53 -0300, Gustavo Padovan wrote:
> From: Gustavo Padovan
>
> Fix paths in the comments.
Why is it useful to have the path or filename embedded
in the file at
all?
___
devel mailing list
de...@linuxdriverproject.org
http://driv
Attn: Lucky Winner,
FINAL AWARD
NOTIFICATIONS!!!
This is to inform you on the release of the EUROMILLONES LOTTERY PROGRAM held
on the 16th of June 2016. Due to mix up of some nu
2016-06-16 18:23 GMT+09:00 DaeSeok Youn :
> 2016-05-10 15:44 GMT+09:00 Daeseok Youn :
>> The dgnc_block_til_ready() is only used in dgnc_tty_open().
>> The unit data(struct un_t) was stored into tty->driver_data in
>> dgnc_tty_open().
>> And also tty and un were tested about NULL so these variable
The driver is only a working port of a badly written driver extracted from an
old and vendor-specified kernel source.
I cannot promise the code style (although I did indent -kr -i8).
I cannot also promise the effect.
20.06.2016, 23:43, "Greg KH" :
> On Sun, Jun 19, 2016 at 08:33:48PM +0800, Iceno
Split the function ll_getxattr_common into two functions.
The code used for listing xattrs and ll_getxattr_common is
placed into a new function ll_getxattr_list. This allows
ll_listxattr to call directly ll_getxattr_list instead of
going through ll_getxattr_common. This change is needed
for the upc
> -Original Message-
> From: Bharat Bhushan [mailto:bharat.bhus...@nxp.com]
> Sent: Thursday, June 16, 2016 1:52 AM
> To: gre...@linuxfoundation.org; Stuart Yoder
> Cc: de...@driverdev.osuosl.org; linux-ker...@vger.kernel.org; Bharat Bhushan
>
> Subject: [PATCH] fsl mc-bus: Move mc-io
commit ac5b14810952 ("staging: lustre: osc: Track and limit
"unstable" pages") added a new sysfs variable, but corresponding bit of
documentation was not forgotten.
Signed-off-by: Oleg Drokin
---
drivers/staging/lustre/sysfs-fs-lustre | 8
1 file changed, 8 insertions(+)
diff --git a/d
From: Oleg Drokin
There are a couple of cases in ll_revalidate_dentry() where
we are pretty sure the dentry is valid, so check for them early
and save more expensive checks for later.
Signed-off-by: Oleg Drokin
---
drivers/staging/lustre/lustre/llite/dcache.c | 11 +++
1 file changed,
From: "John L. Hammond"
Replace the union in struct lookup_intent with the members of struct
lustre_indent_data. Remove the then unused struct lustre_intent_data.
Signed-off-by: John L. Hammond
Reviewed-on: http://review.whamcloud.com/17069
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-74
kthread_run might sleep during an allocation, and so
it's considered unsafe to call with a state that's not
RUNNABLE.
Move the state setting to after kthread_run call.
Signed-off-by: Oleg Drokin
---
drivers/staging/lustre/lnet/libcfs/debug.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Andreas Dilger
Lockdep complains about potential recursive locking during mount
because the client configuration log is holding a lock on the MGC
obd_device to prevent it from being torn down, while also getting
mutexes on the MDC and OSC devices as they are instantiated:
Lustre: Mounted
From: Patrick Farrell
The lli_trunc_sem is taken in 'read' mode in both
ll_page_mkwrite and vvp_io_fault_start. This can lead to a
deadlock with another thread which asks for the semaphore
in write mode between thse two read calls.
Since all users of lli_trunc_sem are in the vvp layer, we
can sa
From: akam kumar bharathi
req_capsule_server_get() through __req_capsule_get in ll_dir_ioctl()
returns a pointer to a PTLRPC request or reply buffer, which is assigned
to struct mdt_body.
If the command is IOC_MDS_GETFILEINFO then the inode "st.st_ino" should
be assigned from one extracted from
From: Dmitry Eremin
Bit field 'oi_lockless' and 'oi_is_active' has one bit and is signed
which is confusing.
Signed-off-by: Dmitry Eremin
Reviewed-on: http://review.whamcloud.com/19196
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7258
Reviewed-by: Andreas Dilger
Reviewed-by: James Simmo
From: Niu Yawei
While atime on close is supposed to only increase, there's
a bug in some older server versions where atime from a client
is taken no matter the value that allows a stale client atime
to overwrite a correct value.
Update atime in close rpc to 0 to help such servers out.
Signed-of
From: "John L. Hammond"
Change the void *it_data member of struct lookup_intent to struct
ptlrpc_request *it_request.
Signed-off-by: John L. Hammond
Reviewed-on: http://review.whamcloud.com/17070
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7403
Reviewed-by: Andreas Dilger
Reviewed-by:
From: Oleg Drokin
Mark dentries that came to us via NFS in a special way so that
we can tell them apart during open and activate open cache
(we really don't want to do open/close RPC for every NFS IO).
This became needed since dentry revlidate no longer reimplements
any RPCs for lookup, and as s
From: Bob Glossman
LU_OBJECT_DEBUG expects non \n terminated message from the caller,
so it should add it's own to keep debug logger happy.
Signed-off-by: Bob Glossman
Reviewed-on: http://review.whamcloud.com/19960
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8094
Reviewed-by: Andreas Di
From: Andriy Skulysh
A deadlock is possible during ccc_prep_size()->ldlm_lock_match() vs
cl_io_lock() which is waiting for a matched lock and conflicts with
already taken lock before ccc_prep_size().
It is better to send an additional lock request to avoid deadlock.
Seagate-bug-id: MRP-3312
Sig
They are just one-liners, so no point in having them exported
and called through a different module.
Signed-off-by: Oleg Drokin
---
drivers/staging/lustre/lustre/include/lustre_intent.h | 15 +++
drivers/staging/lustre/lustre/include/lustre_mdc.h| 3 ---
drivers/staging/lustre/l
From: Yang Sheng
The watched obd device may still not setup while onu_upcall
invoked. So we need verify it in cl_ocd_update.
Signed-off-by: Yang Sheng
Reviewed-on: http://review.whamcloud.com/19597
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8027
Reviewed-by: Niu Yawei
Reviewed-by: Lai
From: Sergey Cheremencev
LASSERT should never be done on data that is
received to over the network. Return EINVAL
when server returns invalid fid despite of
it_status == 0.
Signed-off-by: Sergey Cheremencev
Seagate-bug-id: MRP-3073
Reviewed-on: http://review.whamcloud.com/17985
Intel-bug-id: ht
From: "John L. Hammond"
Add a const qualifier to several struct lustre_handle * parameters in
the LDLM interface.
Signed-off-by: John L. Hammond
Reviewed-on: http://review.whamcloud.com/17071
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7403
Reviewed-by: Andreas Dilger
Reviewed-by: Jame
From: Alex Zhuravlev
as it adds own \n, so any extra \n break log format.
Signed-off-by: Alex Zhuravlev
Reviewed-on: http://review.whamcloud.com/17494
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7521
Reviewed-by: James Simmons
Reviewed-by: John L. Hammond
Reviewed-by: Andreas Dilger
From: Liang Zhen
This patch changes a few things:
- There is no guarantee that request_out_callback will happen
before reply_in_callback, if a request got reply and unlinked
reply buffer before request_out_callback is called, then the
thread waiting on ptlrpc_request_set will miss wakeup e
From: Vitaly Fertman
The reverse order of request_out_callback() and reply_in_callback()
puts the RPC into UNREGISTERING state, which is waiting for RPC &
bulk md unlink, whereas only RPC md unlink has been called so far.
If bulk is lost, even expired_set does not check for UNREGISTERING
state.
From: Ben Evans
Combine __ptlrpc_request_bufs_pack into ptlrpc_request_bufs_pack
because it was an unnecessary wrapper otherwise.
Signed-off-by: Ben Evans
Reviewed-on: http://review.whamcloud.com/16765
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7269
Reviewed-by: Frank Zago
Reviewed-by
From: Vitaly Fertman
A race between unregister_reply & early reply.
When buffers are busy for the early transfer, they cannon be unlinked
by unregister_reply, so the RPC gets into UNREGISTERING state. The
coming reply_in_callback for the early RPC already has unlinked flag
set due to previous mdu
From: Emoly Liu
Since the inflight request holds import refcount as well as export,
sometimes obd_disconnect() in client_common_put_super() can't put
the last refcount of OSC import (e.g. due to network disconnection),
this will cause cl_cache being accessed after free.
To fix this issue, ccc_us
From: Liang Zhen
ptlrpc_request has some structure members are only for client side,
and some others are only for server side, this patch moved these
members to different structure then putting into an union.
By doing this, size of ptlrpc_request is decreased about 300 bytes,
besides saving memo
Changes from v1:
This is rebased and retested on top of latest staging tree,
one patch dropped because it made it to the tree by other means,
two more fixes added.
These patches represent another round of Lustre fixes
and also a few cleanups that some of the fixes were
building up upon.
Alex Zhur
From: Bruno Faccini
There has been several Lustre Client crashes reported by sites
running with Lustre versions 2.1/2.5, all showing the same
dentry->d_hash->next corrupted pointer cause.
This patch fixes a regression that has been introduced since a
long time by commit :
(LU-506 kernel: FC15 -
These are just doing spin_lock/unlock on inode's i_lock,
so just do the spinlock directly to make the code more clear
Signed-off-by: Oleg Drokin
---
drivers/staging/lustre/lustre/llite/dcache.c | 4 ++--
drivers/staging/lustre/lustre/llite/llite_internal.h | 10 --
drivers/stagi
From: "John L. Hammond"
In the FIFO cases of ll_atomic_open() and ll_lookup_nd() remove
spurious calls to ptlrpc_req_finished(). Explain that these cases are
unreachable in practice anyway.
Signed-off-by: John L. Hammond
Reviewed-on: http://review.whamcloud.com/17068
Intel-bug-id: https://jira.
From: Jinshan Xiong
With huge number of pages to scan by osc_lock_weight() it is likely
CLP_GANG_RESCHED is returned from osc_page_gang_lookup() and the scan
will be repeated again from the start. To be sure that the scan is
progressing across those restarts, next scan should be started from
the
When imprting clio simplification patch, the check for
pbject got reversed by mistake when converting from
if (obj == NULL) it somehow became (if (obj) which is obviously wrong,
and so when it does hit, a crash was happening as result.
Fix the condition and all if fine now.
Signed-off-by: Oleg Dr
Fix the checkpatch.pl issues:
WARNING: Block comments use * on subsequent lines
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers/ni_pcimio.c | 216 ++---
1 file changed, 106 insertions(+), 110 deletions(-)
diff -
Fix the checkpatch.pl issues:
WARNING: Block comments use * on subsequent lines
WARNING: Block comments use a trailing */ on a separate line
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers/ni_at_a2150.c | 103 ---
Fix the checkpatch.pl issues:
WARNING: Block comments use * on subsequent lines
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers/ni_atmio.c | 165 ++
1 file changed, 78 insertions(+), 87 deletions(-)
diff --g
Fix the checkpatch.pl issues:
WARNING: Block comments use * on subsequent lines
Move the configuration options comment into the comedi driver comment
block. That's were they typically are listed.
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi
Fix the checkpatch.pl issues:
WARNING: Block comments use * on subsequent lines
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers/ni_daq_dio24.c | 58 +--
1 file changed, 29 insertions(+), 29 deletions(-)
diff --g
Fix the checkpatch.pl issues:
WARNING: Block comments use * on subsequent lines
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers/ni_670x.c | 62 +++-
1 file changed, 28 insertions(+), 34 deletions(-)
diff --g
Fix the checkpatch.pl issues:
WARNING: Block comments use * on subsequent lines
WARNING: Block comments use a trailing */ on a separate line
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers/ni_pcidio.c | 95 +++---
Fix the checkpatch.pl issue:
WARNING: Block comments use * on subsequent lines
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers/das08_cs.c | 73 +++
1 file changed, 36 insertions(+), 37 deletions(-)
diff --gi
Fix the checkpatch.pl issues:
WARNING: Block comments use * on subsequent lines
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers/ni_mio_cs.c | 67 +++---
1 file changed, 33 insertions(+), 34 deletions(-)
diff --g
Fix the checkpatch.pl issues with the comment blocks that are used to
automatically generate documentation in Comedi and Comedilib.
H Hartley Sweeten (9):
staging: comedi: das08_cs: fix block comments
staging: comedi: ni_670x: fix block comment issues
staging: comedi: ni_pcimio: fix block co
This comment block is used to automatically generate documentation in
Comedi and Comedilib.
Signed-off-by: H Hartley Sweeten
Cc: Ian Abbott
Cc: Greg Kroah-Hartman
---
drivers/staging/comedi/drivers/addi_apci_3501.c | 27 +
1 file changed, 27 insertions(+)
diff --git a/
This driver is for a simple 4/8 channel analog output board with 2 isolated
digital inputs and 2 isolated digital outputs. Support for these subdevices
is provided by the driver.
The boards also has a watchdog timer that can be used to reset the analog
outputs. It can also be used as a general pur
The timer/counter subdevice in this driver is broken and it really
doesn't add much use if it did work.
Remove the timer/counter support and add the missing comedi driver
comment block.
H Hartley Sweeten (2):
staging: comedi: addi_apci_3501: remove timer/counter subdevice support
staging: com
On Friday, June 17, 2016 9:02 PM, Greg KH wrote:
>> The patch looks fine (although this odd-ball Comedi driver shouldn't really
>> be sending signals to a user-space task!).
>
> Yeah, that's really odd, fixing that would be nice...
This is the last addi-data driver that does this. It's on my list
2016-06-20 Joe Perches :
> On Mon, 2016-06-20 at 12:53 -0300, Gustavo Padovan wrote:
> > From: Gustavo Padovan
> >
> > Fix paths in the comments.
>
> Why is it useful to have the path or filename embedded
> in the file at
> all?
I just kept it as is. Thinking about this now I don't see
this as
From: Gustavo Padovan
Sync Framework was de-staged to drivers/dma-buf/, so remove it entries
in the TODO file.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/TODO | 8
1 file changed, 8 deletions(-)
diff --git a/drivers/staging/android/TODO b/drivers/staging/android/TODO
From: Gustavo Padovan
Fix paths in the comments.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sync_debug.c | 2 +-
drivers/staging/android/sync_debug.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/android/sync_debug.c
b/drivers/staging/a
From: Gustavo Padovan
Hi Greg,
This is the last step in the Sync Framwork de-stage task. It de-stage
the SW_SYNC validation framework and the sync_debug info debugfs file.
The first 3 patches are clean up and improvements and the rest is preparation
to de-stage and then finally the actual de-st
From: Gustavo Padovan
SW_SYNC allows to run tests on the sync_file framework via debugfs on
/sync/sw_sync
Opening and closing the file triggers creation and release of a sync
timeline. To create fences on this timeline the SW_SYNC_IOC_CREATE_FENCE
ioctl should be used. To increment the timeline
From: Gustavo Padovan
SW_SYNC should never be used by other pieces of the kernel apart from
sync_debug as it is only a Sync File Validation Framework, so hide any
info to avoid confuse this with a standard kernel internal API.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sw_sync.
From: Gustavo Padovan
The common behaviour for trace headers is to have them in the same folder
they are used, instead of creating a special trace/ directory.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sw_sync.c | 2 +-
drivers/staging/android/{trace/sync.h
From: Gustavo Padovan
Closing the timeline without waiting all fences to signal is not
a critical failure, it is just bad usage from userspace so avoid
calling WARN_ON in this case.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sw_sync.c | 2 +-
1 file changed, 1 insertion(+), 1 d
From: Gustavo Padovan
When creating a sync_pt the name received wasn't used anywhere.
Now we add it to the sync info debug output to make it easier to indetify
the userspace name of that sync pt.
Signed-off-by: Gustavo Padovan
---
drivers/staging/android/sw_sync.c| 16
dri
When building with "make W=1", we get multiple harmless build warnings
for the vpfe driver:
drivers/staging/media/davinci_vpfe/dm365_resizer.c:241:1: error: 'static' is
not at beginning of declaration [-Werror=old-style-declaration]
drivers/staging/media/davinci_vpfe/dm365_resizer.c: In function
On Sun, Jun 19, 2016 at 08:33:48PM +0800, Icenowy Zheng wrote:
> This commit adds Espressif ESP8089 driver, the SDIO version.
>
> ESP8089 is a 802.11b/g/n card with SDIO/SPI interface. It is usually used in
> low-price tablets with Allwiner or RockChip SoCs.
>
> Signed-off-by: Icenowy Zheng
Why
Hello,
On Sat, Jun 18, 2016 at 02:14:23PM +0530, Bhaktipriya Shridhar wrote:
> alloc_workqueue replaces deprecated create_workqueue().
> A dedicated workqueue has been used since the workitem (viz &ctx->work,
> which maps to vmbus_onmessage_work), is engaged in normal device
> operation which invo
A couple more changes to "plx9080.h" for easier extraction of fields
from register values, and macro naming consistency.
1) staging: comedi: plx9080.h: define PLX__TO_(r) macros
2) staging: comedi: plx9080.h: rename some macros for consistency
drivers/staging/comedi/drivers/cb_pcidas64.c | 4 +-
Most of the macros in "plx9080.h" that define register values are
single-bits flags of the form `PLX__`, or are constant,
multi-bit values of the form `PLX___`, or are
non-constant, function-like macros of the form `PLX__(x)`.
Some of the macros for constant, multi-bit values do not currently
fit t
Various macros in "plx9080.h" take the form `PLX__(x)`,
where `` is a register name, `` is a field within the
register, and `x` is a value for the field specified by the caller. The
macros construct a partial register register with the specified field
value placed in the appropriate bits of the re
> -Original Message-
> From: Binoy Jayan [mailto:binoy.ja...@linaro.org]
> Sent: Monday, June 20, 2016 1:07 AM
> To: Kershner, David A; Greg Kroah-Hartman
> Cc: Arnd Bergmann; *S-Par-Maintainer; de...@driverdev.osuosl.org; linux-
> ker...@vger.kernel.org; Binoy Jayan
> Subject: [PATCH] stag
Deconstruct the kthread / message_queue logic, replacing it with
create_singlethread_workqueue() / queue_work() setup, by adding a
'struct work_struct' to 'struct host_if_msg'. The current kthread
hostIFthread() is converted to a work queue helper with the name
'host_if_work'.
Signed-off-by: Binoy
This is the second patch series for 'wilc1000'. The original patch series
consisted 7 patches of which only the first 5 are good. The patch 6 and 7
are being worked on in this series in a different way.
This patch series removes the semaphore 'sem' in 'wilc1000' and also
restructures the implement
Move the contents of wilc_msgqueue.c and wilc_msgqueue.h into
host_interface.c, remove 'wilc_msgqueue.c' and 'wilc_msgqueue.h'.
This is done so as to restructure the implementation of the kthread
'hostIFthread' using a work queue.
Signed-off-by: Binoy Jayan
Reviewed-by: Arnd Bergmann
---
driver
75 matches
Mail list logo
