From mboxrd@z Thu Jan 1 00:00:00 1970 From: NeilBrown Date: Wed, 29 Nov 2017 22:37:54 +1100 Subject: [lustre-devel] [PATCH 08/10] staging: lustre: lov: use list_for_each_entry in lov_obd.c In-Reply-To: <20171129094023.GA7597@kroah.com> References: <150933945578.22133.8029060522107378499.stgit@noble> <150933956729.22133.13130557672702877610.stgit@noble> <20171124154341.GA16654@kroah.com> <87r2shwzyf.fsf@notabene.neil.brown.name> <20171129094023.GA7597@kroah.com> Message-ID: <87bmjlwc19.fsf@notabene.neil.brown.name> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Greg Kroah-Hartman Cc: Oleg Drokin , Andreas Dilger , James Simmons , linux-kernel@vger.kernel.org, lustre-devel@lists.lustre.org 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. Thanks, NeilBrown > >> Using the *_entry macro simplifies the code slightly. >> >> Signed-off-by: NeilBrown >> --- >> >> 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: From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754614AbdK2LiF (ORCPT ); Wed, 29 Nov 2017 06:38:05 -0500 Received: from mx2.suse.de ([195.135.220.15]:51776 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752280AbdK2LiE (ORCPT ); Wed, 29 Nov 2017 06:38:04 -0500 From: NeilBrown To: Greg Kroah-Hartman Date: Wed, 29 Nov 2017 22:37:54 +1100 Cc: Oleg Drokin , Andreas Dilger , James Simmons , 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 In-Reply-To: <20171129094023.GA7597@kroah.com> References: <150933945578.22133.8029060522107378499.stgit@noble> <150933956729.22133.13130557672702877610.stgit@noble> <20171124154341.GA16654@kroah.com> <87r2shwzyf.fsf@notabene.neil.brown.name> <20171129094023.GA7597@kroah.com> Message-ID: <87bmjlwc19.fsf@notabene.neil.brown.name> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable 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_ob= d.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. Thanks, NeilBrown > >> Using the *_entry macro simplifies the code slightly. >>=20 >> Signed-off-by: NeilBrown >> --- >>=20 >> 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 --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEG8Yp69OQ2HB7X0l6Oeye3VZigbkFAloenBIACgkQOeye3VZi gbnhRw/+JfF+bhejMxzKPMP0HNyJQTyiYgebpk4vVPs/iE0VemzdhnPMVxUs42Ma cPY+PPVZ064zDUAOyJEsZubZxr5GYpqoCogo4Lczale3xG/AxX2voY41MfXCExeT BDVi2ezlcGaeVSPbBM+44qcEYbls5LEu3mjWZtLc/wAj3huEqvPi7Z8ChZ5JKVKY Wqpt7zsUlYDXg5HvVnrGyKDg9YEeOPk5uM+QdaS5cOaR8MhQ5Z/D/xKeHHPnad5b 9s7/BB1jUKFDBE3yXgFhy0xWAYzul7du8PYKyYYG/kBcKCRPT5MkR75tXwmYy853 C7DG8HbJGzIllMHy5nqNlmVSKB4tXDIPToyOAa+Fn94p18VAhjJOfiKko3Ck+nmb eaVINI3PJfwQZ1q+bCMNfcASpEHcB3pb5ZY0fQefRQzopc4UvoUMwumT5jhpJ0uI qXZis1s0Oh7xC2869ppUzCkMSwyRGSnGXwbRSfSAbBc7OPJSGa/ppP2Tae6b60Mk WvRnPdrPXQfs7qdXgpiZ1kvKT9OJGLa3pQNqD+V4cYJdW7Fj0fwj2Dvbg0Wyb4Nq dmG/xpuBnEwo5OuDb7xzFdTJ2xt/AyqlwahuJS1QJUiAwLy10JTDRgxoO+xPXQkM ZEYt2xXZRQkFTzdLciJwA7HRH6l6Wq+U6qgmuiUpf1CablAimiw= =wTkm -----END PGP SIGNATURE----- --=-=-=--