Re: [PATCH] Staging: omap4iss: fix coding style issues

28.01.2017, 20:11, "Avraham Shukron" : > This is a patch that fixes issues in omap4iss/iss_video.c > Specifically, it fixes "line over 80 characters" issues Hello, are you have a sent this changes patch before? And Greg KH answered you, are you read? Please send the

Re: [PATCH] Staging: omap4iss: fix coding style issues

28.01.2017, 20:11, "Avraham Shukron" : > This is a patch that fixes issues in omap4iss/iss_video.c > Specifically, it fixes "line over 80 characters" issues Hello, are you have a sent this changes patch before? And Greg KH answered you, are you read? Please send the change once, there is no

Re: lkml.org issues

26.12.2016, 10:46, "Nikita Yushchenko" : > Hi > > Is lkml.org supported? > > Currently: > > - [headers] link on top of pages does not show message headers, You can just display the header's list. > - [forward] link on top of pages is not functional - it

Re: lkml.org issues

26.12.2016, 10:46, "Nikita Yushchenko" : > Hi > > Is lkml.org supported? > > Currently: > > - [headers] link on top of pages does not show message headers, You can just display the header's list. > - [forward] link on top of pages is not functional - it requests text > from captcha but does

Re: Question regarding power button of Dell XPS13

26.12.2016, 00:27, "Linus Torvalds" : > On Fri, Dec 23, 2016 at 4:36 AM, Paul Menzel wrote: >>  I heard that you both have a Dell XPS13. I got the “revision” 9360, and >>  installed Debian Stretch/testing on it with Linux 4.8.15 and Linux

Re: Question regarding power button of Dell XPS13

26.12.2016, 00:27, "Linus Torvalds" : > On Fri, Dec 23, 2016 at 4:36 AM, Paul Menzel wrote: >>  I heard that you both have a Dell XPS13. I got the “revision” 9360, and >>  installed Debian Stretch/testing on it with Linux 4.8.15 and Linux 4.9-rc8. >> >>  When pressing the power button the GNOME

Re: [PATCH 2/2] net: wireless: fix to uses struct

22.12.2016, 01:06, "Paul Bolle" <pebo...@tiscali.nl>: > On Thu, 2016-12-22 at 01:50 +0300, Ozgur Karatas wrote: >>  I don't have a problem with C programming > > I'm sorry, but you do need to learn C, at a basic level, first. Hmm, I don't like to discussion but I'm

Re: [PATCH 2/2] net: wireless: fix to uses struct

22.12.2016, 01:06, "Paul Bolle" : > On Thu, 2016-12-22 at 01:50 +0300, Ozgur Karatas wrote: >>  I don't have a problem with C programming > > I'm sorry, but you do need to learn C, at a basic level, first. Hmm, I don't like to discussion but I'm an assertive on C/C++. S

Re: [PATCH 2/2] net: wireless: fix to uses struct

My previous patch is invalid, I'm sorry. The last patc will be fellow because "regulatory_request" is defined as a "static struct". Signed-off-by: Ozgur Karatas <okara...@member.fsf.org> --- net/wireless/reg.c | 10 +- 2 files changed, 2 insertions(+), 2 dele

Re: [PATCH 2/2] net: wireless: fix to uses struct

My previous patch is invalid, I'm sorry. The last patc will be fellow because "regulatory_request" is defined as a "static struct". Signed-off-by: Ozgur Karatas --- net/wireless/reg.c | 10 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/net/

Re: [PATCH 2/2] net: wireless: fix to uses struct

22.12.2016, 00:34, "Paul Bolle" <pebo...@tiscali.nl>: > On Thu, 2016-12-22 at 00:23 +0200, Ozgur Karatas wrote: >>  I compiled and didn't to errors. > > Really? I'm very sorry. The "regulatory_request" is defined a static struct. I missed

Re: [PATCH 2/2] net: wireless: fix to uses struct

22.12.2016, 00:34, "Paul Bolle" : > On Thu, 2016-12-22 at 00:23 +0200, Ozgur Karatas wrote: >>  I compiled and didn't to errors. > > Really? I'm very sorry. The "regulatory_request" is defined a static struct. I missed. line: static struct regulatory_req

[PATCH 2/2] net: wireless: fix to uses struct

