Re: [!GIT PULL] kdbus for 4.2

[Greg Kroah-Hartman]

On Mon, Jun 29, 2015 at 04:10:27PM +0200, Richard Weinberger wrote:
> Greg,
> 
> On Fri, Jun 26, 2015 at 9:26 PM, Greg Kroah-Hartman
> <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
> > Hi all,
> >
> > Given the email threads about kdbus this week from various community
> > members, I figured it would be good to let people know what was going on
> > with things at the moment.
> >
> > We (David, Daniel, Djalal, and myself) do not need to rush anything and
> > will be delaying the kdbus merge request for another cycle.  There still
> > seems to be some disagreement and we are confident that with more time
> > to review this can be sorted out.  We have asked distributions to start
> > testing kdbus and have already gotten back valuable feedback from real
> > world testing.  We are incorporating that feedback, fixing bugs, and
> > optimizing some internal details which will all be part of the pull
> > request for the next release cycle.
> 
> I've started digging into current kdbus to understand the changes you made and
> have a question.
> Where does all the development happen?
> 
> For example your current tree contains the following commit:
> 
> commit f3adf84302fb4fdb6698cf129b96546b47e27d33
> Author: David Herrmann <dh.herrmann@xxxxxxxxx>
> Date:   Thu May 21 20:03:29 2015 +0200
> 
>     kdbus: skip mandatory items on negotiation
> 
>     The kdbus negotiation is used to figure out what items and flags an ioctl
>     supports. It is highly impractical to pass in mandatory items when all we
>     do is negotiation. Therefore, allow user-space to skip mandatory items if
>     KDBUS_FLAG_NEGOTIATE is passed.
> 
>     Signed-off-by: David Herrmann <dh.herrmann@xxxxxxxxx>
>     Acked-by: Daniel Mack <daniel@xxxxxxxxxx>
> 
> Where was this patch posted to?

There was a pull request that happened on the linux-kernel mailing list
with this patch in it, along with others.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/