Re: clang warning: implicit conversion in intel_ddi.c:1481

not taken "clang warning fixes" for stable kernel updates > in the past, and I doubt I will in the future, unless the tree "builds > clean" with clang. If it eventually gets there, then yes, I will do > that. > > Note, if you are going to email this out to everyone who fixes a warning > message, you might want to reconsider it. That's going to be a lot of > work, and for people who have already fixed an issue, it's kind of > pointless to just remind them of work they have done in the past, right? > > What is the goal of these types of emails? > > thanks, > > greg k-h Ozgur

Re: clang warning: implicit conversion in intel_ddi.c:1481

ing fixes" for stable kernel updates > in the past, and I doubt I will in the future, unless the tree "builds > clean" with clang. If it eventually gets there, then yes, I will do > that. > > Note, if you are going to email this out to everyone who fixes a warning > message, you might want to reconsider it. That's going to be a lot of > work, and for people who have already fixed an issue, it's kind of > pointless to just remind them of work they have done in the past, right? > > What is the goal of these types of emails? > > thanks, > > greg k-h Ozgur

Re: Documentation: rapidio: move sysfs interface to ABI

08.01.2018, 12:03, "Aishwarya Pant" <aishp...@gmail.com>: > On Mon, Jan 08, 2018 at 11:58:12AM +0300, Ozgur wrote: >>  08.01.2018, 11:38, "Aishwarya Pant" <aishp...@gmail.com>: >>  > Hi >> >>  Hello, >> >>  > In Documen

Re: Documentation: rapidio: move sysfs interface to ABI

08.01.2018, 12:03, "Aishwarya Pant" : > On Mon, Jan 08, 2018 at 11:58:12AM +0300, Ozgur wrote: >>  08.01.2018, 11:38, "Aishwarya Pant" : >>  > Hi >> >>  Hello, >> >>  > In Documentation/rapidio/sysfs.txt, there is a description o

Re: Documentation: rapidio: move sysfs interface to ABI

Please you make the change you want after send your patch it diff format, right? I think a better decision can be made. > I am doing this in an exercise to move sysfs ABI interfaces (which are > documented) to their right place i.e. in Documentation/ABI along with the > rest. > > Aishwarya Regards Ozgur

Re: Documentation: rapidio: move sysfs interface to ABI

you want after send your patch it diff format, right? I think a better decision can be made. > I am doing this in an exercise to move sysfs ABI interfaces (which are > documented) to their right place i.e. in Documentation/ABI along with the > rest. > > Aishwarya Regards Ozgur

Re: Proposal: CAP_PAYLOAD to reduce Meltdown and Spectre mitigation costs

but currently, impossible to do kernel-level operations. All process start on the browser level and Spectre not read kernel memory, right? Ozgur > As a result, you probably want Spectre mitigations to be enabled in a > root process --- which means capabilities aren't the right answer. > > Regards, > > - Ted

Re: Proposal: CAP_PAYLOAD to reduce Meltdown and Spectre mitigation costs

ssible to do kernel-level operations. All process start on the browser level and Spectre not read kernel memory, right? Ozgur > As a result, you probably want Spectre mitigations to be enabled in a > root process --- which means capabilities aren't the right answer. > > Regards, > > - Ted

[PATCH] Documentation: Fix 00-INDEX file

Updated 00-INDEX file and added non-directories, add descriptions. Signed-off-by: Ozgur Karatas <oz...@goosey.org> --- Documentation/00-INDEX | 15 ++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/Documentation/00-INDEX b/Documentation/00-INDEX index 3bec49

[PATCH] Documentation: Fix 00-INDEX file

Updated 00-INDEX file and added non-directories, add descriptions. Signed-off-by: Ozgur Karatas --- Documentation/00-INDEX | 15 ++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/Documentation/00-INDEX b/Documentation/00-INDEX index 3bec49c33bbb..88eba10037c3

Re: LKML admins (syzbot emails are not delivered)

04.01.2018, 18:31, "David Miller" <da...@davemloft.net>: > From: Ozgur <oz...@goosey.org> > Date: Thu, 04 Jan 2018 12:56:56 +0300 Dvyukov, I think you will set a bot sensitive and syzbot send e-mail that it doesn't disturb list members :) David is sometimes ner

Re: LKML admins (syzbot emails are not delivered)

04.01.2018, 18:31, "David Miller" : > From: Ozgur > Date: Thu, 04 Jan 2018 12:56:56 +0300 Dvyukov, I think you will set a bot sensitive and syzbot send e-mail that it doesn't disturb list members :) David is sometimes nervous. Ozgur >>  autoanswer is just a

Re: LKML admins (syzbot emails are not delivered)

;  I failed to find any admin email referenced anywhere. > > Look a bit harder, like at the bottom of this page: > http://vger.kernel.org/majordomo-info.html > > :) > >>  On a related note, I also tried to contact bugzilla admins via >>  rt.linuxfoundation.org.

Re: LKML admins (syzbot emails are not delivered)