The patch fixed to struct uses in reg.c, I think doesn't need to be use to "struct". There is dataype not have to logical link and each is different definitons. I'm undecided on this patch. I compiled and didn't to errors. Signed-off-by: Ozgur Karatas <okara...@member.fsf.

[PATCH 2/2] net: wireless: fix to uses struct

The patch fixed to struct uses in reg.c, I think doesn't need to be use to "struct". There is dataype not have to logical link and each is different definitons. I'm undecided on this patch. I compiled and didn't to errors. Signed-off-by: Ozgur Karatas --- net/wireless/r

[PATCH 1/2] net: wireless: fixed to checkpatch errors

Fixed to checkpatch errors, Normally, comment's */ had to be finish on the next line. The patch fix to readability and Coding Style. Sİgned-off-by: Ozgur Karatas <okara...@member.fsf.org> --- net/wireless/chan.c | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git

[PATCH 1/2] net: wireless: fixed to checkpatch errors

Fixed to checkpatch errors, Normally, comment's */ had to be finish on the next line. The patch fix to readability and Coding Style. Sİgned-off-by: Ozgur Karatas --- net/wireless/chan.c | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/net/wireless/chan.c b/net/wireless

Re: [PATCH] Documentation/unaligned-memory-access.txt: fix incorrect comparison operator

y been fixed with patch. I tested it. > Meanwhile, there was a question from Ozgur Karatas on the patch, but I've > not yet seen your response. If you see fit your approval. > Thanks, > > jon Regards, ~Ozgur

Re: [PATCH] Documentation/unaligned-memory-access.txt: fix incorrect comparison operator

verlooked to change >>  this operator to reflect the actual function. > > I received this patch two days ago; has something changed that you're > sending it again? My opinion, the patch its update. The assignment of "!=0" has already been fixed with patch. I tested it. >

Re: Documentation/unaligned-memory-access.txt: fix incorrect comparison operator

20.12.2016, 02:22, "Cihangir Akturk" <cakt...@gmail.com>: > On Sun, Dec 18, 2016 at 12:52:12AM +0200, Ozgur Karatas wrote: >>  17.12.2016, 19:43, "Cihangir Akturk" <cakt...@gmail.com>: >>  > In the actual implementation ether_addr_equal functio

Re: Documentation/unaligned-memory-access.txt: fix incorrect comparison operator

20.12.2016, 02:22, "Cihangir Akturk" : > On Sun, Dec 18, 2016 at 12:52:12AM +0200, Ozgur Karatas wrote: >>  17.12.2016, 19:43, "Cihangir Akturk" : >>  > In the actual implementation ether_addr_equal function tests for equality >> to 0 >>  > wh

Re: [PATCH 1/1] kernel: futex: fixed to else and initcall

20.12.2016, 11:21, "Thomas Gleixner" <t...@linutronix.de>: > On Mon, 19 Dec 2016, Ozgur Karatas wrote: > >>  else doesn't need to be used, if should be enclosed in parentheses. > > Really? > > > So you change the code from > > if (err <

Re: [PATCH 1/1] kernel: futex: fixed to else and initcall

20.12.2016, 11:21, "Thomas Gleixner" : > On Mon, 19 Dec 2016, Ozgur Karatas wrote: > >>  else doesn't need to be used, if should be enclosed in parentheses. > > Really? > > > So you change the code from > > if (err < 0) > ret

[PATCH 1/1] kernel: futex: fixed to else and initcall

scripts and fixed to errors. ERROR: "(foo*)" should be "(foo *)" ERROR: "foo * bar" should be "foo *bar" ERROR: "foo * bar" should be "foo *bar" Signed-off-by: Ozgur Karatas <okara...@member.fsf.org> --- kernel/futex.c | 12 ++-

[PATCH 1/1] kernel: futex: fixed to else and initcall

scripts and fixed to errors. ERROR: "(foo*)" should be "(foo *)" ERROR: "foo * bar" should be "foo *bar" ERROR: "foo * bar" should be "foo *bar" Signed-off-by: Ozgur Karatas --- kernel/futex.c | 12 ++-- 1 file changed, 6 inserti

