From: Joe Perches <joe@perches.com>
To: Himanshu Jha <himanshujha199640@gmail.com>, kvalo@codeaurora.org
Cc: ath9k-devel@qca.qualcomm.com, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ath9k: remove cast to void pointer
Date: Thu, 31 Aug 2017 14:29:00 -0700 [thread overview]
Message-ID: <1504214940.2786.47.camel@perches.com> (raw)
In-Reply-To: <1504184863-9732-1-git-send-email-himanshujha199640@gmail.com>
On Thu, 2017-08-31 at 18:37 +0530, Himanshu Jha wrote:
> casting to void pointer from any pointer type and vice-versa is done
> implicitly and therefore casting is not needed in such a case.
You said you were going to remember to mention the tool
and script that did this.
prev parent reply other threads:[~2017-08-31 21:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 13:07 [PATCH] ath9k: remove cast to void pointer Himanshu Jha
2017-08-31 21:29 ` Joe Perches [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=1504214940.2786.47.camel@perches.com \
--to=joe@perches.com \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=himanshujha199640@gmail.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.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).