From: "chunshan.zhu" <chunshan.zhu@gmail.com>
To: Richard Weinberger <richard@nod.at>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Richard Weinberger <richard.weinberger@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
"Eric W. Biederman" <ebiederm@xmission.com>,
One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
Tom Gundersen <teg@jklm.no>, Jiri Kosina <jkosina@suse.cz>,
Andy Lutomirski <luto@amacapital.net>,
LKML <linux-kernel@vger.kernel.org>,
Daniel Mack <daniel@zonque.org>,
David Herrmann <dh.herrmann@gmail.com>,
Djalal Harouni <tixxdz@opendz.org>
Subject: Re: [!GIT PULL] kdbus for 4.2
Date: Tue, 30 Jun 2015 09:06:02 +0800 [thread overview]
Message-ID: <5591EB7A.2040605@gmail.com> (raw)
In-Reply-To: <559168A7.80206@nod.at>
David's out tree modules kdbus tree
https://github.com/systemd/kdbus
On 06/29/2015 11:47 PM, Richard Weinberger wrote:
> Am 29.06.2015 um 17:45 schrieb 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@linuxfoundation.org> 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@gmail.com>
>>> 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@gmail.com>
>>> Acked-by: Daniel Mack <daniel@zonque.org>
>>>
>>> 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.
> I saw the pull request on LKML but not the patch. That's why I'm asking. :)
>
> Thanks,
> //richard
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2015-06-30 1:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 19:26 [!GIT PULL] kdbus for 4.2 Greg Kroah-Hartman
2015-06-26 19:33 ` Andy Lutomirski
2015-06-26 19:36 ` Tom Gundersen
2015-06-28 7:51 ` Richard Weinberger
2015-07-03 0:39 ` Andy Lutomirski
2015-07-03 8:43 ` David Herrmann
2015-07-03 8:53 ` Richard Weinberger
2015-07-03 15:27 ` Greg Kroah-Hartman
2015-07-03 16:22 ` Richard Weinberger
2015-07-03 16:23 ` Andy Lutomirski
2015-06-29 14:10 ` Richard Weinberger
2015-06-29 15:45 ` Greg Kroah-Hartman
2015-06-29 15:47 ` Richard Weinberger
2015-06-30 1:06 ` chunshan.zhu [this message]
2015-06-30 6:29 ` Richard Weinberger
2015-07-01 15:55 ` David Herrmann
2015-07-01 16:12 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5591EB7A.2040605@gmail.com \
--to=chunshan.zhu@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=daniel@zonque.org \
--cc=dh.herrmann@gmail.com \
--cc=ebiederm@xmission.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=richard.weinberger@gmail.com \
--cc=richard@nod.at \
--cc=teg@jklm.no \
--cc=tixxdz@opendz.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.