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>,
James Simmons <uja.ornl@gmail.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: [lustre-devel] [PATCH 2/6] staging: lustre: libcfs: move memory_pressure functions to libcfs_prim.h
Date: Thu, 31 Mar 2016 20:33:34 +0000 [thread overview]
Message-ID: <647018c9fc784e15832340a614e205cc@EXCHCS32.ornl.gov> (raw)
In-Reply-To: <20160331200358.GA28146@kroah.com>
>On Thu, Mar 31, 2016 at 10:18:36AM -0400, James Simmons wrote:
>> Long ago libcfs_prim.h was used for userland code which is why
>> memory_pressure_*() handling is in both libcfs_prim.h and
>> linux-mem.h headers. So lets just move the memory_pressure_*()
>> to libcfs_prim.h.
>>
>> Signed-off-by: James Simmons <uja.ornl@gmail.com>
>> ntel-bug-id: https://jira.hpdd.intel.com/browse/LU-6245
>
>"ntel-bug-id:"? :)
Thanks for fixing that.
next prev parent reply other threads:[~2016-03-31 20:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 14:18 [PATCH 0/6] cleanup libcfs memory handling James Simmons
2016-03-31 14:18 ` [PATCH 1/6] staging: lustre: libcfs: move add_wait_queue_exclusive_head to lustre layer James Simmons
2016-03-31 14:18 ` [PATCH 2/6] staging: lustre: libcfs: move memory_pressure functions to libcfs_prim.h James Simmons
2016-03-31 20:03 ` Greg Kroah-Hartman
2016-03-31 20:33 ` Simmons, James A. [this message]
2016-03-31 14:18 ` [PATCH 3/6] staging: lustre: libcfs: remove page_index() macro James Simmons
2016-03-31 14:18 ` [PATCH 4/6] staging: lustre: libcfs: remove MMSPACE macros James Simmons
2016-03-31 14:18 ` [PATCH 5/6] staging: lustre: libcfs: move NUM_CACHEPAGES to libcfs_prim.h James Simmons
2016-03-31 14:18 ` [PATCH 6/6] staging: lustre: libcfs: delete linux-mem.h James Simmons
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=647018c9fc784e15832340a614e205cc@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 \
--cc=uja.ornl@gmail.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®