Re: [PATCH] drivers: staging: fbtft: fix checkpatch error and udelay

); finally: $ checkpatch.pl drivers/staging/fbtft/fb_agm1264k-fl.c | grep total total: 0 errors Signed-off-by: Ozgur Karatas <okara...@member.fsf.org> --- drivers/staging/fbtft/fb_agm1264k-fl.c | 31 --- 1 file changed, 12 insertions(+), 19 deletions(-) diff

Re: [PATCH] drivers: staging: fbtft: fix checkpatch error and udelay

d give a some errors. So, the code have to "udelay(20)". udelay(20); I read to Documentation/timers/timers-howto.txt and this line incorrect, usleep_range need must be add defined U_DELAY and fixed. udelay(U_DELAY, U_DELAY + 10); finally: $ checkpatch.pl drivers/staging/fbtft

Re: Documentation/unaligned-memory-access.txt: fix incorrect comparison operator

17.12.2016, 19:43, "Cihangir Akturk" : > In the actual implementation ether_addr_equal function tests for equality to 0 > when returning. It seems in commit 0d74c4 it is somehow overlooked to change > this operator to reflect the actual function. why this "return" function need

Re: Documentation/unaligned-memory-access.txt: fix incorrect comparison operator

17.12.2016, 19:43, "Cihangir Akturk" : > In the actual implementation ether_addr_equal function tests for equality to 0 > when returning. It seems in commit 0d74c4 it is somehow overlooked to change > this operator to reflect the actual function. why this "return" function need to be ==0? I

Re: [PATCH 1/1] tools: net: bpf_dbg.c fixed keyboard typo

16.12.2016, 21:08, "Sergei Shtylyov" <sergei.shtyl...@cogentembedded.com>: > Hello. Hi > On 12/16/2016 09:21 PM, Ozgur Karatas wrote: > >>  This patch fixed to keyboard typo, brackets not closed. >>  I think, it should be close to parenthes. >&

Re: [PATCH 1/1] tools: net: bpf_dbg.c fixed keyboard typo

16.12.2016, 21:08, "Sergei Shtylyov" : > Hello. Hi > On 12/16/2016 09:21 PM, Ozgur Karatas wrote: > >>  This patch fixed to keyboard typo, brackets not closed. >>  I think, it should be close to parenthes. >> >>  Signed-off-by: Ozgur Karatas >

Re: [PATCH 1/1] tools: net: bpf_dbg.c fixed keyboard typo

16.12.2016, 20:35, "Joe Perches" <j...@perches.com>: > On Fri, 2016-12-16 at 20:21 +0200, Ozgur Karatas wrote: >>  This patch fixed to keyboard typo, brackets not closed. >>  I think, it should be close to parenthes. > > No. > > Please compile and test y

Re: [PATCH 1/1] tools: net: bpf_dbg.c fixed keyboard typo

16.12.2016, 20:35, "Joe Perches" : > On Fri, 2016-12-16 at 20:21 +0200, Ozgur Karatas wrote: >>  This patch fixed to keyboard typo, brackets not closed. >>  I think, it should be close to parenthes. > > No. > > Please compile and test your patches on your own

Re: [PATCH 1/1] tools: net: bpf_dbg.c fixed keyboard typo

16.12.2016, 20:35, "Joe Perches" <j...@perches.com>: > On Fri, 2016-12-16 at 20:21 +0200, Ozgur Karatas wrote: >>  This patch fixed to keyboard typo, brackets not closed. >>  I think, it should be close to parenthes. > > No. > > Please compile and test y

Re: [PATCH 1/1] tools: net: bpf_dbg.c fixed keyboard typo

16.12.2016, 20:35, "Joe Perches" : > On Fri, 2016-12-16 at 20:21 +0200, Ozgur Karatas wrote: >>  This patch fixed to keyboard typo, brackets not closed. >>  I think, it should be close to parenthes. > > No. > > Please compile and test your patches on your own

[PATCH 1/1] tools: net: bpf_dbg.c fixed keyboard typo

This patch fixed to keyboard typo, brackets not closed. I think, it should be close to parenthes. Signed-off-by: Ozgur Karatas <okara...@member.fsf.org> --- tools/net/bpf_dbg.c | 2 +- 1 files changed, 1 insertion(+), 1 deletions(-) diff --git a/tools/net/bpf_dbg.c b/tools/net/bpf

[PATCH 1/1] tools: net: bpf_dbg.c fixed keyboard typo

