From: James Simmons <jsimmons@infradead.org>
To: Joe Perches <joe@perches.com>
Cc: "Drokin, Oleg" <oleg.drokin@intel.com>,
"<linux-kernel@vger.kernel.org>" <linux-kernel@vger.kernel.org>,
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, 1 Apr 2016 20:57:18 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.20.1604012057020.17701@casper.infradead.org> (raw)
In-Reply-To: <1459536253.1744.26.camel@perches.com>
[-- Attachment #1: Type: text/plain, Size: 2343 bytes --]
> > I know James is working on cleaning up LNet, but I don't know if he has
> > anything this would be conflicting at this moment or not.
> >
> > Thanks for the patches. I wonder if you are generating them automatically?
> > Because it would be great if it also fixes the alignment issues
>
> It's pretty automatic.
>
> It's a trivial variant of the detypedef perl script I wrote awhile ago:
> http://permalink.gmane.org/gmane.linux.drivers.driver-project.devel/18603
>
>
> I think changing the alignment issues is better done in a
> separate patch.
>
> James isn't cc'd on these patches as he's not a listed
> maintainer. Maybe he should be added for all of it or
> some part of it?
Yes please add me to the maintainer list. Currently the work is divided
between Oleg and I. I also actively test this client to find any
regressions. I have been working on the LNet, libcfs cleanups and bug
fixes. Any libcfs/LNet changes please send my way.
Also now that LNet is close to being synced with our production code it
means I have free cycles to find all the earlier dropped patches in
the Lustre code. We have gaps in various places where patches were
dropped. So I will be working on pushing those patches as well. Oleg
still is the main person for the Lustre core client code.
> I don't know what email address James prefers as there
> are several in git log for him.
>
> James Simmons <uja.ornl@yahoo.com>
> James Simmons <uja.ornl@gmail.com>
> James Simmons <jsimmons@infradead.org>
> "Simmons, James A." <simmonsja@ornl.gov>
The infradead.org account is the main one. The ornl.gov is my day job
account. The yahoo and gmail accounts are used, for openid, to push
patches to the OpenSFS Lustre branch which is why you see those Signed-Off
with various patch ports.
> but maybe something like this:
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 16ccda4..d585631 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -10578,6 +10578,7 @@ F: drivers/staging/media/lirc/
> STAGING - LUSTRE PARALLEL FILESYSTEM
> M: Oleg Drokin <oleg.drokin@intel.com>
> M: Andreas Dilger <andreas.dilger@intel.com>
> +R: James Simmons <jsimmons@infradead.org>
> L: lustre-devel@lists.lustre.org (moderated for non-subscribers)
> W: http://wiki.lustre.org/
> S: Maintained
next prev parent reply other threads:[~2016-04-01 19:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 13:02 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 ` [RFC PATCH 2/3] staging: lustre: Remove typedef lnd_t Joe Perches
2016-04-01 13:02 ` [RFC PATCH 3/3] staging: lustre: Remove typedef lnet_msg_t Joe Perches
2016-04-01 14:23 ` [lustre-devel] [RFC PATCH 0/3] staging: lustre: detypedef Drokin, Oleg
2016-04-01 18:44 ` Joe Perches
2016-04-01 19:14 ` Drokin, Oleg
2016-04-01 19:27 ` Joe Perches
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 19:56 ` [lustre-devel] [RFC PATCH 0/3] staging: lustre: detypedef James Simmons
2016-04-01 19:57 ` James Simmons
2016-04-01 19:57 ` James Simmons [this message]
2016-04-01 19:59 ` James Simmons
2016-04-01 15:58 ` Simmons, James A.
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=alpine.LFD.2.20.1604012057020.17701@casper.infradead.org \
--to=jsimmons@infradead.org \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®