k a bit harder, like at the bottom of this page: > http://vger.kernel.org/majordomo-info.html > > :) > >>  On a related note, I also tried to contact bugzilla admins via >>  rt.linuxfoundation.org. But there is complete silence. Does anybody >>  know how to get

Re: KASAN: slab-out-of-bounds Write in tcp_v6_syn_recv_sock

60 [inline] >>   check_memory_region+0x137/0x190 mm/kasan/kasan.c:267 >>   memcpy+0x37/0x50 mm/kasan/kasan.c:303 >>   memcpy include/linux/string.h:344 [inline] >>   tcp_v6_syn_recv_sock+0x628/0x23a0 net/ipv6/tcp_ipv6.c:1144 > > tls_init() changes sk->

Re: KASAN: slab-out-of-bounds Write in tcp_v6_syn_recv_sock

7/0x50 mm/kasan/kasan.c:303 >>   memcpy include/linux/string.h:344 [inline] >>   tcp_v6_syn_recv_sock+0x628/0x23a0 net/ipv6/tcp_ipv6.c:1144 > > tls_init() changes sk->sk_prot from IPv6 to IPv4, which leads > to this bug. I guess IPv6 is not supported for TLS? If so, need > a

Re: [PATCH 2/2] Staging: most: aim-sound: sound.c: removed unnecessary parentheses

annel->iface == iface && channel->id == channel_id) >  return channel; >  } Hello, I think this patch is not good, the code will not work. Please should understand in && operator and () why used with C. Ozgur > -- > 2.15.1

Re: [PATCH 2/2] Staging: most: aim-sound: sound.c: removed unnecessary parentheses

return channel; >  } Hello, I think this patch is not good, the code will not work. Please should understand in && operator and () why used with C. Ozgur > -- > 2.15.1

Re: [PATCH 0/2] Staging: most: aim-sound: sound.c: coding style

29.12.2017, 02:07, "Philippe Loctaux" <loctauxphili...@gmail.com>: > Fixes checkpatch coding style issues. Hello, how can i see is changed/patched code lines? Ozgur > Philippe Loctaux (2): >   Staging: most: aim-sound: sound.c: fixed an alignment issue >   Stagi

Re: [PATCH 0/2] Staging: most: aim-sound: sound.c: coding style

29.12.2017, 02:07, "Philippe Loctaux" : > Fixes checkpatch coding style issues. Hello, how can i see is changed/patched code lines? Ozgur > Philippe Loctaux (2): >   Staging: most: aim-sound: sound.c: fixed an alignment issue >   Staging: most: aim-sound: sound.

Re: niced tasks on SMT system

y on N900 via flightgear? :) >>  I have two N900 and one run gentoo. > > No, no flightgear on N900. It was preparing kernels for my N900 that > interfered with flying. I would like to be involved in the team and share the job. firstly I will read the project documents. > BTW

Re: niced tasks on SMT system

htgear? :) >>  I have two N900 and one run gentoo. > > No, no flightgear on N900. It was preparing kernels for my N900 that > interfered with flying. I would like to be involved in the team and share the job. firstly I will read the project documents. > BTW there's lot of fun to

Re: niced tasks on SMT system

28.12.2017, 21:54, "Pavel Machek" : > Hi! > >>  > Ok, so I'm compiling, and I'd like to run a flight simulator. >>  > >>  > Flightgear normally does 20fps on my system... kinda low but playable. >>  > >>  > I have reniced make -j 5 fo kernel running. Scheduler gives 100% of >>  >

Re: niced tasks on SMT system

28.12.2017, 21:54, "Pavel Machek" : > Hi! > >>  > Ok, so I'm compiling, and I'd like to run a flight simulator. >>  > >>  > Flightgear normally does 20fps on my system... kinda low but playable. >>  > >>  > I have reniced make -j 5 fo kernel running. Scheduler gives 100% of >>  > one of CPUs to

Re: rtc: sysfs: move sysfs interface to Documentation/ABI

28.12.2017, 18:00, "Aishwarya Pant" <aishp...@gmail.com>: > On Thu, Dec 28, 2017 at 05:23:33PM +0300, Ozgur wrote: >>  28.12.2017, 17:22, "Ozgur" <okara...@yandex.com>: >>  > 28.12.2017, 16:31, "Aishwarya Pant" <aishp...@gmail.com&

Re: rtc: sysfs: move sysfs interface to Documentation/ABI

28.12.2017, 18:00, "Aishwarya Pant" : > On Thu, Dec 28, 2017 at 05:23:33PM +0300, Ozgur wrote: >>  28.12.2017, 17:22, "Ozgur" : >>  > 28.12.2017, 16:31, "Aishwarya Pant" : >>  >>  Hi >> >>   Hello, >> >>  >&

Re: rtc: sysfs: move sysfs interface to Documentation/ABI

28.12.2017, 17:22, "Ozgur" <okara...@yandex.com>: > 28.12.2017, 16:31, "Aishwarya Pant" <aishp...@gmail.com>: >>  Hi Hello, >>  In Documentation/rtc.txt, there is a description of the sysfs >>  interface which could be moved to Do

Re: rtc: sysfs: move sysfs interface to Documentation/ABI

