Messages in this thread | | | Date | Tue, 23 Jun 2015 06:59:43 -0700 | From | Greg Kroah-Hartman <> | Subject | Re: linux-next: Tree for Jun 23 |
| |
On Tue, Jun 23, 2015 at 05:53:58AM -0500, Eric W. Biederman wrote: > > Stephen could you please drop the kdbus tree?
What? No, that's not how this works. That's not how any of this works.
> There was some significant work that was identified last merge window > that has not yet been done, and who knows when it will be done. > Certainly the recent sd-bus API announcement strongly suggests that > there are no plans to perform such work. > > Having the kdbus tree in linux-next with the implicit suggestion that a > pull request will be sent to Linus this merge window before the problems > are addressed and we will have to repeat the mess from last merge window > keeps me up at night.
Code sitting in linux-next keeps you awake? I think you need to exercise more so that you can sleep better :)
> So to avoid the appearance that the kdbus folks are continuing to > ignoring feedback can we please keep the kdbus tree out of linux-next > until it is ready to be merged?
We are not ignoring _constructive_ feedback, please realize the difference.
First Andy does a preemptive NAK of a pull request that was never sent, and now you want to kick it out of linux-next for no valid reason. If I was an insecure person, I'd think that there are some people in the kernel community who don't like me at the moment.
This is just getting ridiculous.
greg k-h
| |