[lustre-devel] [PATCH 08/10] staging: lustre: lov: use list_for_each_entry in lov_obd.c

NeilBrown neilb at suse.com
Wed Nov 29 03:37:54 PST 2017

On Wed, Nov 29 2017, Greg Kroah-Hartman wrote:

> On Wed, Nov 29, 2017 at 02:01:12PM +1100, NeilBrown wrote:
>> Subject: [PATCH] staging: lustre: lov: use list_for_each_entry in lov_obd.c
> Why is there a subject line in the body of the text here?  Will git
> figure this out correctly?

Because I wanted to leave the original subject unchanged so it would be
fairly clear to you the context of the email, but also wanted to be
certain picked up the right subject (though in this case it would have
worked right anyway I think).
Yes, "git am" will see the Subject: line in the body and over-ride the
Subject line in the headers.


>> Using the *_entry macro simplifies the code slightly.
>> Signed-off-by: NeilBrown <neilb at suse.com>
>> ---
>> Resubmitted with non-empty changelog text.
> Did I apply the others?  Can you just send a new series of whatever I
> didn't apply so it's obvious for me as to what to do?
> thanks,
> greg k-h
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20171129/2003f661/attachment.sig>

More information about the lustre-devel mailing list