public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <shuahkh@osg.samsung.com>
To: Sergei Zviagintsev <sergei@s15v.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Daniel Mack <daniel@zonque.org>,
	David Herrmann <dh.herrmann@googlemail.com>,
	Djalal Harouni <tixxdz@opendz.org>
Cc: linux-kernel@vger.kernel.org, linux-api@vger.kernel.org
Subject: Re: [PATCH v2 0/5] selftests/kdbus: small fixes
Date: Wed, 17 Jun 2015 11:07:46 -0600	[thread overview]
Message-ID: <5581A962.3040601@osg.samsung.com> (raw)
In-Reply-To: <1434558808-16129-1-git-send-email-sergei@s15v.net>

On 06/17/2015 10:33 AM, Sergei Zviagintsev wrote:
> Set of different fixes over selftests/kdbus.
> 
> These were first sent as independent patches, and in v2 they just
> properly threaded.
> 
> Links to previous patches:
> 
> http://lkml.kernel.org/g/1434550697-24785-1-git-send-email-sergei@s15v.net
> http://lkml.kernel.org/g/1434550697-24785-2-git-send-email-sergei@s15v.net
> http://lkml.kernel.org/g/1434550697-24785-3-git-send-email-sergei@s15v.net
> http://lkml.kernel.org/g/1434550697-24785-4-git-send-email-sergei@s15v.net
> http://lkml.kernel.org/g/1434550697-24785-5-git-send-email-sergei@s15v.net
> 
> Sergei Zviagintsev (5):
>   selftests/kdbus: handle cap_get_proc() error properly
>   selftests/kdbus: drop useless assignment
>   selftests/kdbus: remove useless initializations from
>     kdbus_clone_userns_test()
>   selftests/kdbus: drop duplicated code from __kdbus_msg_send()
>   selftests/kdbus: fix error paths in __kdbus_msg_send()
> 
>  tools/testing/selftests/kdbus/kdbus-util.c       | 46 ++++++++++++------------
>  tools/testing/selftests/kdbus/test-metadata-ns.c |  9 ++---
>  2 files changed, 27 insertions(+), 28 deletions(-)
> 

Nice work! Thanks for these fixes.
Greg! Are you going to apply these into your kdbus tree?

thanks,
-- Shuah

-- 
Shuah Khan
Sr. Linux Kernel Developer
Open Source Innovation Group
Samsung Research America (Silicon Valley)
shuahkh@osg.samsung.com | (970) 217-8978

  parent reply	other threads:[~2015-06-17 17:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17 16:33 [PATCH v2 0/5] selftests/kdbus: small fixes Sergei Zviagintsev
2015-06-17 16:33 ` [PATCH v2 1/5] selftests/kdbus: handle cap_get_proc() error properly Sergei Zviagintsev
2015-06-17 16:33 ` [PATCH v2 2/5] selftests/kdbus: drop useless assignment Sergei Zviagintsev
2015-06-17 16:33 ` [PATCH v2 3/5] selftests/kdbus: remove useless initializations from kdbus_clone_userns_test() Sergei Zviagintsev
2015-06-17 16:33 ` [PATCH v2 4/5] selftests/kdbus: drop duplicated code from __kdbus_msg_send() Sergei Zviagintsev
2015-06-17 16:33 ` [PATCH v2 5/5] selftests/kdbus: fix error paths in __kdbus_msg_send() Sergei Zviagintsev
2015-06-17 17:07 ` Shuah Khan [this message]
2015-06-17 19:11   ` [PATCH v2 0/5] selftests/kdbus: small fixes Greg Kroah-Hartman
2015-06-18 10:05     ` David Herrmann
2015-06-19  4:27 ` Greg Kroah-Hartman

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=5581A962.3040601@osg.samsung.com \
    --to=shuahkh@osg.samsung.com \
    --cc=daniel@zonque.org \
    --cc=dh.herrmann@googlemail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sergei@s15v.net \
    --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