This patch fixed to keyboard typo, brackets not closed. I think, it should be close to parenthes. Signed-off-by: Ozgur Karatas --- tools/net/bpf_dbg.c | 2 +- 1 files changed, 1 insertion(+), 1 deletions(-) diff --git a/tools/net/bpf_dbg.c b/tools/net/bpf_dbg.c index 4f254bc..f715f46

Re: [PATCH 1/1] Fixed to codestyle

12.12.2016, 22:50, "Joe Perches" <j...@perches.com>: > On Mon, 2016-12-12 at 14:41 -0600, Eric Sandeen wrote: >>  On 12/12/16 2:34 PM, Ozgur Karatas wrote: > > [] >>  > Can you tell me the true code style? should use to (* uuid)? >>  > I'm lea

Re: [PATCH 1/1] Fixed to codestyle

12.12.2016, 22:50, "Joe Perches" : > On Mon, 2016-12-12 at 14:41 -0600, Eric Sandeen wrote: >>  On 12/12/16 2:34 PM, Ozgur Karatas wrote: > > [] >>  > Can you tell me the true code style? should use to (* uuid)? >>  > I'm learn to new and I'm newbies :

Re: [PATCH 1/1] Fixed to codestyle

heir own sake is not helpful in > general. > > -Eric I have mentioned above, thank you for all the information. You are helping me and your mentoring in some way. Regards Ozgur Karatas

Re: [PATCH 1/1] Fixed to codestyle

helpful in > general. > > -Eric I have mentioned above, thank you for all the information. You are helping me and your mentoring in some way. Regards Ozgur Karatas

Re: [PATCH 1/1] Fixed to codestyle

12.12.2016, 20:14, "Joe Perches" <j...@perches.com>: > On Mon, 2016-12-12 at 07:49 -0600, Eric Sandeen wrote: >>  On 12/12/16 4:53 AM, Ozgur Karatas wrote: >>  > >>  > Hello, >>  > >>  > I have error to use uuid and I think the

Re: [PATCH 1/1] Fixed to codestyle

12.12.2016, 20:14, "Joe Perches" : > On Mon, 2016-12-12 at 07:49 -0600, Eric Sandeen wrote: >>  On 12/12/16 4:53 AM, Ozgur Karatas wrote: >>  > >>  > Hello, >>  > >>  > I have error to use uuid and I think the functions should be used

Re: [PATCH 1/1] Fixed to codestyle

12.12.2016, 20:35, "Eric Sandeen" <sand...@sandeen.net>: > On 12/12/16 12:14 PM, Joe Perches wrote: >>  On Mon, 2016-12-12 at 07:49 -0600, Eric Sandeen wrote: >>>  On 12/12/16 4:53 AM, Ozgur Karatas wrote: >>>>  Hello, >>>> >>>&

Re: [PATCH 1/1] Fixed to codestyle

12.12.2016, 20:35, "Eric Sandeen" : > On 12/12/16 12:14 PM, Joe Perches wrote: >>  On Mon, 2016-12-12 at 07:49 -0600, Eric Sandeen wrote: >>>  On 12/12/16 4:53 AM, Ozgur Karatas wrote: >>>>  Hello, >>>> >>>>  I have error to use u

Re: [PATCH 1/1] Fixed to BUG_ON to WARN_ON def

12.12.2016, 20:18, "Leon Romanovsky" <l...@kernel.org>: > On Mon, Dec 12, 2016 at 03:04:28PM +0200, Ozgur Karatas wrote: >>  Dear Romanovsky; > > Please avoid top-posting in your replies. > Thanks Dear Leon; thanks for the information., I will pay attention

Re: [PATCH 1/1] Fixed to BUG_ON to WARN_ON def

12.12.2016, 20:18, "Leon Romanovsky" : > On Mon, Dec 12, 2016 at 03:04:28PM +0200, Ozgur Karatas wrote: >>  Dear Romanovsky; > > Please avoid top-posting in your replies. > Thanks Dear Leon; thanks for the information., I will pay attention. >>  I'm tryin

Re: [PATCH 1/1] Fixed to BUG_ON to WARN_ON def

ecause, you will use to "BUG_ON" get a error implicit declaration of functions. sg_set_buf(mem, buf, PAGE_SIZE << order); WARN_ON(mem->offset); Thanks for information and learn to me. Regards, Ozgur Karatas 12.12.2016, 14:39, "Leon Romanovsky" <l.

