All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@samsung.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Simon Shields <simon@lineageos.org>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andi Shyti <andi@etezian.org>
Subject: Re: [PATCH 5/8] Input: mms114 - use lower case for hexadecimal values
Date: Tue, 30 Jan 2018 08:41:58 +0900	[thread overview]
Message-ID: <20180129234158.GX7575@gangnam.samsung> (raw)
In-Reply-To: <20180129233335.ikqioeetkkvocblm@dtor-ws>

Hi Dmitry,

On Mon, Jan 29, 2018 at 03:33:35PM -0800, Dmitry Torokhov wrote:
> On Tue, Jan 30, 2018 at 08:29:23AM +0900, Andi Shyti wrote:
> > Hi Dmitry,
> > 
> > On Mon, Jan 29, 2018 at 10:56:31AM -0800, Dmitry Torokhov wrote:
> > > On Mon, Jan 29, 2018 at 08:33:20PM +0900, Andi Shyti wrote:
> > > > Signed-off-by: Andi Shyti <andi.shyti@samsung.com>
> > > 
> > > But why?
> > 
> > I think this patch is trivial and the subject itself is quite
> > self-explanatory and the commit message would be a copy-paste of
> > it.
> 
> Here is where we disagree. Why lowercase is preferred over uppercase? Do
> we have this in coding style (and I completely forgot about it)? Or is
> it your preference (mine is too to be fair, but I also do not care
> about churning the code for it)?

I think this is the case where the cultural habits become law, I've
been writing lower case hex values from years and my eyes are so
used to it that it looks wrong to have them written upper case.
Many maintainers reject upper case hex values.

As well as many reject the " ? : " conditional form.

In any case, you're basically right here, at this point I
don't mind if you drop it :)

Thanks,
Andi

  reply	other threads:[~2018-01-29 23:43 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20180129113330epcas2p353fa87845f4a1e21661032f16b11be82@epcas2p3.samsung.com>
2018-01-29 11:33 ` [PATCH 0/8] Melfas MMS114 touchscreen cleanups Andi Shyti
     [not found]   ` <CGME20180129113330epcas2p436609515afc0c89504791908ae49059a@epcas2p4.samsung.com>
2018-01-29 11:33     ` [PATCH 1/8] Input: mms114 - use smbus functions whenever possible Andi Shyti
     [not found]   ` <CGME20180129113331epcas2p1851ecb668e26bee1a09d162b4fe42225@epcas2p1.samsung.com>
2018-01-29 11:33     ` [PATCH 2/8] Input: mms114 - get read of custm i2c read/write functions Andi Shyti
2018-01-29 19:01       ` Dmitry Torokhov
2018-01-29 23:25         ` Andi Shyti
     [not found]   ` <CGME20180129113331epcas2p3fab78689f5f00a3049ae675bbc8dee59@epcas2p3.samsung.com>
2018-01-29 11:33     ` [PATCH 3/8] Input: mms114 - replace mdelay with msleep Andi Shyti
2018-01-29 19:46       ` Dmitry Torokhov
     [not found]   ` <CGME20180129113331epcas2p3bb7bc89558e7219ef257b36fa47dc076@epcas2p3.samsung.com>
2018-01-29 11:33     ` [PATCH 4/8] Input: mms114 - remove unused variable Andi Shyti
2018-01-29 18:43       ` Dmitry Torokhov
2018-01-29 23:27         ` Andi Shyti
     [not found]   ` <CGME20180129113331epcas2p29c39450d723f7d2085fc10a74a74e53c@epcas2p2.samsung.com>
2018-01-29 11:33     ` [PATCH 5/8] Input: mms114 - use lower case for hexadecimal values Andi Shyti
2018-01-29 18:56       ` Dmitry Torokhov
2018-01-29 23:29         ` Andi Shyti
2018-01-29 23:33           ` Dmitry Torokhov
2018-01-29 23:41             ` Andi Shyti [this message]
     [not found]   ` <CGME20180129113331epcas2p130b8bf772fc3124c0a76a0938bcacecc@epcas2p1.samsung.com>
2018-01-29 11:33     ` [PATCH 6/8] Input: mms114 - Use BIT() macro instead of explicit shifting Andi Shyti
2018-01-29 19:46       ` Dmitry Torokhov
     [not found]   ` <CGME20180129113331epcas2p193a0a99f660793fbfcf2ec825fac0e2c@epcas2p1.samsung.com>
2018-01-29 11:33     ` [PATCH 7/8] Input: mms114 - add SPDX identifier Andi Shyti
2018-01-29 19:46       ` Dmitry Torokhov
2018-01-31  6:07         ` Andi Shyti
2018-01-31  7:31           ` Marcus Folkesson
2018-01-31 22:53             ` Dmitry Torokhov
2018-02-01  0:50               ` Andi Shyti
2018-02-01  0:49             ` Andi Shyti
     [not found]   ` <CGME20180129113332epcas1p1edee9b62330e4bcfddf4ab7586843ce4@epcas1p1.samsung.com>
2018-01-29 11:33     ` [PATCH 8/8] Input: mms114 - fix typo in definition Andi Shyti
2018-01-29 19:47       ` Dmitry Torokhov

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=20180129234158.GX7575@gangnam.samsung \
    --to=andi.shyti@samsung.com \
    --cc=andi@etezian.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=simon@lineageos.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: link
Be 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.