From: Dan Carpenter <dan.carpenter@oracle.com>
To: Karthik Nishanth <nishanthkarthik@live.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Larry.Finger@lwfinger.net" <Larry.Finger@lwfinger.net>
Subject: Re: [PATCH] Fix clang warning -Wpointer-bool-conversion by removing unnecessary check in regd.c
Date: Sat, 22 Sep 2018 15:44:32 +0300 [thread overview]
Message-ID: <20180922124432.tcykwwisip3rl7ll@mwanda> (raw)
In-Reply-To: <BN6PR17MB099677ADA332476DC575F2EDCA120@BN6PR17MB0996.namprd17.prod.outlook.com>
The subject needs a subsystem prefix. It's also slightly long.
[PATCH] Staging: rtlwifi: remove unnecessary NULL check
regards,
dan carpenter
next prev parent reply other threads:[~2018-09-22 12:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 17:26 [PATCH] Fix clang warning -Wpointer-bool-conversion by removing unnecessary check in regd.c Karthik Nishanth
2018-09-22 12:44 ` Dan Carpenter [this message]
2018-09-22 13:40 ` Karthik Nishanth
2018-09-22 14:04 ` Dan Carpenter
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=20180922124432.tcykwwisip3rl7ll@mwanda \
--to=dan.carpenter@oracle.com \
--cc=Larry.Finger@lwfinger.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nishanthkarthik@live.com \
/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).