Re: [PATCH 1/1] Fixed to BUG_ON to WARN_ON def

ecause, you will use to "BUG_ON" get a error implicit declaration of functions. sg_set_buf(mem, buf, PAGE_SIZE << order); WARN_ON(mem->offset); Thanks for information and learn to me. Regards, Ozgur Karatas 12.12.2016, 14:39, "Leon Romanovsky" :

Re: [PATCH 1/1] Fixed to BUG_ON to WARN_ON

Dear Stefan; I'm reading to Documentation/SubmittingPatches and I still apologized for misrepresentations my patches. I will add a next time good commit message and commit subjects. Sorry, Regards Ozgur Karatas 12.12.2016, 13:20, "Stefan Schmidt" <ste...@osg.samsung.com>: &g

Re: [PATCH 1/1] Fixed to BUG_ON to WARN_ON

Dear Stefan; I'm reading to Documentation/SubmittingPatches and I still apologized for misrepresentations my patches. I will add a next time good commit message and commit subjects. Sorry, Regards Ozgur Karatas 12.12.2016, 13:20, "Stefan Schmidt" : > Hello. > > On 12

[PATCH 1/1] Fixed to BUG_ON to WARN_ON def

Hello all, I think should be use to "WARN_ON" and checkpatch script give to error, I fixed and I think should don't use "BUG_ON". Regards, Signed-off-by: Ozgur Karatas <okara...@member.fsf.org> --- drivers/net/ethernet/mellanox/mlx4/icm.c | 4 ++-- diff --git a/dri

[PATCH 1/1] Fixed to BUG_ON to WARN_ON def

Hello all, I think should be use to "WARN_ON" and checkpatch script give to error, I fixed and I think should don't use "BUG_ON". Regards, Signed-off-by: Ozgur Karatas --- drivers/net/ethernet/mellanox/mlx4/icm.c | 4 ++-- diff --git a/drivers/net/ethernet/mellanox/mlx4/

[PATCH 1/1] Fixed to codestyle

Hello, I have error to use uuid and I think the functions should be used when -i'm eye-catching- "(* uuid)". I tested it. Regards, Signed-off-by: Ozgur Karatas <okara...@member.fsf.org> --- diff --git a/fs/xfs/uuid.c b/fs/xfs/uuid.c index b83f76b..cd8bc8e 100644 --- a/fs/xfs

[PATCH 1/1] Fixed to codestyle

Hello, I have error to use uuid and I think the functions should be used when -i'm eye-catching- "(* uuid)". I tested it. Regards, Signed-off-by: Ozgur Karatas --- diff --git a/fs/xfs/uuid.c b/fs/xfs/uuid.c index b83f76b..cd8bc8e 100644 --- a/fs/xfs/uuid.c +++ b/fs/xfs/uuid.c @@ -

[PATCH 1/1] Fixed checkpatch error to mmu.c

Hello all, I tested to mmu.c and I have fixed to some errors. mmu.c:510: ERROR: "(foo*)" should be "(foo *)" Signed-off-by: Ozgur Karatas <okara...@member.fsf.org> --- arch/arm/kvm/mmu.c | 2 +- diff --git a/arch/arm/kvm/mmu.c b/arch/arm/kvm/mm

[PATCH 1/1] Fixed checkpatch error to mmu.c

Hello all, I tested to mmu.c and I have fixed to some errors. mmu.c:510: ERROR: "(foo*)" should be "(foo *)" Signed-off-by: Ozgur Karatas --- arch/arm/kvm/mmu.c | 2 +- diff --git a/arch/arm/kvm/mmu.c b/arch/arm/kvm/mmu.c index a5265ed..a83cf47 10064

[PATCH 1/1] Fixed to checkpatch errors to usbtmc.c

) drivers/usb/class/usbtmc.c:1403: ERROR: space required before the open parenthesis '(' total: 8 errors, 25 warnings, 1558 lines checked Regards, Signed-off-by: Ozgur Karatas <okara...@member.fsf.org> --- drivers/usb/class/usbtmc.c | 12 +--- 1 file changed, 5 insertions(+), 7 del

