From: Solomon Tan <wjsota@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Coding style operator precedence
Date: Fri, 22 Apr 2022 23:44:40 +0800 [thread overview]
Message-ID: <YmLNaPUPfRi+3DYq@ArchDesktop> (raw)
In-Reply-To: <YmLC2sW7A7gAllhw@kroah.com>
On Fri, Apr 22, 2022 at 04:59:38PM +0200, Greg KH wrote:
> On Fri, Apr 22, 2022 at 10:08:54PM +0800, Solomon Tan wrote:
>
> Make it obvious when people read the code as we do not always remember
> the precedence order. We write code for people first, compilers second.
Understood. Thanks for the advice, Greg. :)
>
> thanks,
>
> greg k-h
Cheers,
Solomon
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2022-04-22 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 14:08 Coding style operator precedence Solomon Tan
2022-04-22 14:59 ` Greg KH
2022-04-22 15:44 ` Solomon Tan [this message]
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=YmLNaPUPfRi+3DYq@ArchDesktop \
--to=wjsota@gmail.com \
--cc=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).