public inbox for linux-kernel@vger.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>,
	Andreas Dilger <andreas.dilger@intel.com>
Subject: Re: [PATCH 08/16] staging/lustre/mdt: HSM coordinator agent interface
Date: Tue, 26 Nov 2013 12:09:56 +0800	[thread overview]
Message-ID: <52941F14.2050900@gmail.com> (raw)
In-Reply-To: <20131126033012.GA30128@kroah.com>

On 11/26/2013 11:30 AM, Greg Kroah-Hartman wrote:
> On Tue, Nov 26, 2013 at 10:05:02AM +0800, Peng Tao wrote:
>> From: JC Lafoucriere <jacques-charles.lafoucriere@cea.fr>
>>
>> To move data with external storage, HSM coordinator
>> uses a Copy Tool running on a client named agent.
>> This patch implements the interface for these agents.
>
> Interesting text here...
>
>> Lustre-change: http://review.whamcloud.com/6534
>> Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-3342
>> Signed-off-by: JC Lafoucriere <jacques-charles.lafoucriere@cea.fr>
>> Reviewed-by: Jinshan Xiong <jinshan.xiong@intel.com>
>> Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
>> Reviewed-by: John L. Hammond <john.hammond@intel.com>
>> Reviewed-by: Oleg Drokin <oleg.drokin@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, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/staging/lustre/lustre/include/lustre/lustre_user.h b/drivers/staging/lustre/lustre/include/lustre/lustre_user.h
>> index 9436166..631f026 100644
>> --- a/drivers/staging/lustre/lustre/include/lustre/lustre_user.h
>> +++ b/drivers/staging/lustre/lustre/include/lustre/lustre_user.h
>> @@ -428,8 +428,8 @@ struct obd_uuid {
>>   	char uuid[UUID_MAX];
>>   };
>>
>> -static inline int obd_uuid_equals(const struct obd_uuid *u1,
>> -				  const struct obd_uuid *u2)
>> +static inline bool obd_uuid_equals(const struct obd_uuid *u1,
>> +				   const struct obd_uuid *u2)
>>   {
>>   	return strcmp((char *)u1->uuid, (char *)u2->uuid) == 0;
>>   }
>> @@ -446,7 +446,7 @@ static inline void obd_str2uuid(struct obd_uuid *uuid, const char *tmp)
>>   }
>>
>>   /* For printf's only, make sure uuid is terminated */
>> -static inline char *obd_uuid2str(struct obd_uuid *uuid)
>> +static inline char *obd_uuid2str(const struct obd_uuid *uuid)
>>   {
>>   	if (uuid->uuid[sizeof(*uuid) - 1] != '\0') {
>>   		/* Obviously not safe, but for printfs, no real harm done...
>
> Too bad it doesn't describe the changes made in the code at all.
>
> How can so many people review a patch that is not the same as what it
> says it really is?
>
The main part of the original commit is dropped as it only touches 
server code. I should have modified the commit message to say what 
exactly the patch does rather than just copying the original commit 
message. I'll fix up. Sorry.

> I'm stopping here in the series, sorry.  Please fix up and resend the
> rest when you can.
>
Will do. Thanks for reviewing!

Thanks,
Tao



  reply	other threads:[~2013-11-26  4:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-26  2:04 [PATCH 00/16] staging/lustre: sync with external tree, set 2 Peng Tao
2013-11-26  2:04 ` [PATCH 01/16] staging/lustre/server: use unified request handler for MGS Peng Tao
2013-11-26  2:04 ` [PATCH 02/16] staging/lustre/llog: MGC to use OSD API for backup logs Peng Tao
2013-11-26  3:14   ` Greg Kroah-Hartman
2013-11-26  3:25     ` Peng Tao
2013-11-26  3:34       ` Greg Kroah-Hartman
2013-11-26  4:05         ` Peng Tao
2013-11-26  2:04 ` [PATCH 03/16] staging/lustre/nfs: writing to new files will return ENOENT Peng Tao
2013-11-26  6:45   ` Patrick Farrell
2013-11-26 14:09     ` Peng Tao
2013-11-26  2:04 ` [PATCH 04/16] staging/lustre/ptlrpc: Fix race during exp_flock_hash creation Peng Tao
2013-11-26  2:04 ` [PATCH 05/16] staging/lustre/mdc: prevent fall through in mdc_iocontrol() Peng Tao
2013-11-26  2:05 ` [PATCH 06/16] staging/lustre/lu: shrink lu_object by 8 bytes on x86_64 Peng Tao
2013-11-26  2:05 ` [PATCH 07/16] staging/lustre/mdt: HSM coordinator client interface Peng Tao
2013-11-26  2:05 ` [PATCH 08/16] staging/lustre/mdt: HSM coordinator agent interface Peng Tao
2013-11-26  3:30   ` Greg Kroah-Hartman
2013-11-26  4:09     ` Peng Tao [this message]
2013-11-26  2:05 ` [PATCH 09/16] staging/lustre/scrub: OI scrub on OST Peng Tao
2013-11-26  2:05 ` [PATCH 10/16] staging/lustre/scrub: control OI scrub on OST from user space Peng Tao
2013-11-26  2:05 ` [PATCH 11/16] staging/lustre/llite: don't check for O_CREAT in it_create_mode Peng Tao
2013-11-26  2:05 ` [PATCH 12/16] staging/lustre/build: clean up unused variables and dead code Peng Tao
2013-11-26  2:05 ` [PATCH 13/16] staging/lustre/build: fix compilation issue with is_compat_task Peng Tao
2013-11-26  2:05 ` [PATCH 14/16] staging/lustre/ptlrpc: Fix a crash when dereferencing NULL pointer Peng Tao
2013-11-26  2:05 ` [PATCH 15/16] staging/lustre/hsm: Add hsm_release feature Peng Tao
2013-11-26  2:05 ` [PATCH] staging/lustre/llite: extended attribute cache 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=52941F14.2050900@gmail.com \
    --to=bergwolf@gmail.com \
    --cc=andreas.dilger@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox