[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [dm-devel] [PATCH v8 01/16] hashtable: introduce a small and naive hashtable
- From: Sasha Levin <levinsasha928 gmail com>
- To: Linus Torvalds <torvalds linux-foundation org>
- Cc: snitzer redhat com, fweisbec gmail com, Trond Myklebust netapp com, bfields fieldses org, paul gortmaker windriver com, dm-devel redhat com, agk redhat com, aarcange redhat com, rds-devel oss oracle com, eric dumazet gmail com, venkat x venkatsubra oracle com, ccaulfie redhat com, mingo elte hu, dev openvswitch org, jesse nicira com, josh joshtriplett org, Steven Rostedt <rostedt goodmis org>, lw cn fujitsu com, mathieu desnoyers efficios com, axboe kernel dk, linux-nfs vger kernel org, edumazet google com, linux-mm kvack org, netdev vger kernel org, linux-kernel vger kernel org, ejt redhat com, ebiederm xmission com, Tejun Heo <tj kernel org>, teigland redhat com, akpm linux-foundation org, davem davemloft net
- Subject: Re: [dm-devel] [PATCH v8 01/16] hashtable: introduce a small and naive hashtable
- Date: Tue, 30 Oct 2012 21:36:21 -0400
Hi Linus,
> But whatever. This series has gotten way too much bike-shedding
> anyway. I think it should just be applied, since it does remove lines
> of code overall. I'd even possibly apply it to mainline, but it seems
> to be against linux-next.
Yup, I switched to using -next because I've been running my
trinity/KVM tools tests with it.
I can either rebase that on top of mainline, or we can ask maintainers
to take it to their own trees if you take only 01/16 into mainline.
What would you prefer?
Thanks,
Sasha
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]