[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20160705.202237.33945138215381341.davem@davemloft.net>
Date: Tue, 05 Jul 2016 20:22:37 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: masashi.honma@...il.com
Cc: netdev@...r.kernel.org, netfilter-devel@...r.kernel.org,
linux-wireless@...r.kernel.org, linux-rdma@...r.kernel.org,
linux-audit@...hat.com, cluster-devel@...hat.com,
johannes@...solutions.net, pablo@...filter.org, kaber@...sh.net,
kadlec@...ckhole.kfki.hu, dledford@...hat.com,
sean.hefty@...el.com, hal.rosenstock@...il.com,
paul@...l-moore.com, eparis@...hat.com, zbr@...emap.net,
pshelar@...ira.com, ccaulfie@...hat.com, teigland@...hat.com,
bsingharora@...il.com
Subject: Re: [RFC 0/7] netlink: Add allocation flag to netlink_unicast()
From: Masashi Honma <masashi.honma@...il.com>
Date: Wed, 6 Jul 2016 09:28:29 +0900
> Though currently such a use case was not found, to solve potential
> issue we will add an allocation flag to netlink_unicast().
We don't solve potential issues, we solve real issues.
There is no reason to add the GFP parameter until it is actually
needed.
Powered by blists - more mailing lists