[PATCH 1/1] Fixed to checkpatch errors to usbtmc.c

) drivers/usb/class/usbtmc.c:1403: ERROR: space required before the open parenthesis '(' total: 8 errors, 25 warnings, 1558 lines checked Regards, Signed-off-by: Ozgur Karatas --- drivers/usb/class/usbtmc.c | 12 +--- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/drivers

[PATCH 130/130] Fixed to checkpatch errors.

Hello, Fixed to checkpatch errors. ERROR: net/wireless/util.c:1787: ERROR: that open brace { should be on the previous line ERROR: net/wireless/util.c:1792: ERROR: that open brace { should be on the previous line Signed-off-by: Ozgur Karatas <okara...@member.fsf.org> --- net/wireless/

[PATCH 130/130] Fixed to checkpatch errors.

Hello, Fixed to checkpatch errors. ERROR: net/wireless/util.c:1787: ERROR: that open brace { should be on the previous line ERROR: net/wireless/util.c:1792: ERROR: that open brace { should be on the previous line Signed-off-by: Ozgur Karatas --- net/wireless/util.c | 10 ++ 1 file

[PATCH] Fixed to checkpatch.pl errors to vlan_dev.c

Hello all, I will solve a checkpatch errors. Signed-off-by: Ozgur Karatas <oz...@member.fsf.org> --- net/8021q/vlan_dev.c | 2 +- diff --git a/net/8021q/vlan_dev.c b/net/8021q/vlan_dev.c index fbfacd5..2edb495 100644 --- a/net/8021q/vlan_dev.c +++ b/net

[PATCH] Fixed to checkpatch.pl errors to vlan_dev.c

Hello all, I will solve a checkpatch errors. Signed-off-by: Ozgur Karatas --- net/8021q/vlan_dev.c | 2 +- diff --git a/net/8021q/vlan_dev.c b/net/8021q/vlan_dev.c index fbfacd5..2edb495 100644 --- a/net/8021q/vlan_dev.c +++ b/net/8021q/vlan_dev.c @@ -738,7

Re: linux-next: unable to fetch the watchdog tree

Hello all, I get a error last week and I couldn't connect from below url: http://www.linux-watchdog.org/cgi-bin/gitweb.cgi?p=linux-watchdog.git;a=summary http://www.linux-watchdog.org/cgi-bin/gitweb.cgi?p=linux-watchdog-next.git;a=summary why do not you use GitHub? Regards, Ozgur

Re: linux-next: unable to fetch the watchdog tree

Hello all, I get a error last week and I couldn't connect from below url: http://www.linux-watchdog.org/cgi-bin/gitweb.cgi?p=linux-watchdog.git;a=summary http://www.linux-watchdog.org/cgi-bin/gitweb.cgi?p=linux-watchdog-next.git;a=summary why do not you use GitHub? Regards, Ozgur

Re: [PATCH] Fixed a functions to rbd.c

Hello all, I fixed to checkpatch.pl error and fixed two errors. static char* obj_op_name(enum obj_operation_type op_type) static bool single_major = false; Signed-off-by: Ozgur Karatas <mued...@goosey.org> ---  drivers/block/rbd.c --- a/drivers/block/rbd.c +++ b/drivers/block/rbd.c @

Re: [PATCH] Fixed a functions to rbd.c

Hello all, I fixed to checkpatch.pl error and fixed two errors. static char* obj_op_name(enum obj_operation_type op_type) static bool single_major = false; Signed-off-by: Ozgur Karatas ---  drivers/block/rbd.c --- a/drivers/block/rbd.c +++ b/drivers/block/rbd.c @@ -2,7 +2,6 @@  /* rbd.c

[PATCH] block: bio-integrity fixed a Oracle Copyright year.

From: Ozgur Karatas <mued...@openldap.org> Fixed a on the github request issue. Signed-off-by: Ozgur Karatas <mued...@goosey.org> --- block/bio-integrity.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/block/bio-integrity.c b/block/bio-integrity.c index 5384

[PATCH] block: bio-integrity fixed a Oracle Copyright year.

From: Ozgur Karatas Fixed a on the github request issue. Signed-off-by: Ozgur Karatas --- block/bio-integrity.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/block/bio-integrity.c b/block/bio-integrity.c index 5384713..775d83e 100644 --- a/block/bio-integrity.c +++ b