From: David Miller <davem@davemloft.net>
To: huangdaode@hisilicon.com
Cc: yisen.zhuang@huawei.com, yankejian@huawei.com,
liguozhu@hisilicon.com, salil.mehta@huawei.com,
geliangtang@163.com, lipeng321@huawei.com,
andriy.shevchenko@linux.intel.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Kenneth-Lee-2012@foxmail.com
Subject: Re: [PATCH net-next] net: hns: bug fix about hisilicon TSO BD mode
Date: Mon, 18 Jan 2016 11:55:24 -0500 (EST) [thread overview]
Message-ID: <20160118.115524.1656097226798937868.davem@davemloft.net> (raw)
In-Reply-To: <1453109056-161865-1-git-send-email-huangdaode@hisilicon.com>
From: Daode Huang <huangdaode@hisilicon.com>
Date: Mon, 18 Jan 2016 17:24:16 +0800
> The current upstreaming code fails to set the tso_mode register
> when initilizes, when processes large size packets, the default 4 bd is
> not enough, so this patch initilizes it and set the default value to 8 bds
>
> Signed-off-by: Daode Huang <huangdaode@hisilicon.com>
Your insistance of continually using "net-next" in your subject lines
shows you have no idea what GIT trees are active and in what trees
development and bug fixing is actually occurring in.
The 'net' tree is the only tree active now and your driver has been in
there for over a week.
And this is the place where all appropriate bug fixes go.
Therefore if your code is present in the 'net' tree and you are fixing
things in that codebase, then that is the tree you target.
I've been silently applying your patches there instead of net-next,
but I'm not going to do it any more and I will just reject patches not
submitted properly from this point forward.
Thanks.
next prev parent reply other threads:[~2016-01-18 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 9:24 [PATCH net-next] net: hns: bug fix about hisilicon TSO BD mode Daode Huang
2016-01-18 9:36 ` Andy Shevchenko
2016-01-18 9:56 ` huangdaode
2016-01-18 16:55 ` David Miller [this message]
2016-01-19 1:51 ` huangdaode
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=20160118.115524.1656097226798937868.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Kenneth-Lee-2012@foxmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=geliangtang@163.com \
--cc=huangdaode@hisilicon.com \
--cc=liguozhu@hisilicon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lipeng321@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=salil.mehta@huawei.com \
--cc=yankejian@huawei.com \
--cc=yisen.zhuang@huawei.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).