From: Ding Tianhong <dingtianhong@huawei.com>
To: Eric Dumazet <eric.dumazet@gmail.com>,
Veaceslav Falico <vfalico@redhat.com>
Cc: Jay Vosburgh <fubar@us.ibm.com>,
Eric Dumazet <edumazet@google.com>,
"David S. Miller" <davem@davemloft.net>,
Netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] bonding: move the netdev_add_tso_features() to bonding module
Date: Sun, 19 Jan 2014 13:34:21 +0800 [thread overview]
Message-ID: <52DB63DD.50203@huawei.com> (raw)
In-Reply-To: <1390064923.31367.531.camel@edumazet-glaptop2.roam.corp.google.com>
On 2014/1/19 1:08, Eric Dumazet wrote:
> On Sat, 2014-01-18 at 12:48 +0100, Veaceslav Falico wrote:
>> On Sat, Jan 18, 2014 at 04:31:33PM +0800, Ding Tianhong wrote:
>>> The function netdev_add_tso_features() was only be used for bonding,
>>> so no need to export it in netdevice.h, move it to bonding module.
>>
>> Eric added it for a reason - like, other drivers might use it. Do you know
>> if team, bridge, vlan etc. might use it?
>
> A helper can be used once, this is fine. A car can have 4 seats, and can
> even be used with no passenger.
>
> I am quite bored by patches that break clean layering for wrong reasons.
>
>
> static inline netdev_features_t netdev_add_tso_features(netdev_features_t features,
> netdev_features_t mask)
> {
> return netdev_increment_features(features, NETIF_F_ALL_TSO, mask);
> }
>
> There is _nothing_ in this helper that implies it should be private to bonding.
>
>
yep, it is look so fool that my patch said, thanks for reminding me.
>
>
>
prev parent reply other threads:[~2014-01-19 5:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-18 8:31 [PATCH net-next] bonding: move the netdev_add_tso_features() to bonding module Ding Tianhong
2014-01-18 11:48 ` Veaceslav Falico
2014-01-18 17:08 ` Eric Dumazet
2014-01-19 5:34 ` Ding Tianhong [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=52DB63DD.50203@huawei.com \
--to=dingtianhong@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=fubar@us.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=vfalico@redhat.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.