All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dmitry Eremin <dmitry.eremin@intel.com>
Cc: devel@driverdev.osuosl.org,
	Andreas Dilger <andreas.dilger@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Oleg Drokin <oleg.drokin@intel.com>,
	Lustre Development List <lustre-devel@lists.lustre.org>
Subject: [lustre-devel] [PATCH v3] staging: lustre: separate a connection destroy from free struct kib_conn
Date: Wed, 24 Jan 2018 15:29:54 +0100	[thread overview]
Message-ID: <20180124142954.GA4658@kroah.com> (raw)
In-Reply-To: <1516803252-14266-1-git-send-email-dmitry.eremin@intel.com>

On Wed, Jan 24, 2018 at 05:14:12PM +0300, Dmitry Eremin wrote:
> Rewrite the logic of the original commit 4d99b2581eff ("staging: lustre: avoid
> intensive reconnecting for ko2iblnd") and move the freeing a struct kib_conn
> outside of the function kiblnd_destroy_conn(). The freeing of struct kib_conn
> should be depending on the second argument free_conn of function
> kiblnd_destroy_conn(struct kib_conn *conn, bool free_conn). If it true the
> structure should be freed.
> 
> Fixes: 4d99b2581eff ("staging: lustre: avoid intensive reconnecting for ko2iblnd")
> Signed-off-by: Dmitry Eremin <Dmitry.Eremin@intel.com>
> ---
>  drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd.c    | 7 +++----
>  drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd.h    | 2 +-
>  drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd_cb.c | 6 ++++--
>  3 files changed, 8 insertions(+), 7 deletions(-)

What changed from version 2 and 1?  Always included that below the ---
line please.

4th try is a charm?  :)

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dmitry Eremin <dmitry.eremin@intel.com>
Cc: devel@driverdev.osuosl.org,
	Andreas Dilger <andreas.dilger@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Oleg Drokin <oleg.drokin@intel.com>,
	Lustre Development List <lustre-devel@lists.lustre.org>
Subject: Re: [PATCH v3] staging: lustre: separate a connection destroy from free struct kib_conn
Date: Wed, 24 Jan 2018 15:29:54 +0100	[thread overview]
Message-ID: <20180124142954.GA4658@kroah.com> (raw)
In-Reply-To: <1516803252-14266-1-git-send-email-dmitry.eremin@intel.com>

On Wed, Jan 24, 2018 at 05:14:12PM +0300, Dmitry Eremin wrote:
> Rewrite the logic of the original commit 4d99b2581eff ("staging: lustre: avoid
> intensive reconnecting for ko2iblnd") and move the freeing a struct kib_conn
> outside of the function kiblnd_destroy_conn(). The freeing of struct kib_conn
> should be depending on the second argument free_conn of function
> kiblnd_destroy_conn(struct kib_conn *conn, bool free_conn). If it true the
> structure should be freed.
> 
> Fixes: 4d99b2581eff ("staging: lustre: avoid intensive reconnecting for ko2iblnd")
> Signed-off-by: Dmitry Eremin <Dmitry.Eremin@intel.com>
> ---
>  drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd.c    | 7 +++----
>  drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd.h    | 2 +-
>  drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd_cb.c | 6 ++++--
>  3 files changed, 8 insertions(+), 7 deletions(-)

What changed from version 2 and 1?  Always included that below the ---
line please.

4th try is a charm?  :)

thanks,

greg k-h
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

  reply	other threads:[~2018-01-24 14:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1516114161-27679-1-git-send-email-Dmitry.Eremin@intel.com>
2018-01-16 15:01 ` [lustre-devel] [PATCH] staging: lustre: Fix avoid intensive reconnecting for ko2iblnd patch Eremin, Dmitry
2018-01-16 15:01   ` Eremin, Dmitry
2018-01-16 16:56   ` [lustre-devel] " Greg Kroah-Hartman
2018-01-16 16:56     ` Greg Kroah-Hartman
2018-01-17  0:36     ` [lustre-devel] " Dilger, Andreas
2018-01-17  0:36       ` Dilger, Andreas
2018-01-17 14:02       ` [lustre-devel] " Greg Kroah-Hartman
2018-01-17 14:02         ` Greg Kroah-Hartman
2018-01-16 18:02 ` [lustre-devel] " Eremin, Dmitry
2018-01-16 18:02   ` Eremin, Dmitry
2018-01-22 10:39   ` [lustre-devel] " Greg Kroah-Hartman
2018-01-22 10:39     ` Greg Kroah-Hartman
2018-01-24 12:45     ` [lustre-devel] [PATCH v2] " Dmitry Eremin
2018-01-24 12:45       ` Dmitry Eremin
2018-01-24 14:14     ` [lustre-devel] [PATCH v3] staging: lustre: separate a connection destroy from free struct kib_conn Dmitry Eremin
2018-01-24 14:14       ` Dmitry Eremin
2018-01-24 14:29       ` Greg Kroah-Hartman [this message]
2018-01-24 14:29         ` Greg Kroah-Hartman
2018-01-25 13:51         ` [lustre-devel] [PATCH v4] " Dmitry Eremin
2018-01-25 13:51           ` Dmitry Eremin
2018-01-25 13:51           ` Dmitry Eremin
2018-01-26  4:34           ` [lustre-devel] " Dilger, Andreas
2018-01-26  4:34             ` Dilger, Andreas

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=20180124142954.GA4658@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andreas.dilger@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=dmitry.eremin@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lustre-devel@lists.lustre.org \
    --cc=oleg.drokin@intel.com \
    /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.