All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: "Simmons, James A." <simmonsja@ornl.gov>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Oleg Drokin <oleg.drokin@intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"lustre-devel@lists.lustre.org" <lustre-devel@lists.lustre.org>
Subject: Re: [lustre-devel] [RFC PATCH 0/3] staging: lustre: detypedef
Date: Fri, 01 Apr 2016 11:54:18 -0700	[thread overview]
Message-ID: <1459536858.1744.30.camel@perches.com> (raw)
In-Reply-To: <e80afb24bd424ab183bc7732ed556d3a@EXCHCS32.ornl.gov>

On Fri, 2016-04-01 at 15:58 +0000, Simmons, James A. wrote:
> > When would be an appropriate time to submit patches similar to
> > below that individually remove various typedefs from lustre code?
> > 
> > These are pretty trivial to produce and verify so there's no
> > particular hurry to do them now but applying them will require
> > resync points for active and actually useful developers.

> Actually could you hold off for the LNet core and LND drivers these
> changes. I have plans to push a few more LNet patches soon. I have
> been just waiting for everyone to figure out how to deal with the 
> latest changes to the infinband layer first.

Sure.  No worries.

> There are a few typedefs like lnet_nid_t I like to keep or if it has to
> be changed turn it into a struct then. Things like lnet_nid_t act like
> a cookie handle.

Fine by me.

WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: "Simmons, James A." <simmonsja@ornl.gov>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Oleg Drokin <oleg.drokin@intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"lustre-devel@lists.lustre.org" <lustre-devel@lists.lustre.org>
Subject: [lustre-devel] [RFC PATCH 0/3] staging: lustre: detypedef
Date: Fri, 01 Apr 2016 11:54:18 -0700	[thread overview]
Message-ID: <1459536858.1744.30.camel@perches.com> (raw)
In-Reply-To: <e80afb24bd424ab183bc7732ed556d3a@EXCHCS32.ornl.gov>

On Fri, 2016-04-01 at 15:58 +0000, Simmons, James A. wrote:
> > When would be an appropriate time to submit patches similar to
> > below that individually remove various typedefs from lustre code?
> > 
> > These are pretty trivial to produce and verify so there's no
> > particular hurry to do them now but applying them will require
> > resync points for active and actually useful developers.

> Actually could you hold off for the LNet core and LND drivers these
> changes. I have plans to push a few more LNet patches soon. I have
> been just waiting for everyone to figure out how to deal with the?
> latest changes to the infinband layer first.

Sure. ?No worries.

> There are a few typedefs like lnet_nid_t I like to keep or if it has to
> be changed turn it into a struct then. Things like lnet_nid_t act like
> a cookie handle.

Fine by me.

  reply	other threads:[~2016-04-01 18:54 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-01 13:02 [RFC PATCH 0/3] staging: lustre: detypedef Joe Perches
2016-04-01 13:02 ` [lustre-devel] " Joe Perches
2016-04-01 13:02 ` [RFC PATCH 1/3] staging: lustre: Remove typedef lnet_peer_t Joe Perches
2016-04-01 13:02   ` [lustre-devel] " Joe Perches
2016-04-01 13:02 ` [RFC PATCH 2/3] staging: lustre: Remove typedef lnd_t Joe Perches
2016-04-01 13:02   ` [lustre-devel] " Joe Perches
2016-04-01 13:02 ` [RFC PATCH 3/3] staging: lustre: Remove typedef lnet_msg_t Joe Perches
2016-04-01 13:02   ` [lustre-devel] " Joe Perches
2016-04-01 14:23 ` [lustre-devel] [RFC PATCH 0/3] staging: lustre: detypedef Drokin, Oleg
2016-04-01 14:23   ` Drokin, Oleg
2016-04-01 18:44   ` Joe Perches
2016-04-01 18:44     ` Joe Perches
2016-04-01 19:14     ` Drokin, Oleg
2016-04-01 19:14       ` Drokin, Oleg
2016-04-01 19:27       ` Joe Perches
2016-04-01 19:27         ` Joe Perches
2016-04-01 19:56     ` James Simmons
2016-04-01 19:56       ` James Simmons
2016-04-01 20:03       ` [lustre-devel] [RFC PATCH 0/3] staging: lustre: detypede James Simmons
2016-04-01 20:03         ` James Simmons
2016-04-01 19:56     ` [lustre-devel] [RFC PATCH 0/3] staging: lustre: detypedef James Simmons
2016-04-01 19:56       ` James Simmons
2016-04-01 19:57     ` James Simmons
2016-04-01 19:57       ` James Simmons
2016-04-01 19:57     ` James Simmons
2016-04-01 19:57       ` James Simmons
2016-04-01 19:59     ` James Simmons
2016-04-01 19:59       ` James Simmons
2016-04-01 15:58 ` Simmons, James A.
2016-04-01 15:58   ` Simmons, James A.
2016-04-01 18:54   ` Joe Perches [this message]
2016-04-01 18:54     ` Joe Perches

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=1459536858.1744.30.camel@perches.com \
    --to=joe@perches.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lustre-devel@lists.lustre.org \
    --cc=oleg.drokin@intel.com \
    --cc=simmonsja@ornl.gov \
    /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.