All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peng Tao <bergwolf@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org,
	JC Lafoucriere <jacques-charles.lafoucriere@cea.fr>,
	Henri Doreau <henri.doreau@cea.fr>, Peng Tao <bergwolf@gmail.com>,
	Andreas Dilger <andreas.dilger@intel.com>
Subject: [PATCH v2 RESEND 7/8] staging/lustre/lustre_user.h: remove obsolete comments
Date: Wed, 22 Jan 2014 21:36:18 +0800	[thread overview]
Message-ID: <1390397779-30975-8-git-send-email-bergwolf@gmail.com> (raw)
In-Reply-To: <1390397779-30975-1-git-send-email-bergwolf@gmail.com>

From: JC Lafoucriere <jacques-charles.lafoucriere@cea.fr>

This is only part of the original Lustre commit, main part of which changes
user space code. And now the comments above struct hsm_copy is no more true.

Lustre-change: http://review.whamcloud.com/4737
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-2062
Signed-off-by: JC Lafoucriere <jacques-charles.lafoucriere@cea.fr>
Signed-off-by: Henri Doreau <henri.doreau@cea.fr>
Reviewed-by: John L. Hammond <john.hammond@intel.com>
Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
Signed-off-by: Peng Tao <bergwolf@gmail.com>
Signed-off-by: Andreas Dilger <andreas.dilger@intel.com>
---
 .../lustre/lustre/include/lustre/lustre_user.h     |    6 ------
 1 file changed, 6 deletions(-)

diff --git a/drivers/staging/lustre/lustre/include/lustre/lustre_user.h b/drivers/staging/lustre/lustre/include/lustre/lustre_user.h
index 6b6c0240..4d3c25f 100644
--- a/drivers/staging/lustre/lustre/include/lustre/lustre_user.h
+++ b/drivers/staging/lustre/lustre/include/lustre/lustre_user.h
@@ -1158,12 +1158,6 @@ struct hsm_progress {
 	__u32			padding;
 };
 
-/**
- * Use by copytool during any hsm request they handled.
- * This structure is initialized by llapi_hsm_copy_start()
- * which is an helper over the ioctl() interface
- * Store Lustre, internal use only, data.
- */
 struct hsm_copy {
 	__u64			hc_data_version;
 	__u16			hc_flags;
-- 
1.7.9.5


  parent reply	other threads:[~2014-01-22 13:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-22 13:36 [PATCH v2 RESEND 0/8] staging/lustre: sync with external tree Peng Tao
2014-01-22 13:36 ` [PATCH v2 RESEND 1/8] staging/lustre/llite: remove ll_d_root_ops Peng Tao
2014-01-22 13:36 ` [PATCH v2 RESEND 2/8] staging/lustre/llite: don't d_add for create only files Peng Tao
2014-01-22 13:36 ` [PATCH v2 RESEND 3/8] staging/lustre/llite: pass correct pointer to obd_iocontrol() Peng Tao
2014-01-22 13:36 ` [PATCH v2 RESEND 4/8] staging/lustre/idl: remove LASSERT/CLASSERT from lustre_idl.h Peng Tao
2014-01-22 13:36 ` [PATCH v2 RESEND 5/8] staging/lustre/mgs: set_param -P option that sets value permanently Peng Tao
2014-01-22 13:36 ` [PATCH v2 RESEND 6/8] staging/lustre/obdclass: remove extra break in class_process_config Peng Tao
2014-02-07 17:43   ` Greg Kroah-Hartman
2014-02-08  1:52     ` Peng Tao
2014-01-22 13:36 ` Peng Tao [this message]
2014-01-22 13:36 ` [PATCH v2 RESEND 8/8] staging/lustre/ptlrpc: flock deadlock detection does not work Peng Tao

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=1390397779-30975-8-git-send-email-bergwolf@gmail.com \
    --to=bergwolf@gmail.com \
    --cc=andreas.dilger@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=henri.doreau@cea.fr \
    --cc=jacques-charles.lafoucriere@cea.fr \
    --cc=linux-kernel@vger.kernel.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 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.