From: Dan Carpenter <dan.carpenter@oracle.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] [PATCH 07/10] staging: lustre: Handle nodemask on UMP machines
Date: Sat, 7 Nov 2015 23:53:50 +0300 [thread overview]
Message-ID: <20151107205350.GL18797@mwanda> (raw)
In-Reply-To: <cafafd1c8db141899d9c9757422451dd@EXCHCS32.ornl.gov>
The tree has to be git bisectable. Don't break and then fix, send the
combo.
regards,
dan carpenter
next prev parent reply other threads:[~2015-11-07 20:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 18:39 [lustre-devel] [PATCH 01/10] staging: lustre: wrong parameter to cfs_hash_keycpy James Simmons
2015-11-04 18:39 ` [lustre-devel] [PATCH 02/10] staging: lustre: remove unnecessary EXPORT_SYMBOL in libcfs James Simmons
2015-11-04 18:39 ` [lustre-devel] [PATCH 03/10] staging: lustre: remove libcfs_debug_set_level prototype from libcfs_private.h James Simmons
2015-11-04 18:40 ` [lustre-devel] [PATCH 04/10] staging: lustre: fix buffer overflow of string buffer James Simmons
2015-11-04 18:40 ` [lustre-devel] [PATCH 05/10] staging: lustre: Fix possible NULL pointer dereference in lprocfs_status.c James Simmons
2015-11-04 18:40 ` [lustre-devel] [PATCH 06/10] staging: lustre: Update module author to OpenSFS James Simmons
2015-11-04 18:40 ` [lustre-devel] [PATCH 07/10] staging: lustre: Handle nodemask on UMP machines James Simmons
2015-11-04 22:06 ` kbuild test robot
2015-11-05 0:46 ` kbuild test robot
2015-11-06 22:18 ` Simmons, James A.
2015-11-07 1:12 ` Greg Kroah-Hartman
2015-11-07 20:53 ` Dan Carpenter [this message]
2015-11-04 18:40 ` [lustre-devel] [PATCH 08/10] staging: lustre: race condition for check/use cfs_fail_val James Simmons
2015-11-04 18:40 ` [lustre-devel] [PATCH 09/10] staging: lustre: remove page_collection::pc_lock in libcfs James Simmons
2015-11-04 18:40 ` [lustre-devel] [PATCH 10/10] staging: lustre: fix 'error handling' issues for libcfs workitem.c 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=20151107205350.GL18797@mwanda \
--to=dan.carpenter@oracle.com \
--cc=lustre-devel@lists.lustre.org \
/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