From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: NeilBrown <neilb@suse.com>
Cc: Oleg Drokin <oleg.drokin@intel.com>,
Andreas Dilger <andreas.dilger@intel.com>,
James Simmons <jsimmons@infradead.org>,
linux-kernel@vger.kernel.org, lustre-devel@lists.lustre.org
Subject: [lustre-devel] [PATCH 08/10] staging: lustre: lov: use list_for_each_entry in lov_obd.c
Date: Wed, 29 Nov 2017 10:40:23 +0100 [thread overview]
Message-ID: <20171129094023.GA7597@kroah.com> (raw)
In-Reply-To: <87r2shwzyf.fsf@notabene.neil.brown.name>
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@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
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: NeilBrown <neilb@suse.com>
Cc: Oleg Drokin <oleg.drokin@intel.com>,
Andreas Dilger <andreas.dilger@intel.com>,
James Simmons <jsimmons@infradead.org>,
linux-kernel@vger.kernel.org, lustre-devel@lists.lustre.org
Subject: Re: [PATCH 08/10] staging: lustre: lov: use list_for_each_entry in lov_obd.c
Date: Wed, 29 Nov 2017 10:40:23 +0100 [thread overview]
Message-ID: <20171129094023.GA7597@kroah.com> (raw)
In-Reply-To: <87r2shwzyf.fsf@notabene.neil.brown.name>
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@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 prev parent reply other threads:[~2017-11-29 9:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 4:59 [lustre-devel] [PATCH 00/10] staging: lustre: assorted code improvements for list manipulations NeilBrown
2017-10-30 4:59 ` NeilBrown
2017-10-30 4:59 ` [lustre-devel] [PATCH 07/10] staging: lustre: ldlm: use list_for_each_entry in ldlm_resource.c NeilBrown
2017-10-30 4:59 ` NeilBrown
2017-10-30 4:59 ` [lustre-devel] [PATCH 02/10] staging: lustre: ldlm: use list_for_each_entry in ldlm_extent_shift_kms() NeilBrown
2017-10-30 4:59 ` NeilBrown
2017-10-30 4:59 ` [lustre-devel] [PATCH 04/10] staging: lustre: ldlm: use list_for_each_entry in ldlm_lock.c NeilBrown
2017-10-30 4:59 ` NeilBrown
2017-10-30 4:59 ` [lustre-devel] [PATCH 03/10] staging: lustre: ldlm: use list_first_entry in ldlm_lock NeilBrown
2017-10-30 4:59 ` NeilBrown
2017-10-30 4:59 ` [lustre-devel] [PATCH 09/10] staging: lustre: simplfy lov_finish_set() NeilBrown
2017-10-30 4:59 ` NeilBrown
2017-10-30 4:59 ` [lustre-devel] [PATCH 06/10] staging: lustre: ldlm: minor list_entry improvements in ldlm_request.c NeilBrown
2017-10-30 4:59 ` NeilBrown
2017-10-30 4:59 ` [lustre-devel] [PATCH 05/10] staging: lustre: ldlm: use list_first_entry in ldlm_lockd.c NeilBrown
2017-10-30 4:59 ` NeilBrown
2017-10-30 4:59 ` [lustre-devel] [PATCH 08/10] staging: lustre: lov: use list_for_each_entry in lov_obd.c NeilBrown
2017-10-30 4:59 ` NeilBrown
2017-11-24 15:43 ` [lustre-devel] " Greg Kroah-Hartman
2017-11-24 15:43 ` Greg Kroah-Hartman
2017-11-29 3:01 ` [lustre-devel] " NeilBrown
2017-11-29 3:01 ` NeilBrown
2017-11-29 9:40 ` Greg Kroah-Hartman [this message]
2017-11-29 9:40 ` Greg Kroah-Hartman
2017-11-29 11:37 ` [lustre-devel] " NeilBrown
2017-11-29 11:37 ` NeilBrown
2017-10-30 4:59 ` [lustre-devel] [PATCH 01/10] staging: lustre: use list_last_entry to simplify fld_cache_shrink NeilBrown
2017-10-30 4:59 ` NeilBrown
2017-10-30 4:59 ` [lustre-devel] [PATCH 10/10] staging: lustre: obdclass: simplify cl_lock_fini() NeilBrown
2017-10-30 4:59 ` NeilBrown
2017-11-24 15:44 ` [lustre-devel] [PATCH 00/10] staging: lustre: assorted code improvements for list manipulations Greg Kroah-Hartman
2017-11-24 15:44 ` Greg Kroah-Hartman
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=20171129094023.GA7597@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andreas.dilger@intel.com \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=neilb@suse.com \
--cc=oleg.drokin@intel.com \
/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.