From: David Miller <davem@davemloft.net>
To: dan.carpenter@oracle.com
Cc: isdn@linux-pingi.de, akpm@linux-foundation.org,
keescook@chromium.org, netdev@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [patch] isdn/hisax: hex vs decimal typo in prfeatureind()
Date: Thu, 06 Feb 2014 20:40:07 -0800 (PST) [thread overview]
Message-ID: <20140206.204007.2254644541681384666.davem@davemloft.net> (raw)
In-Reply-To: <20140206080308.GB26661@elgon.mountain>
From: Dan Carpenter <dan.carpenter@oracle.com>
Date: Thu, 6 Feb 2014 11:03:08 +0300
> This is a static checker fix, but judging from the context then I think
> hexidecimal 0x80 is intended here instead of decimal 80.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Applied.
prev parent reply other threads:[~2014-02-07 4:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 8:03 [patch] isdn/hisax: hex vs decimal typo in prfeatureind() Dan Carpenter
2014-02-07 4:40 ` David Miller [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=20140206.204007.2254644541681384666.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=dan.carpenter@oracle.com \
--cc=isdn@linux-pingi.de \
--cc=keescook@chromium.org \
--cc=kernel-janitors@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).