Fix a coding style issue.
Signed-off-by: Matei Oprea
Cc: ROSEdu Kernel Commmunity
---
drivers/staging/comedi/drivers/ni_daq_dio24.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/comedi/drivers/ni_daq_dio24.c
b/drivers/staging/comedi/drivers
oremap' was not declared. Should it be static?
* drivers/staging/cxt1e1/hwprobe.c:195:1:
warning: symbol 'cleanup_devs' was not declared. Should it be static?
drivers/staging/cxt1e1/hwprobe.c:293:1:
* warning: symbol 'c4hw_attach_all' was not declared. Should it be static?
I did it against your master branch of staging.git. I guess that's why
doesn't apply at all. I switched branches to staging-next after your
e-mail.
Thanks and sorry !
On Wed, Mar 19, 2014 at 1:14 AM, Greg KH wrote:
> On Wed, Mar 19, 2014 at 12:33:19AM +0200, Matei Oprea wrote:
>
Fix different address spaces when unmapping IO. hi->addr_mapped[0]
and hi->addr_mapped[1] should be tagged __iomem.
Signed-off-by: Matei Oprea
Cc: ROSEdu Kernel Community
---
drivers/staging/cxt1e1/hwprobe.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/d
Fix sparse "should be static" warnings. Those structures are
only referenced in file scope so they can be marked as static.
Signed-off-by: Matei Oprea
Cc: ROSEdu Kernel Community
---
drivers/staging/rtl8192u/r8192U_wx.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
This patch fixes "incorrect type in argument 1" warning from sparse.
Signed-off-by: Matei Oprea
Cc: ROSEdu Kernel Community
---
drivers/staging/cxt1e1/hwprobe.c |6 +++---
drivers/staging/cxt1e1/pmcc4_private.h |2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
di
Any comments on this ?
ᐧ
On Sun, Mar 23, 2014 at 2:13 PM, Matei Oprea wrote:
> This patch fixes "incorrect type in argument 1" warning from sparse.
>
> Signed-off-by: Matei Oprea
> Cc: ROSEdu Kernel Community
> ---
> drivers/staging/cxt1e1/hwprobe.c |
Sorry,
I thought that it's out.
ᐧ
On Mon, Apr 7, 2014 at 5:14 PM, Greg KH wrote:
> On Mon, Apr 07, 2014 at 03:38:27PM +0300, Matei Oprea wrote:
>> Any comments on this ?
>
> You got an email from me about this, on the 23rd, saying that I can't do
> anything w