After changing the comments format, the other error disappears.
So silences two checkpatch errors:
ERROR: do not use C99 // comments
ERROR: trailing statements should be on next line
Signed-off-by: Janet Liu
---
drivers/staging/lustre/lnet/lnet/lib-md.c |6 +++---
1 file changed, 3 inser
Silences the following checkpatch warning:
WARNING: space prohibited between function name and open parenthesis '('
Signed-off-by: Janet Liu
---
drivers/staging/lustre/lnet/lnet/lib-md.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/staging/lu
Silences the following checkpatch warning:
WARNING: line over 80 characters
Signed-off-by: Janet Liu
---
drivers/staging/lustre/lnet/lnet/lib-md.c | 15 +--
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/lustre/lnet/lnet/lib-md.c
b/drivers/staging/
Signed-off-by: Chase Southwood
Cc: Ian Abbott
Cc: H Hartley Sweeten
---
.../comedi/drivers/addi-data/hwdrv_apci1564.c | 23 --
drivers/staging/comedi/drivers/addi_apci_1564.c| 23 ++
2 files changed, 23 insertions(+), 23 deletions(-)
diff --git
Sparse has many warnings like:
drivers/staging/comedi/drivers/usbduxsigma.c:293:21: warning: cast to
restricted __be32
on lines on which devpriv->in_buf is passed to be32_to_cpu(). This
suggests that this variable should actually be of type __be32.
Signed-off-by: Chase Southwood
Cc: Ian Abbott
Sparse has many warnings like:
drivers/staging/comedi/drivers/usbdux.c:366:32: warning: cast to
restricted __le16
on lines on which devpriv->in_buf or devpriv->insn_buf are passed to
le16_to_cpu(). This suggests that both of these variables should actually
be of type __le16.
Signed-off-by: Chas
Remove insignificant spaces before tabs in comments.
Signed-off-by: Andrew Plummer
---
drivers/staging/bcm/LeakyBucket.c | 81 ---
1 file changed, 33 insertions(+), 48 deletions(-)
diff --git a/drivers/staging/bcm/LeakyBucket.c
b/drivers/staging/bcm/LeakyBuc
On Fri, Aug 29, 2014 at 05:18:51PM +, KY Srinivasan wrote:
>
> > -Original Message-
> > From: Sitsofe Wheeler [mailto:sits...@gmail.com]
> > Sent: Friday, August 29, 2014 2:32 AM
> > To: Dexuan Cui
> > Cc: KY Srinivasan; Greg Kroah-Hartman; Haiyang Zhang;
> > de...@linuxdriverproject.o
The following changes since commit 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9:
Linux 3.17-rc1 (2014-08-16 10:40:26 -0600)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/
tags/staging-3.17-rc3
for you to fetch changes up to a2fa6721c72
> -Original Message-
> From: Sitsofe Wheeler [mailto:sits...@gmail.com]
> Sent: Friday, August 29, 2014 2:32 AM
> To: Dexuan Cui
> Cc: KY Srinivasan; Greg Kroah-Hartman; Haiyang Zhang;
> de...@linuxdriverproject.org; linux-ker...@vger.kernel.org;
> net...@vger.kernel.org; David Miller; Da
> -Original Message-
> From: Sitsofe Wheeler [mailto:sits...@gmail.com]
> Sent: Friday, August 29, 2014 2:32 AM
> To: Dexuan Cui
> Cc: KY Srinivasan; Greg Kroah-Hartman; Haiyang Zhang;
> de...@linuxdriverproject.org; linux-ker...@vger.kernel.org;
> net...@vger.kernel.org; David Miller; Da
On Thu, 2014-08-28 at 21:42 -0500, Mike Christie wrote:
> On 08/27/2014 09:31 AM, Hannes Reinecke wrote:
> > On 08/19/2014 07:54 PM, Christoph Hellwig wrote:
> >> On Sat, Aug 16, 2014 at 08:09:48PM -0700, K. Y. Srinivasan wrote:
> >>> The host asks the guest to scan when a LUN is removed or added.
> -Original Message-
> From: Sitsofe Wheeler
> Sent: Friday, August 29, 2014 19:20 PM
> Because this particular return code is overloaded with multiple meanings
> that can't necessarily be deduced from its name perhaps this
> documentation patch would be helpful:
>
> diff --git a/arch/x86/
Add support for enumerating the device through ACPI.
Signed-off-by: Laurentiu Palcu
---
drivers/staging/iio/light/isl29018.c | 46 +++-
1 file changed, 40 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/iio/light/isl29018.c
b/drivers/staging/iio/light
isl29108 was used, instead of isl29018.
Signed-off-by: Laurentiu Palcu
---
drivers/staging/iio/light/isl29018.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/iio/light/isl29018.c
b/drivers/staging/iio/light/isl29018.c
index 86cc8f9..63c70be 100644
-
Intersil chips ISL29018, ISL29023 and ISL29035 are very similar. They're
all ambience light sensors. The ISL29018, however, is also a proximity
sensor. The registers are similar too:
-+--+--
AVAILABLE IN | ADDR REG | NAME
290xx | |
-+
Hi,
This patchset adds support for 2 similar ALS chips: ISL29023 and ISL29035.
The chip I performed tests on was a ISL29035, since I didn't have eval boards,
for the
other 2 chips, handy.
The registers tables for each chip can be found here:
ISL29018: [1] - page 10
ISL29023: [2] - page 8
ISL29
On Fri, 2014-08-29 at 10:13 +0200, Hannes Reinecke wrote:
> On 08/29/2014 09:39 AM, Bart Van Assche wrote:
> > On 08/29/14 08:19, Hannes Reinecke wrote:
> >> On 08/29/2014 04:42 AM, Mike Christie wrote:
> >>> How are distros handling 0x6/0x3f/0x0e (report luns changed) when it
> >>> gets passed to
Dear Sir,
I am the Chairman of the Contract Award Committee of the Republic of Nile
Petroleum Corporation (NILEPET) which is an integral part of the Republic of
South Sudan and it's the commercial arm of Ministry of Petroleum & Mining. I
choose to get in touch with you regarding how we can joi
Dear Sir,
I am the Chairman of the Contract Award Committee of the Republic of Nile
Petroleum Corporation (NILEPET) which is an integral part of the Republic of
South Sudan and it's the commercial arm of Ministry of Petroleum & Mining. I
choose to get in touch with you regarding how we can joi
On Fri, Aug 29, 2014 at 01:24:11PM +0300, Dan Carpenter wrote:
> On Fri, Aug 29, 2014 at 10:16:32AM +, Dexuan Cui wrote:
> >
> > Section 4.11.3 of Hypervisor Top Level Functional Specification(available at
> > http://blogs.msdn.com/b/virtual_pc_guy/archive/2014/02/17/updated-hypervisor-top-lev
On Fri, Aug 29, 2014 at 10:16:32AM +, Dexuan Cui wrote:
> Hi Dan,
>
> Section 4.11.3 of Hypervisor Top Level Functional Specification(available at
> http://blogs.msdn.com/b/virtual_pc_guy/archive/2014/02/17/updated-hypervisor-top-level-functional-specification.aspx)
> says HV_STATUS_INVALID_AL
> -Original Message-
> From: Dan Carpenter
> Sent: Friday, August 29, 2014 17:50 PM
> To: KY Srinivasan
> Cc: Sitsofe Wheeler; Dexuan Cui; Greg Kroah-Hartman; Haiyang Zhang;
> linux-ker...@vger.kernel.org; de...@linuxdriverproject.org
> Subject: Re: [PANIC, hyperv] BUG: unable to handle ker
It's sort of weird that this is an alignment issue. The config that
was posted earlier was an x86_64 config and on that system then the
pointers from kmalloc() should already be aligned correctly at
sizeof(u64).
Earlier I said I suspected the code is racy, so possibly changing from
kmalloc() to g
While booting a 10 vcpu system with a post v3.17-rc2 kernel with the
"Drivers: hv: vmbus: Eliminate calls to BUG_ON()", "Drivers: hv: vmbus:
Miscellaneous cleanup" patches and debugging/verification config options
on I'm seeing the following:
[ 31.570860] EXT4-fs (sdb1): mounted filesystem with
On Thu, Aug 28, 2014 at 06:29:52PM -0700, K. Y. Srinivasan wrote:
> Minimize failures in this function by pre-allocating the buffer
> for posting messages. The hypercall for posting the message can fail
> for a number of reasons:
>
>
> Cc:
Is this patch useful for all longterm (2.6.32.63, 3.2.
On 08/29/2014 09:39 AM, Bart Van Assche wrote:
On 08/29/14 08:19, Hannes Reinecke wrote:
On 08/29/2014 04:42 AM, Mike Christie wrote:
How are distros handling 0x6/0x3f/0x0e (report luns changed) when it
gets passed to userspace? Is everyone kicking off a new full (add and
delete) scan to handle
On Thu, Aug 28, 2014 at 06:29:33PM -0700, K. Y. Srinivasan wrote:
> Cleanup hv_post_message() to minimize failures. Also disable preemption
> when sampling CPU ID when preemption is otherwise possible.
>
> K. Y. Srinivasan (2):
> Drivers: hv: vmbus: Cleanup hv_post_message()
> Drivers: hv: vmb
On 08/29/14 08:19, Hannes Reinecke wrote:
> On 08/29/2014 04:42 AM, Mike Christie wrote:
>> How are distros handling 0x6/0x3f/0x0e (report luns changed) when it
>> gets passed to userspace? Is everyone kicking off a new full (add and
>> delete) scan to handle this or logging it? Is the driver retur
On Wed, Aug 27, 2014 at 04:25:05PM -0700, K. Y. Srinivasan wrote:
> Cleanup the channel management code and eliminate calls to BUG_ON().
> Also fix an error propagation bug in vmbus_open().
>
> In this version of the patch-set, I have addressed comments from
> Dan Carpenter.
>
> K. Y. Srinivasan
30 matches
Mail list logo
