From: Greg KH <greg@kroah.com>
To: Anuz Pratap Singh Tomar <chambilkethakur@gmail.com>
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: spaces after typecasts?
Date: Wed, 19 Feb 2020 19:56:12 +0100 [thread overview]
Message-ID: <20200219185612.GA2868598@kroah.com> (raw)
In-Reply-To: <CAJnfX5svx7Sq1KQ0O3-3eDWnfn4iar=teupOyY0+_i-Gxyhpvg@mail.gmail.com>
On Wed, Feb 19, 2020 at 01:27:45PM +0000, Anuz Pratap Singh Tomar wrote:
> Hi all,
> I don't see anything in coding guidelines about spaces after typecasts i.e.
> (char *)x; vs (char *) x;.
> Typecasts are considered keywords or not? given you could typecast to a non
> C keyword as well?
(char *)x;
checkpatch.pl will catch this for you, try it and see :)
thanks,
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2020-02-19 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 13:27 spaces after typecasts? Anuz Pratap Singh Tomar
2020-02-19 18:56 ` Greg KH [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=20200219185612.GA2868598@kroah.com \
--to=greg@kroah.com \
--cc=chambilkethakur@gmail.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).