From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: David Herrmann <dh.herrmann@gmail.com>
Cc: Djalal Harouni <tixxdz@opendz.org>,
Daniel Mack <daniel@zonque.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] kdbus updates for Greg
Date: Mon, 13 Jul 2015 14:54:13 -0700 [thread overview]
Message-ID: <20150713215413.GA24770@kroah.com> (raw)
In-Reply-To: <CANq1E4T64hw4NL4Nk1YyOcb+S+v7ddxAAMhhGjUAwYANmqjE5A@mail.gmail.com>
On Mon, Jul 06, 2015 at 08:40:29PM +0200, David Herrmann wrote:
> Hi Greg
>
> Big set of updates for kdbus. I picked up all remaining cleanups and
> fixes from the ML and added my performance rework. Features are
> described below. All tested for several weeks as part of the
> out-of-tree repo.
>
> Thanks
> David
>
> The following changes since commit 337faaf05f04521a1546e652626e7f386f598193:
>
> Merge 4.1 into branch 'kdbus' (2015-06-26 15:54:26 -0700)
Sorry for the delay, all now pulled and pushed out.
thanks,
greg k-h
prev parent reply other threads:[~2015-07-13 21:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 18:40 [GIT PULL] kdbus updates for Greg David Herrmann
2015-07-13 21:54 ` Greg Kroah-Hartman [this message]
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=20150713215413.GA24770@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=daniel@zonque.org \
--cc=dh.herrmann@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tixxdz@opendz.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox