* [PATCH] staging: i2o: Used <linux/uaccess.h>
@ 2015-08-18 17:46 Aparna Karuthodi
2015-09-03 16:46 ` Greg KH
0 siblings, 1 reply; 4+ messages in thread
From: Aparna Karuthodi @ 2015-08-18 17:46 UTC (permalink / raw)
To: kdasaparna; +Cc: gregkh, linux-kernel, alan, devel
Used #include <linux/uaccess.h> instead of #include <asm/uaccess.h> to
remove a coding style warning detected by checkpatch.
The warning is given below:
drivers/staging/i2o/config-osm.c:22: WARNING: Use #include
<linux/uaccess.h> instead of <asm/uaccess.h>
Signed-off-by: Aparna Karuthodi <kdasaparna@gmail.com>
---
drivers/staging/i2o/config-osm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/i2o/config-osm.c b/drivers/staging/i2o/config-osm.c
index 519f52f..45091ac 100644
--- a/drivers/staging/i2o/config-osm.c
+++ b/drivers/staging/i2o/config-osm.c
@@ -19,7 +19,7 @@
#include <linux/namei.h>
#include <linux/fs.h>
-#include <asm/uaccess.h>
+#include <linux/uaccess.h>
#define OSM_NAME "config-osm"
#define OSM_VERSION "1.323"
--
1.7.9.5
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH] staging: i2o: Used <linux/uaccess.h>
2015-08-18 17:46 [PATCH] staging: i2o: Used <linux/uaccess.h> Aparna Karuthodi
@ 2015-09-03 16:46 ` Greg KH
2015-09-08 16:25 ` Albino B Neto
0 siblings, 1 reply; 4+ messages in thread
From: Greg KH @ 2015-09-03 16:46 UTC (permalink / raw)
To: Aparna Karuthodi; +Cc: linux-kernel, alan, devel
On Tue, Aug 18, 2015 at 11:16:46PM +0530, Aparna Karuthodi wrote:
> Used #include <linux/uaccess.h> instead of #include <asm/uaccess.h> to
> remove a coding style warning detected by checkpatch.
>
> The warning is given below:
> drivers/staging/i2o/config-osm.c:22: WARNING: Use #include
> <linux/uaccess.h> instead of <asm/uaccess.h>
>
> Signed-off-by: Aparna Karuthodi <kdasaparna@gmail.com>
> ---
> drivers/staging/i2o/config-osm.c | 2 +-
This file isn't in any kernel tree that I see anymore, what kernel did
you make this against?
greg k-h
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] staging: i2o: Used <linux/uaccess.h>
2015-09-03 16:46 ` Greg KH
@ 2015-09-08 16:25 ` Albino B Neto
2015-09-08 16:47 ` Greg KH
0 siblings, 1 reply; 4+ messages in thread
From: Albino B Neto @ 2015-09-08 16:25 UTC (permalink / raw)
To: Greg KH; +Cc: Aparna Karuthodi, devel, LKML, alan
2015-09-03 13:46 GMT-03:00 Greg KH <gregkh@linuxfoundation.org>:
> On Tue, Aug 18, 2015 at 11:16:46PM +0530, Aparna Karuthodi wrote:
>> Used #include <linux/uaccess.h> instead of #include <asm/uaccess.h> to
>> remove a coding style warning detected by checkpatch.
>
> This file isn't in any kernel tree that I see anymore, what kernel did
> you make this against?
Greg, he should fix code all files ?
--
Albino B Neto
www.bino.us
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] staging: i2o: Used <linux/uaccess.h>
2015-09-08 16:25 ` Albino B Neto
@ 2015-09-08 16:47 ` Greg KH
0 siblings, 0 replies; 4+ messages in thread
From: Greg KH @ 2015-09-08 16:47 UTC (permalink / raw)
To: Albino B Neto; +Cc: devel, alan, LKML, Aparna Karuthodi
On Tue, Sep 08, 2015 at 01:25:42PM -0300, Albino B Neto wrote:
> 2015-09-03 13:46 GMT-03:00 Greg KH <gregkh@linuxfoundation.org>:
> > On Tue, Aug 18, 2015 at 11:16:46PM +0530, Aparna Karuthodi wrote:
> >> Used #include <linux/uaccess.h> instead of #include <asm/uaccess.h> to
> >> remove a coding style warning detected by checkpatch.
> >
> > This file isn't in any kernel tree that I see anymore, what kernel did
> > you make this against?
>
> Greg, he should fix code all files ?
I'm sorry, but I can not parse that sentance, please try rewording it.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-09-08 16:47 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-08-18 17:46 [PATCH] staging: i2o: Used <linux/uaccess.h> Aparna Karuthodi
2015-09-03 16:46 ` Greg KH
2015-09-08 16:25 ` Albino B Neto
2015-09-08 16:47 ` Greg KH
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox