2016-06-08 19:02, Jerin Jacob: > On Wed, Jun 08, 2016 at 02:22:55PM +0100, Bruce Richardson wrote: > > On Wed, Jun 08, 2016 at 06:13:21PM +0530, Jerin Jacob wrote: > > > On Wed, Jun 08, 2016 at 01:30:28PM +0100, Ferruh Yigit wrote: > > > > On 6/7/2016 5:40 PM, Jerin Jacob wrote: > > > > Hi Jerin, > > > > > > > > In patch subject, as tag, other drivers are using only driver name, and > > > > Intel drivers also has "driver/base", since base code has some special > > > > case. For thunderx, what do you think about keeping subject as: > > > > "thunderx: ...." > > > > > > > > > > Hi Ferruh, > > > > > > We may add crypto or other builtin ThunderX HW accelerated block drivers > > > in future to DPDK. > > > So that is the reason why I thought of keeping the subject as > > > thunderx/nicvf. > > > If you don't have any objection then I would like to keep it as > > > thunderx/nicvf or just nicvf. > > > > Are you upstreaming kernel modules for this device? If so, what is the Linux > > kernel module-name for this device going to be, as perhaps that can help us > > here? > > Yes, Kernel module has been upstreamed. > the commit log in linux kernel is "net: thunderx: ......."
If you want to modify the conventions, we just need to agree on a patch modifying the guidelines. We can think about the proposal of Ferruh to use net/ and crypto/ prefixes. The most important is to have something short and easy to parse when quick browsing the git history.
