linux-kernel - Re: [PATCH 08/10] staging: lustre: lov: use list_for_each_entry in lov

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 29 Nov 2017 10:40:23 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     NeilBrown <neilb@...e.com>
Cc:     Oleg Drokin <oleg.drokin@...el.com>,
        Andreas Dilger <andreas.dilger@...el.com>,
        James Simmons <jsimmons@...radead.org>,
        linux-kernel@...r.kernel.org, lustre-devel@...ts.lustre.org
Subject: Re: [PATCH 08/10] staging: lustre: lov: use list_for_each_entry in
 lov_obd.c

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?

> Using the *_entry macro simplifies the code slightly.
> 
> Signed-off-by: NeilBrown <neilb@...e.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