From: Joe Perches <joe@perches•com>
To: Shea Levy <shea@shealevy•com>,
linux-riscv@lists•infradead.org, linux-kernel@vger•kernel.org
Cc: Benjamin Herrenschmidt <benh@kernel•crashing.org>,
Paul Mackerras <paulus@samba•org>,
Michael Ellerman <mpe@ellerman•id.au>,
Michal Hocko <mhocko@suse•com>, Vlastimil Babka <vbabka@suse•cz>,
Andrew Morton <akpm@linux-foundation•org>,
Dan Williams <dan.j.williams@intel•com>,
Christophe Leroy <christophe.leroy@c-s•fr>,
Oliver O'Halloran <oohall@gmail•com>,
linuxppc-dev@lists•ozlabs.org
Subject: Re: [PATCH v4 14/16] powerpc: Use generic free_initrd_mem.
Date: Wed, 28 Mar 2018 13:44:13 -0700 [thread overview]
Message-ID: <1522269853.12357.135.camel@perches.com> (raw)
In-Reply-To: <20180328203659.18692-15-shea@shealevy.com>
On Wed, 2018-03-28 at 16:36 -0400, Shea Levy wrote:
> Signed-off-by: Shea Levy <shea@shealevy•com>
Most people seem to want some form of commit message
and not just your sign-off.
And btw:
It seems you used get_maintainer to determine who to
send these patches to.
I suggest you add --nogit and --nogit-fallback to the
get_maintainer command line you use to avoid sending
these patches to people like me that have done drive-by
cleanup work on these files.
next prev parent reply other threads:[~2018-03-28 20:44 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-24 17:44 [PATCH 00/16] Generic infrastructure for unloading initramfs Shea Levy
2018-03-24 17:44 ` [PATCH 01/16] initrd: Add generic code path for common initrd unloading logic Shea Levy
2018-03-25 17:17 ` LEROY Christophe
2018-03-25 22:20 ` Shea Levy
2018-03-28 12:04 ` Christoph Hellwig
2018-03-28 12:23 ` Geert Uytterhoeven
2018-03-24 17:44 ` [PATCH 02/16] riscv: Use INITRAMFS_GENERIC_UNLOAD Shea Levy
2018-03-24 17:44 ` [PATCH 03/16] alpha: " Shea Levy
2018-03-24 17:44 ` [PATCH 04/16] arc: " Shea Levy
2018-03-24 17:44 ` [PATCH 05/16] c6x: " Shea Levy
2018-03-24 17:44 ` [PATCH 06/16] frv: " Shea Levy
2018-03-24 17:44 ` [PATCH 07/16] h8300: " Shea Levy
2018-03-24 17:44 ` [PATCH 08/16] m32r: " Shea Levy
2018-03-24 17:44 ` [PATCH 09/16] m68k: " Shea Levy
2018-03-24 17:44 ` [PATCH 10/16] microblaze: " Shea Levy
2018-03-24 17:44 ` [PATCH 11/16] nios2: " Shea Levy
2018-03-24 17:44 ` [PATCH 12/16] openrisc: " Shea Levy
2018-03-24 17:44 ` [PATCH 13/16] parisc: " Shea Levy
2018-03-24 17:44 ` [PATCH 14/16] powerpc: " Shea Levy
2018-03-24 17:44 ` [PATCH 15/16] sh: " Shea Levy
2018-03-24 17:44 ` [PATCH 16/16] um: " Shea Levy
2018-03-25 22:18 ` [PATCH v2 00/16] Generic infrastructure for unloading initramfs Shea Levy
2018-03-25 22:18 ` [PATCH v2 01/16] initrd: Add generic code path for common initrd unloading logic Shea Levy
2018-03-25 22:18 ` [PATCH v2 02/16] riscv: Use INITRAMFS_GENERIC_UNLOAD Shea Levy
2018-03-26 0:41 ` Palmer Dabbelt
2018-03-26 0:55 ` Shea Levy
2018-03-25 22:18 ` [PATCH v2 03/16] alpha: " Shea Levy
2018-03-25 22:18 ` [PATCH v2 04/16] arc: " Shea Levy
2018-03-25 22:18 ` [PATCH v2 05/16] c6x: " Shea Levy
2018-03-25 22:18 ` [PATCH v2 06/16] frv: " Shea Levy
2018-03-25 22:18 ` [PATCH v2 07/16] h8300: " Shea Levy
2018-03-25 22:18 ` [PATCH v2 08/16] m32r: " Shea Levy
2018-03-25 22:18 ` [PATCH v2 09/16] m68k: " Shea Levy
2018-03-25 22:18 ` [PATCH v2 10/16] microblaze: " Shea Levy
2018-03-25 22:18 ` [PATCH v2 11/16] nios2: " Shea Levy
2018-03-25 22:18 ` [PATCH v2 12/16] openrisc: " Shea Levy
2018-03-25 22:18 ` [PATCH v2 13/16] parisc: " Shea Levy
2018-03-25 22:18 ` [PATCH v2 14/16] powerpc: " Shea Levy
2018-03-25 22:18 ` [PATCH v2 15/16] sh: " Shea Levy
2018-03-25 22:18 ` [PATCH v2 16/16] um: " Shea Levy
2018-03-28 15:26 ` [PATCH] Extract initrd free logic from arch-specific code Shea Levy
2018-03-28 15:58 ` Rob Landley
2018-03-28 16:04 ` Shea Levy
2018-03-28 16:48 ` Russell King - ARM Linux
2018-03-28 19:04 ` Rob Landley
2018-03-28 22:14 ` Russell King - ARM Linux
2018-03-28 22:37 ` Oliver
2018-03-29 0:23 ` Nicholas Piggin
2018-03-29 15:27 ` Russell King - ARM Linux
2018-03-29 15:43 ` Geert Uytterhoeven
2018-03-29 15:58 ` Russell King - ARM Linux
2018-03-29 16:53 ` Marc Zyngier
2018-03-29 17:32 ` Russell King - ARM Linux
2018-03-29 17:53 ` Marc Zyngier
2018-03-29 17:43 ` Rob Landley
2018-03-29 16:39 ` Rob Landley
2018-03-29 17:31 ` Russell King - ARM Linux
2018-03-28 16:55 ` Kees Cook
2018-03-29 1:12 ` Wei Yang
[not found] ` <20180328203659.18692-1-shea@shealevy.com>
2018-03-28 20:36 ` [PATCH v4 14/16] powerpc: Use generic free_initrd_mem Shea Levy
2018-03-28 20:44 ` Joe Perches [this message]
2018-03-28 20:53 ` Shea Levy
2018-03-29 13:19 ` Michael Ellerman
2018-04-01 15:01 ` Shea Levy
[not found] ` <20180329113207.30674-1-shea@shealevy.com>
2018-03-29 11:32 ` [PATCH v5 14/16] powerpc: Switch to " Shea Levy
[not found] ` <20180401145931.7932-1-shea@shealevy.com>
2018-04-01 14:59 ` [PATCH v6 " Shea Levy
2018-03-30 1:43 ` [PATCH] Extract initrd free logic from arch-specific code kbuild test robot
2018-03-30 3:16 ` kbuild test robot
2018-03-30 11:15 ` Ingo Molnar
2018-04-01 15:05 ` Shea Levy
2018-04-02 5:59 ` Ingo Molnar
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=1522269853.12357.135.camel@perches.com \
--to=joe@perches$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=benh@kernel$(echo .)crashing.org \
--cc=christophe.leroy@c-s$(echo .)fr \
--cc=dan.j.williams@intel$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-riscv@lists$(echo .)infradead.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mhocko@suse$(echo .)com \
--cc=mpe@ellerman$(echo .)id.au \
--cc=oohall@gmail$(echo .)com \
--cc=paulus@samba$(echo .)org \
--cc=shea@shealevy$(echo .)com \
--cc=vbabka@suse$(echo .)cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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