28.12.2017, 17:22, "Ozgur" : > 28.12.2017, 16:31, "Aishwarya Pant" : >>  Hi Hello, >>  In Documentation/rtc.txt, there is a description of the sysfs >>  interface which could be moved to Documentation/ABI. >> >>  Would such a change be u

Re: [RFC] syzbot process

28.12.2017, 15:30, "Dmitry Vyukov" <dvyu...@google.com>: > On Thu, Dec 28, 2017 at 1:26 PM, Ozgur <oz...@goosey.org> wrote: > >>>>   and I think syzbot use to .txt file attached. >>>>   .txt is not good. >>> >>>  Why are not

Re: [RFC] syzbot process

28.12.2017, 15:30, "Dmitry Vyukov" : > On Thu, Dec 28, 2017 at 1:26 PM, Ozgur wrote: > >>>>   and I think syzbot use to .txt file attached. >>>>   .txt is not good. >>> >>>  Why are not .txt attachments good? What do you propose to use?

Re: [RFC] syzbot process

28.12.2017, 14:45, "Dmitry Vyukov" <dvyu...@google.com>: > On Thu, Dec 28, 2017 at 11:51 AM, Ozgur <oz...@goosey.org> wrote: >>  28.12.2017, 13:41, "Dmitry Vyukov" <dvyu...@google.com>: >>>  On Fri, Dec 22, 2017 at 4:32 AM, Eric Biggers

Re: [RFC] syzbot process

28.12.2017, 14:45, "Dmitry Vyukov" : > On Thu, Dec 28, 2017 at 11:51 AM, Ozgur wrote: >>  28.12.2017, 13:41, "Dmitry Vyukov" : >>>  On Fri, Dec 22, 2017 at 4:32 AM, Eric Biggers wrote: >>>>   On Thu, Dec 21, 2017 at 01:52:40PM +01

Re: [RFC] syzbot process

le. The good news is that information is already accumulating > and we can do pings, etc. Hello Dmitry, I think not useful to be a GUI, for example it can be console based ui we can conenct and get information and fixed patches. So syzbot is perfectly, I founded a patc last time :) https://

Re: [RFC] syzbot process

s, etc. Hello Dmitry, I think not useful to be a GUI, for example it can be console based ui we can conenct and get information and fixed patches. So syzbot is perfectly, I founded a patc last time :) https://09738734946362323617.googlegroups.com/attach/3c6ef7059f77c/patch.txt?part=0.2=1=ANaJVr

Re: 4.14.9 boot error (regression), 4.14.8 is fine

g copy /boot directory? $ copy /boot/config* .config $ make Have you try this default .config? Everything is good? >>  FWIW I'm surprised a little bit about having a new kernel option in a LTS >> release. > > It's just a renamed kernel config option, right? > and a different default setting (UNWINDER_ORC became the new default). > > -- > ~Randy Ozgur

Re: 4.14.9 boot error (regression), 4.14.8 is fine

copy /boot/config* .config $ make Have you try this default .config? Everything is good? >>  FWIW I'm surprised a little bit about having a new kernel option in a LTS >> release. > > It's just a renamed kernel config option, right? > and a different default setting (UNWINDER_ORC became the new default). > > -- > ~Randy Ozgur

Re: 4.14.9 boot error (regression), 4.14.8 is fine

new kernel option in a LTS > release. > > -- > Toralf > PGP C4EACDDE 0076E94E Ozgur

Re: 4.14.9 boot error (regression), 4.14.8 is fine

se. > > -- > Toralf > PGP C4EACDDE 0076E94E Ozgur

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

eration first and fallback to get format if not > - * implemented. > + /* Try the get selection operation first and fallback to get format if > + * not implemented. >   */ There is no change here, it opens with comment /* and closes with */. Please read submittting patch document. Regards, >  sdsel.pad = pad; >  ret = v4l2_subdev_call(subdev, pad, get_selection, NULL, ); > -- > 2.7.4 ~Ozgur

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

mat if not > - * implemented. > + /* Try the get selection operation first and fallback to get format if > + * not implemented. >   */ There is no change here, it opens with comment /* and closes with */. Please read submittting patch document. Regards, >  sdsel.pad = pad; >  ret = v4l2_subdev_call(subdev, pad, get_selection, NULL, ); > -- > 2.7.4 ~Ozgur

Re: lkml.org issues

nd forging in-reply-to headers. previously lkml hve to FAQ please contact to tux.org Regards, Ozgur

Re: lkml.org issues

usly lkml hve to FAQ please contact to tux.org Regards, Ozgur

Re: Question regarding power button of Dell XPS13

visible indication of the suspend state (ie the > traditional slowly pulsing LED showing that it's all nice and > suspended). But that seems to be intentional, if stupid. I think it's > the only real beef I have with the XPS13. > >    Linus Regards, Ozgur

Re: Question regarding power button of Dell XPS13

t; traditional slowly pulsing LED showing that it's all nice and > suspended). But that seems to be intentional, if stupid. I think it's > the only real beef I have with the XPS13. > >    Linus Regards, Ozgur

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

  1   2   >