From: Johannes Berg <johannes@sipsolutions.net>
To: Rahul Jain <rahul.jain@samsung.com>
Cc: linux-wireless@vger.kernel.org, Amit Khatri <amit.khatri@samsung.com>
Subject: Re: [PATCH 2/2]iw: UNSPECIFIED_CHAR_IN_COND : Fix
Date: Thu, 26 Nov 2015 10:36:35 +0100 [thread overview]
Message-ID: <1448530595.2167.0.camel@sipsolutions.net> (raw)
In-Reply-To: <1448529080-710-1-git-send-email-rahul.jain@samsung.com>
Err, the other patch I can kinda understand - but this one? What kind
of static checker is giving that warning, and what does it really mean?
please describe in the commit log... actually I'm not sure why I should
apply this at all even, if there's a problem just make the function
prototype "unsigned char"?
johannes
prev parent reply other threads:[~2015-11-26 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 9:11 [PATCH 2/2]iw: UNSPECIFIED_CHAR_IN_COND : Fix Rahul Jain
2015-11-26 9:36 ` Johannes Berg [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=1448530595.2167.0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=amit.khatri@samsung.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rahul.jain@samsung.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 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.