From: "Simmons, James A." <simmonsja@ornl.gov>
To: "'Greg Kroah-Hartman'" <gregkh@linuxfoundation.org>,
James Simmons <jsimmons@infradead.org>
Cc: "devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
Oleg Drokin <oleg.drokin@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Lustre Development List <lustre-devel@lists.lustre.org>
Subject: RE: [lustre-devel] [PATCH 00/10] Last batch of fixes for LNet
Date: Mon, 7 Mar 2016 19:34:54 +0000 [thread overview]
Message-ID: <eb04d2ccb6ef4fe98df59ecb9f75afa9@EXCHCS32.ornl.gov> (raw)
In-Reply-To: <20160305195256.GA8126@kroah.com>
>On Fri, Mar 04, 2016 at 09:09:40PM -0500, James Simmons wrote:
>> This batch merges the remaining LNet patches from the OpenSFS
>> branch for the upstream client. Once merged the LNet code
>> will be up to date with the latest production code. Only style
>> issues are remaining. Still future patches being developed
>> for LNet will be landed to the upstream client as soon as they
>> are ready after extensive testing.
>
>Please fix up the build issue, and figure out what went wrong with the
>__user patch that you sent and resend this series after reworking them.
I had a discussion with Oleg about the __user patch. It appears that is
a bug in the production branch so that patch can be dropped. As for the
build issues this has been a know issue for a awhile but nobody has
gotten around to fixing all the 32 bit issues. I guess it is time to fix that up.
I will send out new patches later after I'm doing testing them.
WARNING: multiple messages have this Message-ID (diff)
From: Simmons, James A. <simmonsja@ornl.gov>
To: 'Greg Kroah-Hartman' <gregkh@linuxfoundation.org>,
James Simmons <jsimmons@infradead.org>
Cc: "devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
Oleg Drokin <oleg.drokin@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Lustre Development List <lustre-devel@lists.lustre.org>
Subject: [lustre-devel] [PATCH 00/10] Last batch of fixes for LNet
Date: Mon, 7 Mar 2016 19:34:54 +0000 [thread overview]
Message-ID: <eb04d2ccb6ef4fe98df59ecb9f75afa9@EXCHCS32.ornl.gov> (raw)
In-Reply-To: <20160305195256.GA8126@kroah.com>
>On Fri, Mar 04, 2016 at 09:09:40PM -0500, James Simmons wrote:
>> This batch merges the remaining LNet patches from the OpenSFS
>> branch for the upstream client. Once merged the LNet code
>> will be up to date with the latest production code. Only style
>> issues are remaining. Still future patches being developed
>> for LNet will be landed to the upstream client as soon as they
>> are ready after extensive testing.
>
>Please fix up the build issue, and figure out what went wrong with the
>__user patch that you sent and resend this series after reworking them.
I had a discussion with Oleg about the __user patch. It appears that is
a bug in the production branch so that patch can be dropped. As for the
build issues this has been a know issue for a awhile but nobody has
gotten around to fixing all the 32 bit issues. I guess it is time to fix that up.
I will send out new patches later after I'm doing testing them.
next prev parent reply other threads:[~2016-03-07 19:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 2:09 [PATCH 00/10] Last batch of fixes for LNet James Simmons
2016-03-05 2:09 ` [lustre-devel] " James Simmons
2016-03-05 2:09 ` [PATCH 01/10] staging: lustre: LNet drop rule implementation James Simmons
2016-03-05 2:09 ` [lustre-devel] " James Simmons
2016-03-05 7:53 ` kbuild test robot
2016-03-05 7:53 ` [lustre-devel] " kbuild test robot
2016-03-05 2:09 ` [PATCH 02/10] staging: lustre: LNet network latency simulation James Simmons
2016-03-05 2:09 ` [lustre-devel] " James Simmons
2016-03-05 2:09 ` [PATCH 03/10] staging: lustre: fix 'data race condition' issue in conrpc.c James Simmons
2016-03-05 2:09 ` [lustre-devel] " James Simmons
2016-03-05 2:09 ` [PATCH 04/10] staging: lustre: fix 'NULL pointer dereference' errors James Simmons
2016-03-05 2:09 ` [lustre-devel] " James Simmons
2016-03-05 2:09 ` [PATCH 05/10] staging: lustre: fix 'data race condition' issue in framework.c James Simmons
2016-03-05 2:09 ` [lustre-devel] " James Simmons
2016-03-05 2:09 ` [PATCH 06/10] staging: lustre: Correct missing newline James Simmons
2016-03-05 2:09 ` [lustre-devel] " James Simmons
2016-03-05 2:09 ` [PATCH 07/10] staging: lustre: add last missing sparse annotation __user James Simmons
2016-03-05 2:09 ` [lustre-devel] " James Simmons
2016-03-05 2:55 ` Drokin, Oleg
2016-03-05 2:55 ` [lustre-devel] " Drokin, Oleg
2016-03-05 2:09 ` [PATCH 08/10] staging: lustre: change test to asser in LNetGetId James Simmons
2016-03-05 2:09 ` [lustre-devel] " James Simmons
2016-03-05 2:09 ` [PATCH 09/10] staging: lustre: rename proc_call_handler to lprocfs_call_handler James Simmons
2016-03-05 2:09 ` [lustre-devel] " James Simmons
2016-03-05 2:09 ` [PATCH 10/10] staging: lustre: make LNet use lprocfs_call_handler James Simmons
2016-03-05 2:09 ` [lustre-devel] " James Simmons
2016-03-05 19:52 ` [PATCH 00/10] Last batch of fixes for LNet Greg Kroah-Hartman
2016-03-05 19:52 ` [lustre-devel] " Greg Kroah-Hartman
2016-03-07 19:34 ` Simmons, James A. [this message]
2016-03-07 19:34 ` Simmons, James A.
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=eb04d2ccb6ef4fe98df59ecb9f75afa9@EXCHCS32.ornl.gov \
--to=simmonsja@ornl.gov \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jsimmons@infradead.org \
--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.