On Sat, Jun 17, 2017 at 07:09:59AM +0200, 'Greg Kroah-Hartman' wrote: > On Fri, Jun 16, 2017 at 11:21:00PM +0300, Serge Semin wrote: > > On Fri, Jun 16, 2017 at 01:34:59PM -0600, Logan Gunthorpe > > <log...@deltatee.com> wrote: > > > Now, if you'd like to actually review the code I'd be happy to address > > > any concerns you find. I won't be responding to any more philosophical > > > arguments or bike-shedding over the format of the patch. > > > > > > > I don't want to review a patchset, which isn't properly formated. > > Ah, but the patchset does seem to properly formatted. At least it's > easy for me to review as-published, while a much smaller number of > patches, making much larger individual patches, would be much much > harder to review. > > But what do I know... > > Oh wait, I review more kernel patches than anyone else :) > > Logan, given that you need to rebase these on the "new" ntb api (and why > the hell is that tree on github? We can't take kernel git pulls from > github), is it worth reviewing this patch series as-is, or do you want
Well, Linus has been taking my pull request from it since v3.12. He did call me out initially for requesting it initially, but was amenible after I GPG signed all of my pull requests (and had a sufficient number of people he "knew" in my ring). But all of that has been sorted out now. The reason it is on Github is for the Wiki of NTB HW and it's usage https://github.com/jonmason/ntb/wiki It's gotten a bit stale, but was very useful back in the v3.12 days :) (Also, I am using this as a call to update the Wiki!) Thanks, Jon > us to wait? > > thanks, > > greg k-h