From: David Miller <davem@davemloft.net>
To: dingtianhong@huawei.com
Cc: dan.carpenter@oracle.com, zhangfei.gao@linaro.org, arnd@arndb.de,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch net-next] hisilicon: add some missing curly braces
Date: Wed, 28 Jan 2015 23:07:05 -0800 (PST) [thread overview]
Message-ID: <20150128.230705.155343650325772037.davem@davemloft.net> (raw)
In-Reply-To: <54C99FFB.2080207@huawei.com>
From: Ding Tianhong <dingtianhong@huawei.com>
Date: Thu, 29 Jan 2015 10:50:35 +0800
> On 2015/1/29 2:58, Dan Carpenter wrote:
>> The if block was supposed to have curly braces. In the current code we
>> complain about dropped rx packets when we shouldn't.
>>
>> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>>
> Acked-by: Ding Tianhong <dingtianhong@huawei.com>
Applied, thanks everyone.
prev parent reply other threads:[~2015-01-29 7:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 18:58 [patch net-next] hisilicon: add some missing curly braces Dan Carpenter
2015-01-29 2:50 ` Ding Tianhong
2015-01-29 7:07 ` 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=20150128.230705.155343650325772037.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=arnd@arndb.de \
--cc=dan.carpenter@oracle.com \
--cc=dingtianhong@huawei.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=zhangfei.gao@linaro.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).