From: Greg Kroah-Hartman <gregkh@linuxfoundation•org>
To: Mike Rapoport <rppt@linux•ibm.com>
Cc: Rich Felker <dalias@libc•org>,
linux-ia64@vger•kernel.org, devicetree@vger•kernel.org,
Catalin Marinas <catalin.marinas@arm•com>,
Heiko Carstens <heiko.carstens@de•ibm.com>,
x86@kernel•org, linux-mips@vger•kernel.org,
Max Filippov <jcmvbkbc@gmail•com>, Guo Ren <guoren@kernel•org>,
sparclinux@vger•kernel.org, Christoph Hellwig <hch@lst•de>,
linux-s390@vger•kernel.org, linux-c6x-dev@linux-c6x•org,
Yoshinori Sato <ysato@users•sourceforge.jp>,
Richard Weinberger <richard@nod•at>,
linux-sh@vger•kernel.org, Russell King <linux@armlinux•org.uk>,
kasan-dev@googlegroups•com,
Geert Uytterhoeven <geert@linux-m68k•org>,
Mark Salter <msalter@redhat•com>, Dennis Zhou <dennis@kernel•org>,
Matt Turner <mattst88@gmail•com>,
linux-snps-arc@lists•infradead.org,
uclinux-h8-devel@lists•sourceforge.jp,
Petr Mladek <pmladek@suse•com>,
linux-xtensa@linux-xtensa•org, linux-alpha@vger•kernel.org,
linux-um@lists•infradead.org, linux-m68k@lists•linux-m68k.org,
Rob Herring <robh+dt@kernel•org>,
Greentime Hu <green.hu@gmail•com>,
xen-devel@lists•xenproject.org, Stafford Horne <shorne@gmail•com>,
Guan Xuetao <gxt@pku•edu.cn>,
linux-arm-kernel@lists•infradead.org,
Michal Simek <monstr@monstr•eu>, Tony Luck <tony.luck@intel•com>,
linux-mm@kvack•org, Vineet Gupta <vgupta@synopsys•com>,
linux-usb@vger•kernel.org, linux-kernel@vger•kernel.org,
Paul Burton <paul.burton@mips•com>,
openrisc@lists•librecores.org,
Andrew Morton <akpm@linux-foundation•org>,
linuxppc-dev@lists•ozlabs.org,
"David S. Miller" <davem@davemloft•net>
Subject: Re: [PATCH 21/21] memblock: drop memblock_alloc_*_nopanic() variants
Date: Fri, 18 Jan 2019 09:42:30 +0100 [thread overview]
Message-ID: <20190118084230.GA8855@kroah.com> (raw)
In-Reply-To: <1547646261-32535-22-git-send-email-rppt@linux.ibm.com>
On Wed, Jan 16, 2019 at 03:44:21PM +0200, Mike Rapoport wrote:
> As all the memblock allocation functions return NULL in case of error
> rather than panic(), the duplicates with _nopanic suffix can be removed.
>
> Signed-off-by: Mike Rapoport <rppt@linux•ibm.com>
> ---
> arch/arc/kernel/unwind.c | 3 +--
> arch/sh/mm/init.c | 2 +-
> arch/x86/kernel/setup_percpu.c | 10 +++++-----
> arch/x86/mm/kasan_init_64.c | 14 ++++++++------
> drivers/firmware/memmap.c | 2 +-
> drivers/usb/early/xhci-dbc.c | 2 +-
> include/linux/memblock.h | 35 -----------------------------------
> kernel/dma/swiotlb.c | 2 +-
> kernel/printk/printk.c | 17 +++++++----------
> mm/memblock.c | 35 -----------------------------------
> mm/page_alloc.c | 10 +++++-----
> mm/page_ext.c | 2 +-
> mm/percpu.c | 11 ++++-------
> mm/sparse.c | 6 ++----
> 14 files changed, 37 insertions(+), 114 deletions(-)
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation•org>
prev parent reply other threads:[~2019-01-18 8:44 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 13:44 [PATCH 00/21] Refine memblock API Mike Rapoport
2019-01-16 13:44 ` [PATCH 01/21] openrisc: prefer memblock APIs returning virtual address Mike Rapoport
2019-01-16 13:44 ` [PATCH 02/21] powerpc: use memblock functions " Mike Rapoport
2019-01-16 13:44 ` [PATCH 03/21] memblock: replace memblock_alloc_base(ANYWHERE) with memblock_phys_alloc Mike Rapoport
2019-01-16 13:44 ` [PATCH 04/21] memblock: drop memblock_alloc_base_nid() Mike Rapoport
2019-01-16 13:44 ` [PATCH 05/21] memblock: emphasize that memblock_alloc_range() returns a physical address Mike Rapoport
2019-01-16 13:44 ` [PATCH 06/21] memblock: memblock_phys_alloc_try_nid(): don't panic Mike Rapoport
2019-01-16 13:44 ` [PATCH 07/21] memblock: memblock_phys_alloc(): " Mike Rapoport
2019-01-16 13:44 ` [PATCH 08/21] memblock: drop __memblock_alloc_base() Mike Rapoport
2019-01-16 15:15 ` Rob Herring
2019-01-16 13:44 ` [PATCH 09/21] memblock: drop memblock_alloc_base() Mike Rapoport
2019-01-16 13:44 ` [PATCH 10/21] memblock: refactor internal allocation functions Mike Rapoport
2019-01-16 13:44 ` [PATCH 11/21] memblock: make memblock_find_in_range_node() and choose_memblock_flags() static Mike Rapoport
2019-01-16 13:44 ` [PATCH 12/21] arch: use memblock_alloc() instead of memblock_alloc_from(size, align, 0) Mike Rapoport
2019-01-18 17:53 ` Paul Burton
2019-01-16 13:44 ` [PATCH 13/21] arch: don't memset(0) memory returned by memblock_alloc() Mike Rapoport
2019-01-16 14:17 ` Geert Uytterhoeven
2019-01-16 13:44 ` [PATCH 14/21] ia64: add checks for the return value of memblock_alloc*() Mike Rapoport
2019-01-16 13:44 ` [PATCH 15/21] sparc: " Mike Rapoport
2019-01-16 17:21 ` David Miller
2019-01-16 13:44 ` [PATCH 16/21] mm/percpu: " Mike Rapoport
2019-01-16 13:44 ` [PATCH 17/21] init/main: " Mike Rapoport
2019-01-16 13:44 ` [PATCH 18/21] swiotlb: " Mike Rapoport
2019-01-16 13:44 ` [PATCH 19/21] treewide: " Mike Rapoport
2019-01-16 14:27 ` Geert Uytterhoeven
2019-01-16 15:13 ` Mike Rapoport
2019-01-16 14:32 ` [Xen-devel] " Juergen Gross
2019-01-16 15:18 ` Rob Herring
2019-01-17 7:06 ` Guo Ren
2019-01-18 8:43 ` Heiko Carstens
2019-01-18 18:02 ` Paul Burton
2019-01-16 13:44 ` [PATCH 20/21] memblock: memblock_alloc_try_nid: don't panic Mike Rapoport
2019-01-16 13:44 ` [PATCH 21/21] memblock: drop memblock_alloc_*_nopanic() variants Mike Rapoport
2019-01-17 9:28 ` Petr Mladek
2019-01-18 8:42 ` Greg Kroah-Hartman [this message]
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=20190118084230.GA8855@kroah.com \
--to=gregkh@linuxfoundation$(echo .)org \
--cc=akpm@linux-foundation$(echo .)org \
--cc=catalin.marinas@arm$(echo .)com \
--cc=dalias@libc$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=dennis@kernel$(echo .)org \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=geert@linux-m68k$(echo .)org \
--cc=green.hu@gmail$(echo .)com \
--cc=guoren@kernel$(echo .)org \
--cc=gxt@pku$(echo .)edu.cn \
--cc=hch@lst$(echo .)de \
--cc=heiko.carstens@de$(echo .)ibm.com \
--cc=jcmvbkbc@gmail$(echo .)com \
--cc=kasan-dev@googlegroups$(echo .)com \
--cc=linux-alpha@vger$(echo .)kernel.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-c6x-dev@linux-c6x$(echo .)org \
--cc=linux-ia64@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-m68k@lists$(echo .)linux-m68k.org \
--cc=linux-mips@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=linux-s390@vger$(echo .)kernel.org \
--cc=linux-sh@vger$(echo .)kernel.org \
--cc=linux-snps-arc@lists$(echo .)infradead.org \
--cc=linux-um@lists$(echo .)infradead.org \
--cc=linux-usb@vger$(echo .)kernel.org \
--cc=linux-xtensa@linux-xtensa$(echo .)org \
--cc=linux@armlinux$(echo .)org.uk \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mattst88@gmail$(echo .)com \
--cc=monstr@monstr$(echo .)eu \
--cc=msalter@redhat$(echo .)com \
--cc=openrisc@lists$(echo .)librecores.org \
--cc=paul.burton@mips$(echo .)com \
--cc=pmladek@suse$(echo .)com \
--cc=richard@nod$(echo .)at \
--cc=robh+dt@kernel$(echo .)org \
--cc=rppt@linux$(echo .)ibm.com \
--cc=shorne@gmail$(echo .)com \
--cc=sparclinux@vger$(echo .)kernel.org \
--cc=tony.luck@intel$(echo .)com \
--cc=uclinux-h8-devel@lists$(echo .)sourceforge.jp \
--cc=vgupta@synopsys$(echo .)com \
--cc=x86@kernel$(echo .)org \
--cc=xen-devel@lists$(echo .)xenproject.org \
--cc=ysato@users$(echo .)sourceforge.jp \
/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