Re: stalled again

2015-12-03 Thread Christoph Hellwig
Hi Doug, not having any maintainer available for an extended time is a problem, and we actually had long discussions about that at kernel summit, with a clear hint with a cluebat from Linus that he'd prefer maintainer teams. So I'd really love to know who was so ead set aginst them. I personally

Re: stalled again

2015-12-02 Thread Doug Ledford
On 12/02/2015 01:42 PM, Jason Gunthorpe wrote: > On Wed, Dec 02, 2015 at 04:29:27AM -0800, Christoph Hellwig wrote: >> Maybe we need more co-maintainers if the two current maintainers can't >> handle the workload? > > Doug is the only maintainer. The idea of co-maintainers was rejected > by some p

Re: stalled again

2015-12-02 Thread Jason Gunthorpe
On Wed, Dec 02, 2015 at 04:29:27AM -0800, Christoph Hellwig wrote: > Maybe we need more co-maintainers if the two current maintainers can't > handle the workload? Doug is the only maintainer. The idea of co-maintainers was rejected by some parties. Don't be confused, the other 'M' people in the M

Re: stalled again

2015-12-02 Thread Christoph Hellwig
On Tue, Dec 01, 2015 at 06:30:28PM +0200, Or Gerlitz wrote: > Any reason on earth not to rebase your tree (== create new branch, move > their the for-next tag) after an rc1 is out? how long does this take? I'm not too worried about the base as there doesn't seem to be anything pending for 4.5-rc r

Re: stalled again

2015-12-01 Thread Greg Kroah-Hartman
On Tue, Dec 01, 2015 at 06:30:28PM +0200, Or Gerlitz wrote: > Doug, > > We're against into this... upstream is on 4.4-rc3 while your latest branch > in kernel.org (the one that carries thefor-next tag) is rebased to > 4.3-rc3... > > --> our internal build and review systems for patches to linux-r

Re: stalled again

2015-12-01 Thread Christoph Lameter
On Tue, 1 Dec 2015, Or Gerlitz wrote: > We're against into this... upstream is on 4.4-rc3 while your latest branch in > kernel.org (the one that carries thefor-next tag) is rebased to 4.3-rc3... Seems that everything was merged? So you can directly use 4.4-rc1 until he comes up with a for-next fo

stalled again

2015-12-01 Thread Or Gerlitz
Doug, We're against into this... upstream is on 4.4-rc3 while your latest branch in kernel.org (the one that carries thefor-next tag) is rebased to 4.3-rc3... --> our internal build and review systems for patches to linux-rdma can'tmake any use of your tree. People here have to rebase their