IRQF_DISABLED flag is depricated and should be removed.
Signed-off-by: Kumar Gaurav
---
drivers/block/rsxx/core.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/block/rsxx/core.c b/drivers/block/rsxx/core.c
index a8de2ee..ddb6b2b 100644
--- a/drivers/block/rsxx
IRQF_DISABLED flag is depricated and should be removed.
Signed-off-by: Kumar Gaurav kumargauravgup...@gmail.com
---
drivers/block/rsxx/core.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/block/rsxx/core.c b/drivers/block/rsxx/core.c
index a8de2ee..ddb6b2b 100644
---
Please revert with comment on whether I am correct or not. If yes, I'll
submit the patches for upgrading codes to skip the overhead of checking
memory area for permission.
Regards,
Kumar Gaurav
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
with comment on whether I am correct or not. If yes, I'll
submit the patches for upgrading codes to skip the overhead of checking
memory area for permission.
Regards,
Kumar Gaurav
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord
Hi All,
Any update on below patch. Do i need to make any modification?
On Thursday 17 April 2014 09:25 PM, Kumar Gaurav wrote:
dgap driver uses semaphore for obtaining lock. I upgraded it to use MUTEX.
Signed-off-by: Kumar Gaurav
---
drivers/staging/dgap/dgap_tty.c | 17
Hi All,
Any update on below patch. Do i need to make any modification?
On Thursday 17 April 2014 09:25 PM, Kumar Gaurav wrote:
dgap driver uses semaphore for obtaining lock. I upgraded it to use MUTEX.
Signed-off-by: Kumar Gaurav kumargauravgup...@gmail.com
---
drivers/staging/dgap
dgap driver uses semaphore for obtaining lock. I upgraded it to use MUTEX.
Signed-off-by: Kumar Gaurav
---
drivers/staging/dgap/dgap_tty.c | 17 +
1 file changed, 5 insertions(+), 12 deletions(-)
diff --git a/drivers/staging/dgap/dgap_tty.c b/drivers/staging/dgap/dgap_tty.c
Hi All,
Please ignore this patch. I'm sending with correct Subject Line
On Thursday 17 April 2014 09:21 PM, Kumar Gaurav wrote:
dgap driver uses semaphore for obtaining lock. I upgraded it to use MUTEX.
Signed-off-by: Kumar Gaurav
---
drivers/staging/dgap/dgap_tty.c | 17
dgap driver uses semaphore for obtaining lock. I upgraded it to use MUTEX.
Signed-off-by: Kumar Gaurav
---
drivers/staging/dgap/dgap_tty.c | 17 +
1 file changed, 5 insertions(+), 12 deletions(-)
diff --git a/drivers/staging/dgap/dgap_tty.c b/drivers/staging/dgap/dgap_tty.c
dgap driver uses semaphore for obtaining lock. I upgraded it to use MUTEX.
Signed-off-by: Kumar Gaurav kumargauravgup...@gmail.com
---
drivers/staging/dgap/dgap_tty.c | 17 +
1 file changed, 5 insertions(+), 12 deletions(-)
diff --git a/drivers/staging/dgap/dgap_tty.c b
Hi All,
Please ignore this patch. I'm sending with correct Subject Line
On Thursday 17 April 2014 09:21 PM, Kumar Gaurav wrote:
dgap driver uses semaphore for obtaining lock. I upgraded it to use MUTEX.
Signed-off-by: Kumar Gaurav kumargauravgup...@gmail.com
---
drivers/staging/dgap
dgap driver uses semaphore for obtaining lock. I upgraded it to use MUTEX.
Signed-off-by: Kumar Gaurav kumargauravgup...@gmail.com
---
drivers/staging/dgap/dgap_tty.c | 17 +
1 file changed, 5 insertions(+), 12 deletions(-)
diff --git a/drivers/staging/dgap/dgap_tty.c b
On Wed, Sep 04, 2013 at 11:42:33AM +0530, Kumar Gaurav wrote:
On Tuesday 03 September 2013 09:34 PM, Sarah Sharp wrote:
I'm confused. I said the last version of this patch didn't apply
against usb-next, and you should rebase it. Why did you put "No Change"
in the subject prefix?
I miss
On Wed, Sep 04, 2013 at 11:42:33AM +0530, Kumar Gaurav wrote:
On Tuesday 03 September 2013 09:34 PM, Sarah Sharp wrote:
I'm confused. I said the last version of this patch didn't apply
against usb-next, and you should rebase it. Why did you put No Change
in the subject prefix?
I miss understood
if there's
no change from previous patch, but he didn't meant in subject (my bad).
On Sat, Aug 31, 2013 at 11:02:45PM +0530, Kumar Gaurav wrote:
This patch redefine function xhci_readl. xhci_readl function doesn't use
xhci_hcd argument.
Hence there is no need of keeping it in the function
no change from previous patch, but he didn't meant in subject (my bad).
On Sat, Aug 31, 2013 at 11:02:45PM +0530, Kumar Gaurav wrote:
This patch redefine function xhci_readl. xhci_readl function doesn't use
xhci_hcd argument.
Hence there is no need of keeping it in the function arguments.
Redefining
I tried applying this patch on linux-next and it applies well.
i used
git apply --apply
On Saturday 31 August 2013 11:02 PM, Kumar Gaurav wrote:
This patch redefine function xhci_readl. xhci_readl function doesn't use
xhci_hcd argument.
Hence there is no need of keeping
I tried applying this patch on linux-next and it applies well.
i used
git apply --apply
On Saturday 31 August 2013 11:02 PM, Kumar Gaurav wrote:
This patch redefine function xhci_readl. xhci_readl function doesn't use
xhci_hcd argument.
Hence there is no need of keeping
-off-by: Kumar Gaurav
---
drivers/usb/host/xhci-dbg.c | 36 -
drivers/usb/host/xhci-hub.c | 72 -
drivers/usb/host/xhci-mem.c | 20 -
drivers/usb/host/xhci-ring.c | 12 +++---
drivers/usb/host/xhci.c | 92
-off-by: Kumar Gaurav kumargauravgup...@gmail.com
---
drivers/usb/host/xhci-dbg.c | 36 -
drivers/usb/host/xhci-hub.c | 72 -
drivers/usb/host/xhci-mem.c | 20 -
drivers/usb/host/xhci-ring.c | 12 +++---
drivers/usb/host/xhci.c
On Wednesday 28 August 2013 10:31 PM, Sarah Sharp wrote:
On Wed, Aug 28, 2013 at 08:39:06PM +0530, Kumar Gaurav wrote:
On Wednesday 28 August 2013 12:43 PM, Dan Carpenter wrote:
On Mon, Aug 26, 2013 at 07:38:57AM +0530, Kumar Gaurav wrote:
I've started cloning linux-next and as it's
On Wednesday 28 August 2013 12:43 PM, Dan Carpenter wrote:
On Mon, Aug 26, 2013 at 07:38:57AM +0530, Kumar Gaurav wrote:
This patch redefine function xhci_readl.xhci_readl function doesn't use
xhci_hcd argument.
Hence there is no need of keeping it in the function arguments.
Redefining
On Wednesday 28 August 2013 12:43 PM, Dan Carpenter wrote:
On Mon, Aug 26, 2013 at 07:38:57AM +0530, Kumar Gaurav wrote:
This patch redefine function xhci_readl.xhci_readl function doesn't use
xhci_hcd argument.
Hence there is no need of keeping it in the function arguments.
Redefining
On Wednesday 28 August 2013 10:31 PM, Sarah Sharp wrote:
On Wed, Aug 28, 2013 at 08:39:06PM +0530, Kumar Gaurav wrote:
On Wednesday 28 August 2013 12:43 PM, Dan Carpenter wrote:
On Mon, Aug 26, 2013 at 07:38:57AM +0530, Kumar Gaurav wrote:
I've started cloning linux-next and as it's
-by: Kumar Gaurav
---
drivers/usb/host/xhci-dbg.c | 36 +++
drivers/usb/host/xhci-hub.c | 72 +++---
drivers/usb/host/xhci-mem.c | 20 -
drivers/usb/host/xhci-ring.c | 12 ++---
drivers/usb/host/xhci.c | 100
-by: Kumar Gaurav kumargauravgup...@gmail.com
---
drivers/usb/host/xhci-dbg.c | 36 +++
drivers/usb/host/xhci-hub.c | 72 +++---
drivers/usb/host/xhci-mem.c | 20 -
drivers/usb/host/xhci-ring.c | 12 ++---
drivers/usb/host/xhci.c | 100
-by: Kumar Gaurav
---
drivers/usb/host/xhci-dbg.c | 36 +++
drivers/usb/host/xhci-hub.c | 72 +++---
drivers/usb/host/xhci-mem.c | 20 -
drivers/usb/host/xhci-ring.c | 12 ++---
drivers/usb/host/xhci.c | 100
-by: Kumar Gaurav kumargauravgup...@gmail.com
---
drivers/usb/host/xhci-dbg.c | 36 +++
drivers/usb/host/xhci-hub.c | 72 +++---
drivers/usb/host/xhci-mem.c | 20 -
drivers/usb/host/xhci-ring.c | 12 ++---
drivers/usb/host/xhci.c | 100
Fixing other programs in xhci driver which calls this function
Signed-off-by: Kumar Gaurav
---
drivers/usb/host/xhci-dbg.c | 36 +++
drivers/usb/host/xhci-hub.c | 72 +++---
drivers/usb/host/xhci-mem.c | 20 -
drivers/usb/host/xhci-ring.c
Fixing other programs in xhci driver which calls this function
Signed-off-by: Kumar Gaurav kumargauravgup...@gmail.com
---
drivers/usb/host/xhci-dbg.c | 36 +++
drivers/usb/host/xhci-hub.c | 72 +++---
drivers/usb/host/xhci-mem.c | 20
lly helps and that i have understood the discussion.
re,
wh
Thanks for the clarification. I'll be following this.
Regards
Kumar Gaurav
Am 10.08.2013 20:15, schrieb Kumar Gaurav:
On Saturday 10 August 2013 10:54 PM, Julia Lawall wrote:
On Sat, 10 Aug 2013, Kumar Gaurav wrote:
On Saturday 1
On Saturday 10 August 2013 10:54 PM, Julia Lawall wrote:
On Sat, 10 Aug 2013, Kumar Gaurav wrote:
On Saturday 10 August 2013 10:17 PM, Julia Lawall wrote:
If it is in a | with something else, I think you can just remove it.
julia
On Sat, 10 Aug 2013, Kumar Gaurav wrote:
Removed
On Saturday 10 August 2013 10:17 PM, Julia Lawall wrote:
If it is in a | with something else, I think you can just remove it.
julia
On Sat, 10 Aug 2013, Kumar Gaurav wrote:
Removed IRQF_DISABLED as it's deprecated and should be removed
Signed-off-by: Kumar Gaurav
---
drivers/net/hamradio
Removed IRQF_DISABLED as it's deprecated and should be removed
Signed-off-by: Kumar Gaurav
---
drivers/net/hamradio/baycom_ser_fdx.c |2 +-
drivers/net/hamradio/baycom_ser_hdx.c |2 +-
drivers/net/hamradio/scc.c|2 +-
drivers/net/hamradio/yam.c|2 +-
4
Removed IRQF_DISABLED as it's deprecated and should be removed
Signed-off-by: Kumar Gaurav kumargauravgup...@gmail.com
---
drivers/net/hamradio/baycom_ser_fdx.c |2 +-
drivers/net/hamradio/baycom_ser_hdx.c |2 +-
drivers/net/hamradio/scc.c|2 +-
drivers/net/hamradio/yam.c
On Saturday 10 August 2013 10:17 PM, Julia Lawall wrote:
If it is in a | with something else, I think you can just remove it.
julia
On Sat, 10 Aug 2013, Kumar Gaurav wrote:
Removed IRQF_DISABLED as it's deprecated and should be removed
Signed-off-by: Kumar Gaurav kumargauravgup...@gmail.com
On Saturday 10 August 2013 10:54 PM, Julia Lawall wrote:
On Sat, 10 Aug 2013, Kumar Gaurav wrote:
On Saturday 10 August 2013 10:17 PM, Julia Lawall wrote:
If it is in a | with something else, I think you can just remove it.
julia
On Sat, 10 Aug 2013, Kumar Gaurav wrote:
Removed
the discussion.
re,
wh
Thanks for the clarification. I'll be following this.
Regards
Kumar Gaurav
Am 10.08.2013 20:15, schrieb Kumar Gaurav:
On Saturday 10 August 2013 10:54 PM, Julia Lawall wrote:
On Sat, 10 Aug 2013, Kumar Gaurav wrote:
On Saturday 10 August 2013 10:17 PM, Julia Lawall wrote
On Saturday 10 August 2013 01:08 AM, Sergei Shtylyov wrote:
Hello.
On 08/09/2013 10:25 PM, Kumar Gaurav wrote:
Removed IRQF_DISABLED as it is deprecated and fixed a coding style issue
of more than 80 chars on single line by sliting the line in two.
That's clearly a material for 2
It's a single patch. Please don't be confused with the subject [PATCH
17/17]. I forgot to edit this before sending.
my apology for mistake
On Friday 09 August 2013 11:55 PM, Kumar Gaurav wrote:
Removed IRQF_DISABLED as it is deprecated and fixed a coding style issue
of more than 80 chars
Removed IRQF_DISABLED as it is deprecated and fixed a coding style issue
of more than 80 chars on single line by sliting the line in two.
Signed-off-by: Kumar Gaurav
---
drivers/net/ethernet/lantiq_etop.c |8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/drivers/net
Removed IRQF_DISABLED as it is deprecated and fixed a coding style issue
of more than 80 chars on single line by sliting the line in two.
Signed-off-by: Kumar Gaurav kumargauravgup...@gmail.com
---
drivers/net/ethernet/lantiq_etop.c |8 +---
1 file changed, 5 insertions(+), 3 deletions
It's a single patch. Please don't be confused with the subject [PATCH
17/17]. I forgot to edit this before sending.
my apology for mistake
On Friday 09 August 2013 11:55 PM, Kumar Gaurav wrote:
Removed IRQF_DISABLED as it is deprecated and fixed a coding style issue
of more than 80 chars
On Saturday 10 August 2013 01:08 AM, Sergei Shtylyov wrote:
Hello.
On 08/09/2013 10:25 PM, Kumar Gaurav wrote:
Removed IRQF_DISABLED as it is deprecated and fixed a coding style issue
of more than 80 chars on single line by sliting the line in two.
That's clearly a material for 2
Please ignore the below patch. I'll be resending this with 0 instead of
IRQF_TRIGGER_NONE
On Friday 09 August 2013 08:47 AM, Kumar Gaurav wrote:
Removed IRQF_DISABLED as it's no-op and should be removed
Signed-off-by: Kumar Gaurav
---
arch/avr32/kernel/time.c |2 +-
1 file changed, 1
Removed IRQF_DISABLED as it's no-op and should be removed
Signed-off-by: Kumar Gaurav
---
arch/avr32/kernel/time.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/avr32/kernel/time.c b/arch/avr32/kernel/time.c
index 869a1c6..0566c81 100644
--- a/arch/avr32/kernel
Fixed by removing trailing whitespace
Signed-off-by: Kumar Gaurav
---
drivers/staging/zram/zram_drv.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/zram/zram_drv.c b/drivers/staging/zram/zram_drv.c
index 82c7202..f590715 100644
--- a/drivers/staging/zram
Fixed by removing trailing whitespace
Signed-off-by: Kumar Gaurav kumargauravgup...@gmail.com
---
drivers/staging/zram/zram_drv.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/zram/zram_drv.c b/drivers/staging/zram/zram_drv.c
index 82c7202..f590715 100644
Removed IRQF_DISABLED as it's no-op and should be removed
Signed-off-by: Kumar Gaurav kumargauravgup...@gmail.com
---
arch/avr32/kernel/time.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/avr32/kernel/time.c b/arch/avr32/kernel/time.c
index 869a1c6..0566c81 100644
Please ignore the below patch. I'll be resending this with 0 instead of
IRQF_TRIGGER_NONE
On Friday 09 August 2013 08:47 AM, Kumar Gaurav wrote:
Removed IRQF_DISABLED as it's no-op and should be removed
Signed-off-by: Kumar Gaurav kumargauravgup...@gmail.com
---
arch/avr32/kernel/time.c
Fixed issue by removing Space before semicolon
Signed-off-by: Kumar Gaurav
---
drivers/staging/xgifb/vb_setmode.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/xgifb/vb_setmode.h
b/drivers/staging/xgifb/vb_setmode.h
index 2c0a31c..679a822 100644
Fixed issue by removing Space before semicolon
Signed-off-by: Kumar Gaurav kumargauravgup...@gmail.com
---
drivers/staging/xgifb/vb_setmode.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/xgifb/vb_setmode.h
b/drivers/staging/xgifb/vb_setmode.h
index
52 matches
Mail list logo
