From: Boris Brezillon <boris.brezillon-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org> To: Mason <slash.tmp-GANU6spQydw@public.gmane.org> Cc: Marc Gonzalez <marc_gonzalez-y1yR0Z3OICC7zZZRDBGcUA@public.gmane.org>, linux-mtd <linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>, Richard Weinberger <richard-/L3Ra7n9ekc@public.gmane.org>, DT <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>, Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>, Sebastian Frias <sf84-QFKgK+z4sOrR7s880joybQ@public.gmane.org> Subject: Re: [PATCH v8] mtd: nand: add tango NAND flash controller support Date: Fri, 11 Nov 2016 18:14:51 +0100 [thread overview] Message-ID: <20161111181451.00b5ebfa@bbrezillon> (raw) In-Reply-To: <5825EB70.4070406-GANU6spQydw@public.gmane.org> Hi Marc, On Fri, 11 Nov 2016 17:01:52 +0100 Mason <slash.tmp-GANU6spQydw@public.gmane.org> wrote: > On 06/11/2016 23:58, Boris Brezillon wrote: > > > Applied after fixing a few coding style issues to make checkpatch happy. > > First of all, I want to thank you for all the help you provided > along the way. > > I have to admit that I'm a bit frustrated by some of the changes you made > to the patch. > > Specifically, changing > > from: if (ptr_expr == NULL) > to: if (!ptr_expr) > > I dislike the second form, because it "hides" what is being tested. > I've even seen people use !count to mean count == 0, and I find that > very unintuitive. I just fixed checkpatch --strict complaints. > > I also have a hard time discerning a '!' after a '(' > > > The other change is the chip->options initialization. I thought > you said on IRC I could keep my preferred formatting. Hm, I said that you could use one flag per line, and I kept that. I just moved the 'or' operator which is, IMO, better placed at the end of the line, and I aligned the following flags with the first one to make checkpatch happy. > > > In the end, these are tiny issues in the grand scheme of things, > but it was important for me to point them out. Some maintainers don't care much, but I think enforcing these rules is what brings consistency in the kernel code, that's why I try to make checkpatch happy when I submit new code and ask developers to do so when they submit code to the NAND subsystem. I know you often disagree with the Linux coding style rules, but you're a contributor to this project, and as such, you should commit to the defined rules (and this includes the coding style rules). And it appears that, instead of complying to these rules when you're asked to, you keep arguing endlessly that your own coding style is better. You'd better spend time on things that really matters. Note that most of the time, when the contribution is looking good, but a few coding style issue remain, I'm fixing those issues myself because I know how annoying it can be to ask someone to post a new version to fix such minor things. But since you complain about that, next time I'll ask you to make "checkpatch --strict" happy before accepting your patch. On a side note, as I already told you privately, you seem to be a smart guy (the evolution of the tango NAND driver shows that you're able to understand how things work, and take comments/reviews into account). But you have the bad habit of consistently arguing when you're asked to change something (and especially on minor things that are easy to fix). This is really the kind of behavior that can upset maintainers (me included). So please, try to work on that. Regards, Boris -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Boris Brezillon <boris.brezillon@free-electrons.com> To: Mason <slash.tmp@free.fr> Cc: Marc Gonzalez <marc_gonzalez@sigmadesigns.com>, linux-mtd <linux-mtd@lists.infradead.org>, Richard Weinberger <richard@nod.at>, DT <devicetree@vger.kernel.org>, Rob Herring <robh+dt@kernel.org>, Mark Rutland <mark.rutland@arm.com>, Sebastian Frias <sf84@laposte.net> Subject: Re: [PATCH v8] mtd: nand: add tango NAND flash controller support Date: Fri, 11 Nov 2016 18:14:51 +0100 [thread overview] Message-ID: <20161111181451.00b5ebfa@bbrezillon> (raw) In-Reply-To: <5825EB70.4070406@free.fr> Hi Marc, On Fri, 11 Nov 2016 17:01:52 +0100 Mason <slash.tmp@free.fr> wrote: > On 06/11/2016 23:58, Boris Brezillon wrote: > > > Applied after fixing a few coding style issues to make checkpatch happy. > > First of all, I want to thank you for all the help you provided > along the way. > > I have to admit that I'm a bit frustrated by some of the changes you made > to the patch. > > Specifically, changing > > from: if (ptr_expr == NULL) > to: if (!ptr_expr) > > I dislike the second form, because it "hides" what is being tested. > I've even seen people use !count to mean count == 0, and I find that > very unintuitive. I just fixed checkpatch --strict complaints. > > I also have a hard time discerning a '!' after a '(' > > > The other change is the chip->options initialization. I thought > you said on IRC I could keep my preferred formatting. Hm, I said that you could use one flag per line, and I kept that. I just moved the 'or' operator which is, IMO, better placed at the end of the line, and I aligned the following flags with the first one to make checkpatch happy. > > > In the end, these are tiny issues in the grand scheme of things, > but it was important for me to point them out. Some maintainers don't care much, but I think enforcing these rules is what brings consistency in the kernel code, that's why I try to make checkpatch happy when I submit new code and ask developers to do so when they submit code to the NAND subsystem. I know you often disagree with the Linux coding style rules, but you're a contributor to this project, and as such, you should commit to the defined rules (and this includes the coding style rules). And it appears that, instead of complying to these rules when you're asked to, you keep arguing endlessly that your own coding style is better. You'd better spend time on things that really matters. Note that most of the time, when the contribution is looking good, but a few coding style issue remain, I'm fixing those issues myself because I know how annoying it can be to ask someone to post a new version to fix such minor things. But since you complain about that, next time I'll ask you to make "checkpatch --strict" happy before accepting your patch. On a side note, as I already told you privately, you seem to be a smart guy (the evolution of the tango NAND driver shows that you're able to understand how things work, and take comments/reviews into account). But you have the bad habit of consistently arguing when you're asked to change something (and especially on minor things that are easy to fix). This is really the kind of behavior that can upset maintainers (me included). So please, try to work on that. Regards, Boris
next prev parent reply other threads:[~2016-11-11 17:14 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-10-25 13:14 [PATCH v7 0/2] tango NFC support + bindings doc Marc Gonzalez 2016-10-25 13:14 ` Marc Gonzalez 2016-10-25 13:15 ` [PATCH v7 1/2] mtd: nand: add tango NFC dt " Marc Gonzalez 2016-10-25 13:15 ` Marc Gonzalez [not found] ` <580F5B06.6030608-y1yR0Z3OICC7zZZRDBGcUA@public.gmane.org> 2016-10-25 13:25 ` Boris Brezillon 2016-10-25 13:25 ` Boris Brezillon 2016-10-31 2:45 ` Rob Herring 2016-10-31 2:45 ` Rob Herring 2016-11-06 22:57 ` Boris Brezillon 2016-11-06 22:57 ` Boris Brezillon 2016-11-07 9:18 ` Arnd Bergmann 2016-11-07 9:18 ` Arnd Bergmann 2016-11-07 9:26 ` Marc Gonzalez 2016-11-07 9:26 ` Marc Gonzalez [not found] ` <582048D8.3000000-y1yR0Z3OICC7zZZRDBGcUA@public.gmane.org> 2016-11-07 9:40 ` Boris Brezillon 2016-11-07 9:40 ` Boris Brezillon 2016-12-16 10:56 ` Marc Gonzalez 2016-12-16 10:56 ` Marc Gonzalez 2016-12-16 13:26 ` Marc Gonzalez 2016-12-16 13:26 ` Marc Gonzalez [not found] ` <ee9efd0a-59f5-8c21-0cad-40ca30e3a3e7-y1yR0Z3OICC7zZZRDBGcUA@public.gmane.org> 2016-12-16 13:33 ` Mark Rutland 2016-12-16 13:33 ` Mark Rutland [not found] ` <d3cbfda6-23bf-4ad1-b1ce-c179b765272f-y1yR0Z3OICC7zZZRDBGcUA@public.gmane.org> 2016-12-19 12:59 ` Boris Brezillon 2016-12-19 12:59 ` Boris Brezillon 2016-10-25 13:16 ` [PATCH v7 2/2] mtd: nand: add tango NAND flash controller support Marc Gonzalez 2016-10-25 13:16 ` Marc Gonzalez [not found] ` <580F5B37.5090100-y1yR0Z3OICC7zZZRDBGcUA@public.gmane.org> 2016-10-25 16:10 ` [PATCH v8] " Marc Gonzalez 2016-10-25 16:10 ` Marc Gonzalez [not found] ` <580F8407.5070706-y1yR0Z3OICC7zZZRDBGcUA@public.gmane.org> 2016-11-06 22:58 ` Boris Brezillon 2016-11-06 22:58 ` Boris Brezillon 2016-11-11 16:01 ` Mason 2016-11-11 16:01 ` Mason [not found] ` <5825EB70.4070406-GANU6spQydw@public.gmane.org> 2016-11-11 17:14 ` Boris Brezillon [this message] 2016-11-11 17:14 ` Boris Brezillon 2016-12-01 1:44 ` Brian Norris 2016-12-01 1:44 ` Brian Norris
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20161111181451.00b5ebfa@bbrezillon \ --to=boris.brezillon-wi1+55scjutkeb57/3fjtnbpr1lh4cv8@public.gmane.org \ --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \ --cc=marc_gonzalez-y1yR0Z3OICC7zZZRDBGcUA@public.gmane.org \ --cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \ --cc=richard-/L3Ra7n9ekc@public.gmane.org \ --cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \ --cc=sf84-QFKgK+z4sOrR7s880joybQ@public.gmane.org \ --cc=slash.tmp-GANU6spQydw@public.gmane.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.