From: Adam Ford <aford173@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Rich Felker <dalias@libc.org>,
linux-ia64@vger.kernel.org, linux-sh@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-mips@vger.kernel.org, Max Filippov <jcmvbkbc@gmail.com>,
devicetree <devicetree@vger.kernel.org>,
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>,
x86@kernel.org, Russell King <linux@armlinux.org.uk>,
kasan-dev <kasan-dev@googlegroups.com>,
Mike Rapoport <rppt@linux.ibm.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,
Chris Healy <cphealy@gmail.com>,
uclinux-h8-devel@lists.sourceforge.jp
Subject: Re: [PATCH v2 00/21] Refine memblock API
Date: Thu, 26 Sep 2019 08:09:52 -0500 [thread overview]
Message-ID: <CAHCN7xJ32BYZu-DVTVLSzv222U50JDb8F0A_tLDERbb8kPdRxg@mail.gmail.com> (raw)
In-Reply-To: <CAOMZO5D2uzR6Sz1QnX3G-Ce_juxU-0PO_vBZX+nR1mpQB8s8-w@mail.gmail.com>
On Wed, Sep 25, 2019 at 10:17 AM Fabio Estevam <festevam@gmail.com> wrote:
>
> On Wed, Sep 25, 2019 at 9:17 AM Adam Ford <aford173@gmail.com> wrote:
>
> > I tried cma=256M and noticed the cma dump at the beginning didn't
> > change. Do we need to setup a reserved-memory node like
> > imx6ul-ccimx6ulsom.dtsi did?
>
> I don't think so.
>
> Were you able to identify what was the exact commit that caused such regression?
I was able to narrow it down the 92d12f9544b7 ("memblock: refactor
internal allocation functions") that caused the regression with
Etnaviv.
I also noticed that if I create a reserved memory node as was done one
imx6ul-ccimx6ulsom.dtsi the 3D seems to work again, but without it, I
was getting errors regardless of the 'cma=256M' or not.
I don't have a problem using the reserved memory, but I guess I am not
sure what the amount should be. I know for the video decoding 1080p,
I have historically used cma=128M, but with the 3D also needing some
memory allocation, is that enough or should I use 256M?
adam
WARNING: multiple messages have this Message-ID (diff)
From: Adam Ford <aford173@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Mike Rapoport <rppt@linux.ibm.com>, Rich Felker <dalias@libc.org>,
linux-ia64@vger.kernel.org, Petr Mladek <pmladek@suse.com>,
linux-sh@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Max Filippov <jcmvbkbc@gmail.com>, Guo Ren <guoren@kernel.org>,
Michael Ellerman <mpe@ellerman.id.au>,
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>,
x86@kernel.org, Russell King <linux@armlinux.org.uk>,
kasan-dev <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,
devicetree <devicetree@vger.kernel.org>,
linux-xtensa@linux-xtensa.org, linux-um@lists.infradead.org,
The etnaviv authors <etnaviv@lists.freedesktop.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>,
arm-soc <linux-arm-kernel@lists.infradead.org>,
Michal Simek <monstr@monstr.eu>, Tony Luck <tony.luck@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
USB list <linux-usb@vger.kernel.org>,
linux-mips@vger.kernel.org, Paul Burton <paul.burton@mips.com>,
Vineet Gupta <vgupta@synopsys.com>,
linux-alpha@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linuxppc-dev@lists.ozlabs.org,
"David S. Miller" <davem@davemloft.net>,
openrisc@lists.librecores.org, Chris Healy <cphealy@gmail.com>
Subject: Re: [PATCH v2 00/21] Refine memblock API
Date: Thu, 26 Sep 2019 08:09:52 -0500 [thread overview]
Message-ID: <CAHCN7xJ32BYZu-DVTVLSzv222U50JDb8F0A_tLDERbb8kPdRxg@mail.gmail.com> (raw)
In-Reply-To: <CAOMZO5D2uzR6Sz1QnX3G-Ce_juxU-0PO_vBZX+nR1mpQB8s8-w@mail.gmail.com>
On Wed, Sep 25, 2019 at 10:17 AM Fabio Estevam <festevam@gmail.com> wrote:
>
> On Wed, Sep 25, 2019 at 9:17 AM Adam Ford <aford173@gmail.com> wrote:
>
> > I tried cma=256M and noticed the cma dump at the beginning didn't
> > change. Do we need to setup a reserved-memory node like
> > imx6ul-ccimx6ulsom.dtsi did?
>
> I don't think so.
>
> Were you able to identify what was the exact commit that caused such regression?
I was able to narrow it down the 92d12f9544b7 ("memblock: refactor
internal allocation functions") that caused the regression with
Etnaviv.
I also noticed that if I create a reserved memory node as was done one
imx6ul-ccimx6ulsom.dtsi the 3D seems to work again, but without it, I
was getting errors regardless of the 'cma=256M' or not.
I don't have a problem using the reserved memory, but I guess I am not
sure what the amount should be. I know for the video decoding 1080p,
I have historically used cma=128M, but with the 3D also needing some
memory allocation, is that enough or should I use 256M?
adam
WARNING: multiple messages have this Message-ID (diff)
From: Adam Ford <aford173@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Rich Felker <dalias@libc.org>,
linux-ia64@vger.kernel.org, linux-sh@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-mips@vger.kernel.org, Max Filippov <jcmvbkbc@gmail.com>,
devicetree <devicetree@vger.kernel.org>,
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>,
x86@kernel.org, Russell King <linux@armlinux.org.uk>,
kasan-dev <kasan-dev@googlegroups.com>,
Mike Rapoport <rppt@linux.ibm.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,
Chris Healy <cphealy@gmail.com>,
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,
The etnaviv authors <etnaviv@lists.freedesktop.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>,
arm-soc <linux-arm-kernel@lists.infradead.org>,
Michal Simek <monstr@monstr.eu>, Tony Luck <tony.luck@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
USB list <linux-usb@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Paul Burton <paul.burton@mips.com>,
Vineet Gupta <vgupta@synopsys.com>,
Andrew Morton <akpm@linux-foundation.org>,
linuxppc-dev@lists.ozlabs.org,
"David S. Miller" <davem@davemloft.net>,
openrisc@lists.librecores.org
Subject: Re: [PATCH v2 00/21] Refine memblock API
Date: Thu, 26 Sep 2019 08:09:52 -0500 [thread overview]
Message-ID: <CAHCN7xJ32BYZu-DVTVLSzv222U50JDb8F0A_tLDERbb8kPdRxg@mail.gmail.com> (raw)
In-Reply-To: <CAOMZO5D2uzR6Sz1QnX3G-Ce_juxU-0PO_vBZX+nR1mpQB8s8-w@mail.gmail.com>
On Wed, Sep 25, 2019 at 10:17 AM Fabio Estevam <festevam@gmail.com> wrote:
>
> On Wed, Sep 25, 2019 at 9:17 AM Adam Ford <aford173@gmail.com> wrote:
>
> > I tried cma=256M and noticed the cma dump at the beginning didn't
> > change. Do we need to setup a reserved-memory node like
> > imx6ul-ccimx6ulsom.dtsi did?
>
> I don't think so.
>
> Were you able to identify what was the exact commit that caused such regression?
I was able to narrow it down the 92d12f9544b7 ("memblock: refactor
internal allocation functions") that caused the regression with
Etnaviv.
I also noticed that if I create a reserved memory node as was done one
imx6ul-ccimx6ulsom.dtsi the 3D seems to work again, but without it, I
was getting errors regardless of the 'cma=256M' or not.
I don't have a problem using the reserved memory, but I guess I am not
sure what the amount should be. I know for the video decoding 1080p,
I have historically used cma=128M, but with the 3D also needing some
memory allocation, is that enough or should I use 256M?
adam
WARNING: multiple messages have this Message-ID (diff)
From: aford173@gmail.com (Adam Ford)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH v2 00/21] Refine memblock API
Date: Thu, 26 Sep 2019 08:09:52 -0500 [thread overview]
Message-ID: <CAHCN7xJ32BYZu-DVTVLSzv222U50JDb8F0A_tLDERbb8kPdRxg@mail.gmail.com> (raw)
In-Reply-To: <CAOMZO5D2uzR6Sz1QnX3G-Ce_juxU-0PO_vBZX+nR1mpQB8s8-w@mail.gmail.com>
On Wed, Sep 25, 2019@10:17 AM Fabio Estevam <festevam@gmail.com> wrote:
>
> On Wed, Sep 25, 2019@9:17 AM Adam Ford <aford173@gmail.com> wrote:
>
> > I tried cma=256M and noticed the cma dump at the beginning didn't
> > change. Do we need to setup a reserved-memory node like
> > imx6ul-ccimx6ulsom.dtsi did?
>
> I don't think so.
>
> Were you able to identify what was the exact commit that caused such regression?
I was able to narrow it down the 92d12f9544b7 ("memblock: refactor
internal allocation functions") that caused the regression with
Etnaviv.
I also noticed that if I create a reserved memory node as was done one
imx6ul-ccimx6ulsom.dtsi the 3D seems to work again, but without it, I
was getting errors regardless of the 'cma=256M' or not.
I don't have a problem using the reserved memory, but I guess I am not
sure what the amount should be. I know for the video decoding 1080p,
I have historically used cma=128M, but with the 3D also needing some
memory allocation, is that enough or should I use 256M?
adam
WARNING: multiple messages have this Message-ID (diff)
From: Adam Ford <aford173@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Rich Felker <dalias@libc.org>,
linux-ia64@vger.kernel.org, linux-sh@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-mips@vger.kernel.org, Max Filippov <jcmvbkbc@gmail.com>,
devicetree <devicetree@vger.kernel.org>,
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>,
x86@kernel.org, Russell King <linux@armlinux.org.uk>,
kasan-dev <kasan-dev@googlegroups.com>,
Mike Rapoport <rppt@linux.ibm.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,
Chris Healy <cphealy@gmail.com>,
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,
The etnaviv authors <etnaviv@lists.freedesktop.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>,
arm-soc <linux-arm-kernel@lists.infradead.org>,
Michal Simek <monstr@monstr.eu>, Tony Luck <tony.luck@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
USB list <linux-usb@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Paul Burton <paul.burton@mips.com>,
Vineet Gupta <vgupta@synopsys.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Andrew Morton <akpm@linux-foundation.org>,
linuxppc-dev@lists.ozlabs.org,
"David S. Miller" <davem@davemloft.net>,
openrisc@lists.librecores.org
Subject: Re: [Xen-devel] [PATCH v2 00/21] Refine memblock API
Date: Thu, 26 Sep 2019 08:09:52 -0500 [thread overview]
Message-ID: <CAHCN7xJ32BYZu-DVTVLSzv222U50JDb8F0A_tLDERbb8kPdRxg@mail.gmail.com> (raw)
In-Reply-To: <CAOMZO5D2uzR6Sz1QnX3G-Ce_juxU-0PO_vBZX+nR1mpQB8s8-w@mail.gmail.com>
On Wed, Sep 25, 2019 at 10:17 AM Fabio Estevam <festevam@gmail.com> wrote:
>
> On Wed, Sep 25, 2019 at 9:17 AM Adam Ford <aford173@gmail.com> wrote:
>
> > I tried cma=256M and noticed the cma dump at the beginning didn't
> > change. Do we need to setup a reserved-memory node like
> > imx6ul-ccimx6ulsom.dtsi did?
>
> I don't think so.
>
> Were you able to identify what was the exact commit that caused such regression?
I was able to narrow it down the 92d12f9544b7 ("memblock: refactor
internal allocation functions") that caused the regression with
Etnaviv.
I also noticed that if I create a reserved memory node as was done one
imx6ul-ccimx6ulsom.dtsi the 3D seems to work again, but without it, I
was getting errors regardless of the 'cma=256M' or not.
I don't have a problem using the reserved memory, but I guess I am not
sure what the amount should be. I know for the video decoding 1080p,
I have historically used cma=128M, but with the 3D also needing some
memory allocation, is that enough or should I use 256M?
adam
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: Adam Ford <aford173@gmail.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH v2 00/21] Refine memblock API
Date: Thu, 26 Sep 2019 08:09:52 -0500 [thread overview]
Message-ID: <CAHCN7xJ32BYZu-DVTVLSzv222U50JDb8F0A_tLDERbb8kPdRxg@mail.gmail.com> (raw)
In-Reply-To: <CAOMZO5D2uzR6Sz1QnX3G-Ce_juxU-0PO_vBZX+nR1mpQB8s8-w@mail.gmail.com>
On Wed, Sep 25, 2019 at 10:17 AM Fabio Estevam <festevam@gmail.com> wrote:
>
> On Wed, Sep 25, 2019 at 9:17 AM Adam Ford <aford173@gmail.com> wrote:
>
> > I tried cma=256M and noticed the cma dump at the beginning didn't
> > change. Do we need to setup a reserved-memory node like
> > imx6ul-ccimx6ulsom.dtsi did?
>
> I don't think so.
>
> Were you able to identify what was the exact commit that caused such regression?
I was able to narrow it down the 92d12f9544b7 ("memblock: refactor
internal allocation functions") that caused the regression with
Etnaviv.
I also noticed that if I create a reserved memory node as was done one
imx6ul-ccimx6ulsom.dtsi the 3D seems to work again, but without it, I
was getting errors regardless of the 'cma=256M' or not.
I don't have a problem using the reserved memory, but I guess I am not
sure what the amount should be. I know for the video decoding 1080p,
I have historically used cma=128M, but with the 3D also needing some
memory allocation, is that enough or should I use 256M?
adam
next prev parent reply other threads:[~2019-09-26 13:09 UTC|newest]
Thread overview: 470+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 8:03 [PATCH v2 00/21] Refine memblock API Mike Rapoport
2019-01-21 8:03 ` [OpenRISC] " Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` [PATCH v2 01/21] openrisc: prefer memblock APIs returning virtual address Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` [OpenRISC] " Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` [v2,01/21] " Mike Rapoport
2019-01-21 8:03 ` [PATCH v2 01/21] " Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-27 3:07 ` Stafford Horne
2019-01-27 3:07 ` Stafford Horne
2019-01-27 3:07 ` [OpenRISC] " Stafford Horne
2019-01-27 3:07 ` Stafford Horne
2019-01-27 3:07 ` Stafford Horne
2019-01-27 3:07 ` [v2,01/21] " Stafford Horne
2019-01-27 3:07 ` [PATCH v2 01/21] " Stafford Horne
2019-01-27 3:07 ` Stafford Horne
2019-01-27 3:07 ` Stafford Horne
2019-01-21 8:03 ` [PATCH v2 02/21] powerpc: use memblock functions " Mike Rapoport
2019-01-21 8:03 ` [OpenRISC] " Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` [v2,02/21] " Mike Rapoport
2019-01-21 8:03 ` [PATCH v2 02/21] " Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-29 9:52 ` Michael Ellerman
2019-01-29 9:52 ` [OpenRISC] " Michael Ellerman
2019-01-29 9:52 ` Michael Ellerman
2019-01-29 9:52 ` Michael Ellerman
2019-01-29 9:52 ` [v2,02/21] " Michael Ellerman
2019-01-29 9:52 ` [PATCH v2 02/21] " Michael Ellerman
2019-01-29 9:52 ` Michael Ellerman
2019-01-29 9:52 ` Michael Ellerman
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` [PATCH v2 03/21] memblock: replace memblock_alloc_base(ANYWHERE) with memblock_phys_alloc Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` [OpenRISC] " Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` [v2,03/21] " Mike Rapoport
2019-01-21 8:03 ` [PATCH v2 03/21] " Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` [PATCH v2 04/21] memblock: drop memblock_alloc_base_nid() Mike Rapoport
2019-01-21 8:03 ` [OpenRISC] " Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` [v2,04/21] " Mike Rapoport
2019-01-21 8:03 ` [PATCH v2 04/21] " Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` [PATCH v2 05/21] memblock: emphasize that memblock_alloc_range() returns a physical address Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` [OpenRISC] " Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` [v2,05/21] " Mike Rapoport
2019-01-21 8:03 ` [PATCH v2 05/21] " Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` [PATCH v2 06/21] memblock: memblock_phys_alloc_try_nid(): don't panic Mike Rapoport
2019-01-21 8:03 ` [OpenRISC] " Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` [v2,06/21] " Mike Rapoport
2019-01-21 8:03 ` [PATCH v2 06/21] " Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-25 17:45 ` Catalin Marinas
2019-01-25 17:45 ` Catalin Marinas
2019-01-25 17:45 ` [OpenRISC] " Catalin Marinas
2019-01-25 17:45 ` Catalin Marinas
2019-01-25 17:45 ` Catalin Marinas
2019-01-25 17:45 ` [v2,06/21] " Catalin Marinas
2019-01-25 17:45 ` [PATCH v2 06/21] " Catalin Marinas
2019-01-25 17:45 ` Catalin Marinas
2019-01-25 17:45 ` Catalin Marinas
2019-01-25 19:32 ` Mike Rapoport
2019-01-25 19:32 ` [OpenRISC] " Mike Rapoport
2019-01-25 19:32 ` Mike Rapoport
2019-01-25 19:32 ` Mike Rapoport
2019-01-25 19:32 ` [v2,06/21] " Mike Rapoport
2019-01-25 19:32 ` [PATCH v2 06/21] " Mike Rapoport
2019-01-25 19:32 ` Mike Rapoport
2019-01-25 19:32 ` Mike Rapoport
2019-01-25 19:32 ` Mike Rapoport
2019-01-29 9:56 ` Michael Ellerman
2019-01-29 9:56 ` Michael Ellerman
2019-01-29 9:56 ` [OpenRISC] " Michael Ellerman
2019-01-29 9:56 ` Michael Ellerman
2019-01-29 9:56 ` Michael Ellerman
2019-01-29 9:56 ` Michael Ellerman
2019-01-29 9:56 ` [v2,06/21] " Michael Ellerman
2019-01-29 9:56 ` [PATCH v2 06/21] " Michael Ellerman
2019-01-29 9:56 ` Michael Ellerman
2019-01-29 9:56 ` Michael Ellerman
2019-01-29 9:58 ` Michael Ellerman
2019-01-29 9:58 ` Michael Ellerman
2019-01-29 9:58 ` [OpenRISC] " Michael Ellerman
2019-01-29 9:58 ` Michael Ellerman
2019-01-29 9:58 ` Michael Ellerman
2019-01-29 9:58 ` Michael Ellerman
2019-01-29 9:58 ` [v2,06/21] " Michael Ellerman
2019-01-29 9:58 ` [PATCH v2 06/21] " Michael Ellerman
2019-01-29 9:58 ` Michael Ellerman
2019-01-29 9:58 ` Michael Ellerman
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` [PATCH v2 07/21] memblock: memblock_phys_alloc(): " Mike Rapoport
2019-01-21 8:03 ` [OpenRISC] " Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` [v2,07/21] " Mike Rapoport
2019-01-21 8:03 ` [PATCH v2 07/21] " Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` [PATCH v2 08/21] memblock: drop __memblock_alloc_base() Mike Rapoport
2019-01-21 8:03 ` [OpenRISC] " Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` [v2,08/21] " Mike Rapoport
2019-01-21 8:03 ` [PATCH v2 08/21] " Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` [PATCH v2 09/21] memblock: drop memblock_alloc_base() Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` [OpenRISC] " Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` [v2,09/21] " Mike Rapoport
2019-01-21 8:03 ` [PATCH v2 09/21] " Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-29 10:29 ` Michael Ellerman
2019-01-29 10:29 ` [OpenRISC] " Michael Ellerman
2019-01-29 10:29 ` Michael Ellerman
2019-01-29 10:29 ` Michael Ellerman
2019-01-29 10:29 ` Michael Ellerman
2019-01-29 10:29 ` [v2,09/21] " Michael Ellerman
2019-01-29 10:29 ` [PATCH v2 09/21] " Michael Ellerman
2019-01-29 10:29 ` Michael Ellerman
2019-01-29 10:29 ` Michael Ellerman
2019-01-29 10:29 ` Michael Ellerman
2019-01-21 8:03 ` [PATCH v2 10/21] memblock: refactor internal allocation functions Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` [OpenRISC] " Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` [v2,10/21] " Mike Rapoport
2019-01-21 8:03 ` [PATCH v2 10/21] " Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-02-03 9:39 ` Michael Ellerman
2019-02-03 9:39 ` Michael Ellerman
2019-02-03 9:39 ` [OpenRISC] " Michael Ellerman
2019-02-03 9:39 ` Michael Ellerman
2019-02-03 9:39 ` Michael Ellerman
2019-02-03 9:39 ` Michael Ellerman
2019-02-03 9:39 ` [v2,10/21] " Michael Ellerman
2019-02-03 9:39 ` [PATCH v2 10/21] " Michael Ellerman
2019-02-03 9:39 ` Michael Ellerman
2019-02-03 9:39 ` Michael Ellerman
2019-02-03 10:04 ` Mike Rapoport
2019-02-03 10:04 ` [OpenRISC] " Mike Rapoport
2019-02-03 10:04 ` Mike Rapoport
2019-02-03 10:04 ` Mike Rapoport
2019-02-03 10:04 ` [v2,10/21] " Mike Rapoport
2019-02-03 10:04 ` [PATCH v2 10/21] " Mike Rapoport
2019-02-03 10:04 ` Mike Rapoport
2019-02-03 10:04 ` Mike Rapoport
2019-02-03 10:04 ` Mike Rapoport
2019-02-03 11:39 ` Mike Rapoport
2019-02-03 11:39 ` Mike Rapoport
2019-02-04 8:45 ` Michael Ellerman
2019-02-04 8:45 ` Michael Ellerman
2019-02-04 23:08 ` Stephen Rothwell
2019-02-04 23:08 ` Stephen Rothwell
2019-01-21 8:03 ` [PATCH v2 11/21] memblock: make memblock_find_in_range_node() and choose_memblock_flags() static Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` [OpenRISC] " Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` [v2,11/21] " Mike Rapoport
2019-01-21 8:03 ` [PATCH v2 11/21] " Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` [PATCH v2 12/21] arch: use memblock_alloc() instead of memblock_alloc_from(size, align, 0) Mike Rapoport
2019-01-21 8:03 ` [OpenRISC] " Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` [v2,12/21] " Mike Rapoport
2019-01-21 8:03 ` [PATCH v2 12/21] " Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:03 ` Mike Rapoport
2019-01-21 8:04 ` [PATCH v2 13/21] arch: don't memset(0) memory returned by memblock_alloc() Mike Rapoport
2019-01-21 8:04 ` [OpenRISC] " Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` [v2,13/21] " Mike Rapoport
2019-01-21 8:04 ` [PATCH v2 13/21] " Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` [PATCH v2 14/21] ia64: add checks for the return value of memblock_alloc*() Mike Rapoport
2019-01-21 8:04 ` [OpenRISC] " Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` [v2,14/21] " Mike Rapoport
2019-01-21 8:04 ` [PATCH v2 14/21] " Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` [PATCH v2 15/21] sparc: " Mike Rapoport
2019-01-21 8:04 ` [OpenRISC] " Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` [v2,15/21] " Mike Rapoport
2019-01-21 8:04 ` [PATCH v2 15/21] " Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` [PATCH v2 16/21] mm/percpu: " Mike Rapoport
2019-01-21 8:04 ` [OpenRISC] " Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` [v2,16/21] " Mike Rapoport
2019-01-21 8:04 ` [PATCH v2 16/21] " Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` [PATCH v2 17/21] init/main: " Mike Rapoport
2019-01-21 8:04 ` [OpenRISC] " Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` [v2,17/21] " Mike Rapoport
2019-01-21 8:04 ` [PATCH v2 17/21] " Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` [PATCH v2 18/21] swiotlb: " Mike Rapoport
2019-01-21 8:04 ` [OpenRISC] " Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` [v2,18/21] " Mike Rapoport
2019-01-21 8:04 ` [PATCH v2 18/21] " Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` [PATCH v2 19/21] treewide: " Mike Rapoport
2019-01-21 8:04 ` [OpenRISC] " Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` [v2,19/21] " Mike Rapoport
2019-01-21 8:04 ` [PATCH v2 19/21] " Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:39 ` Geert Uytterhoeven
2019-01-21 8:39 ` Geert Uytterhoeven
2019-01-21 8:39 ` Geert Uytterhoeven
2019-01-21 8:39 ` Geert Uytterhoeven
2019-01-21 8:39 ` [OpenRISC] " Geert Uytterhoeven
2019-01-21 8:39 ` Geert Uytterhoeven
2019-01-21 8:39 ` Geert Uytterhoeven
2019-01-21 8:39 ` Geert Uytterhoeven
2019-01-21 8:39 ` Geert Uytterhoeven
2019-01-21 8:39 ` Geert Uytterhoeven
2019-01-21 17:18 ` Rob Herring
2019-01-21 17:18 ` Rob Herring
2019-01-21 17:18 ` [OpenRISC] " Rob Herring
2019-01-21 17:18 ` Rob Herring
2019-01-21 17:18 ` Rob Herring
2019-01-21 17:18 ` [v2,19/21] " Rob Herring
2019-01-21 17:18 ` [PATCH v2 19/21] " Rob Herring
2019-01-21 17:18 ` Rob Herring
2019-01-21 17:18 ` Rob Herring
2019-01-31 6:07 ` Christophe Leroy
2019-01-31 6:07 ` [OpenRISC] " Christophe Leroy
2019-01-31 6:07 ` Christophe Leroy
2019-01-31 6:07 ` Christophe Leroy
2019-01-31 6:07 ` [v2,19/21] " Christophe Leroy
2019-01-31 6:07 ` [PATCH v2 19/21] " Christophe Leroy
2019-01-31 6:07 ` Christophe Leroy
2019-01-31 6:07 ` Christophe Leroy
2019-01-31 6:41 ` Mike Rapoport
2019-01-31 6:41 ` Mike Rapoport
2019-01-31 6:41 ` Mike Rapoport
2019-01-31 6:41 ` [OpenRISC] " Mike Rapoport
2019-01-31 6:41 ` Mike Rapoport
2019-01-31 6:41 ` Mike Rapoport
2019-01-31 6:41 ` [v2,19/21] " Mike Rapoport
2019-01-31 6:41 ` [PATCH v2 19/21] " Mike Rapoport
2019-01-31 6:41 ` Mike Rapoport
2019-01-31 6:41 ` Mike Rapoport
2019-01-31 6:44 ` Christophe Leroy
2019-01-31 6:44 ` Christophe Leroy
2019-01-31 6:44 ` [OpenRISC] " Christophe Leroy
2019-01-31 6:44 ` Christophe Leroy
2019-01-31 6:44 ` Christophe Leroy
2019-01-31 6:44 ` [v2,19/21] " Christophe Leroy
2019-01-31 6:44 ` [PATCH v2 19/21] " Christophe Leroy
2019-01-31 6:44 ` Christophe Leroy
2019-01-31 6:44 ` Christophe Leroy
2019-01-31 7:07 ` Christophe Leroy
2019-01-31 7:07 ` [OpenRISC] " Christophe Leroy
2019-01-31 7:07 ` Christophe Leroy
2019-01-31 7:07 ` Christophe Leroy
2019-01-31 7:07 ` [v2,19/21] " Christophe Leroy
2019-01-31 7:07 ` [PATCH v2 19/21] " Christophe Leroy
2019-01-31 7:07 ` Christophe Leroy
2019-01-31 7:07 ` Christophe Leroy
2019-01-31 7:14 ` Mike Rapoport
2019-01-31 7:14 ` Mike Rapoport
2019-01-31 7:14 ` Mike Rapoport
2019-01-31 7:14 ` [OpenRISC] " Mike Rapoport
2019-01-31 7:14 ` Mike Rapoport
2019-01-31 7:14 ` Mike Rapoport
2019-01-31 7:14 ` [v2,19/21] " Mike Rapoport
2019-01-31 7:14 ` [PATCH v2 19/21] " Mike Rapoport
2019-01-31 7:14 ` Mike Rapoport
2019-01-31 7:14 ` Mike Rapoport
2019-01-31 7:07 ` Christophe Leroy
2019-01-31 6:07 ` Christophe Leroy
2019-01-31 15:23 ` Max Filippov
2019-01-31 15:23 ` Max Filippov
2019-01-31 15:23 ` Max Filippov
2019-01-31 15:23 ` Max Filippov
2019-01-31 15:23 ` [OpenRISC] " Max Filippov
2019-01-31 15:23 ` Max Filippov
2019-01-31 15:23 ` Max Filippov
2019-01-31 15:23 ` Max Filippov
2019-01-31 15:23 ` Max Filippov
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` [PATCH v2 20/21] memblock: memblock_alloc_try_nid: don't panic Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` [OpenRISC] " Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` [v2,20/21] " Mike Rapoport
2019-01-21 8:04 ` [PATCH v2 20/21] " Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` [PATCH v2 21/21] memblock: drop memblock_alloc_*_nopanic() variants Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` [OpenRISC] " Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` [v2,21/21] " Mike Rapoport
2019-01-21 8:04 ` [PATCH v2 21/21] " Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-21 8:04 ` Mike Rapoport
2019-01-30 13:38 ` Petr Mladek
2019-01-30 13:38 ` Petr Mladek
2019-01-30 13:38 ` [OpenRISC] " Petr Mladek
2019-01-30 13:38 ` Petr Mladek
2019-01-30 13:38 ` Petr Mladek
2019-01-30 13:38 ` [v2,21/21] " Petr Mladek
2019-01-30 13:38 ` [PATCH v2 21/21] " Petr Mladek
2019-01-30 13:38 ` Petr Mladek
2019-01-30 13:38 ` Petr Mladek
2019-09-24 17:52 ` [PATCH v2 00/21] Refine memblock API Adam Ford
2019-09-24 17:52 ` [OpenRISC] " Adam Ford
2019-09-24 17:52 ` [Xen-devel] " Adam Ford
2019-09-24 17:52 ` Adam Ford
2019-09-24 17:52 ` Adam Ford
2019-09-24 17:52 ` Adam Ford
2019-09-24 17:52 ` Adam Ford
2019-09-24 17:52 ` Adam Ford
2019-09-25 6:42 ` Mike Rapoport
2019-09-25 6:42 ` Mike Rapoport
2019-09-25 12:12 ` Fabio Estevam
2019-09-25 12:12 ` [OpenRISC] " Fabio Estevam
2019-09-25 12:12 ` [Xen-devel] " Fabio Estevam
2019-09-25 12:12 ` Fabio Estevam
2019-09-25 12:12 ` Fabio Estevam
2019-09-25 12:12 ` Fabio Estevam
2019-09-25 12:17 ` Adam Ford
2019-09-25 12:17 ` [OpenRISC] " Adam Ford
2019-09-25 12:17 ` [Xen-devel] " Adam Ford
2019-09-25 12:17 ` Adam Ford
2019-09-25 12:17 ` Adam Ford
2019-09-25 12:17 ` Adam Ford
2019-09-25 15:17 ` Fabio Estevam
2019-09-25 15:17 ` [OpenRISC] " Fabio Estevam
2019-09-25 15:17 ` [Xen-devel] " Fabio Estevam
2019-09-25 15:17 ` Fabio Estevam
2019-09-25 15:17 ` Fabio Estevam
2019-09-25 15:17 ` Fabio Estevam
2019-09-26 13:09 ` Adam Ford [this message]
2019-09-26 13:09 ` [OpenRISC] " Adam Ford
2019-09-26 13:09 ` [Xen-devel] " Adam Ford
2019-09-26 13:09 ` Adam Ford
2019-09-26 13:09 ` Adam Ford
2019-09-26 13:09 ` Adam Ford
2019-09-26 16:04 ` Mike Rapoport
2019-09-26 16:04 ` [OpenRISC] " Mike Rapoport
2019-09-26 16:04 ` [Xen-devel] " Mike Rapoport
2019-09-26 16:04 ` Mike Rapoport
2019-09-26 16:04 ` Mike Rapoport
2019-09-26 16:04 ` Mike Rapoport
2019-09-26 19:35 ` Adam Ford
2019-09-26 19:35 ` [OpenRISC] " Adam Ford
2019-09-26 19:35 ` [Xen-devel] " Adam Ford
2019-09-26 19:35 ` Adam Ford
2019-09-26 19:35 ` Adam Ford
2019-09-26 19:35 ` Adam Ford
2019-09-28 7:33 ` Mike Rapoport
2019-09-28 7:33 ` [OpenRISC] " Mike Rapoport
2019-09-28 7:33 ` [Xen-devel] " Mike Rapoport
2019-09-28 7:33 ` Mike Rapoport
2019-09-28 7:33 ` Mike Rapoport
2019-09-28 7:33 ` Mike Rapoport
2019-09-29 13:33 ` Adam Ford
2019-09-29 13:33 ` [OpenRISC] " Adam Ford
2019-09-29 13:33 ` [Xen-devel] " Adam Ford
2019-09-29 13:33 ` Adam Ford
2019-09-29 13:33 ` Adam Ford
2019-09-29 13:33 ` Adam Ford
2019-10-02 0:14 ` Adam Ford
2019-10-02 0:14 ` [OpenRISC] " Adam Ford
2019-10-02 0:14 ` [Xen-devel] " Adam Ford
2019-10-02 0:14 ` Adam Ford
2019-10-02 0:14 ` Adam Ford
2019-10-02 0:14 ` Adam Ford
2019-10-02 7:36 ` Mike Rapoport
2019-10-02 7:36 ` [OpenRISC] " Mike Rapoport
2019-10-02 7:36 ` [Xen-devel] " Mike Rapoport
2019-10-02 7:36 ` Mike Rapoport
2019-10-02 7:36 ` Mike Rapoport
2019-10-02 7:36 ` Mike Rapoport
2019-10-02 7:36 ` Mike Rapoport
2019-10-02 11:14 ` Adam Ford
2019-10-02 11:14 ` [OpenRISC] " Adam Ford
2019-10-02 11:14 ` [Xen-devel] " Adam Ford
2019-10-02 11:14 ` Adam Ford
2019-10-02 11:14 ` Adam Ford
2019-10-02 11:14 ` Adam Ford
2019-10-03 5:34 ` Mike Rapoport
2019-10-03 5:34 ` Mike Rapoport
2019-10-03 8:49 ` Russell King - ARM Linux admin
2019-10-03 8:49 ` Russell King - ARM Linux admin
2019-10-03 11:30 ` Mike Rapoport
2019-10-03 11:30 ` Mike Rapoport
2019-10-03 13:17 ` Lucas Stach
2019-10-03 13:17 ` Lucas Stach
2019-10-03 13:17 ` Lucas Stach
2019-10-04 9:27 ` Russell King - ARM Linux admin
2019-10-04 9:27 ` Russell King - ARM Linux admin
2019-10-04 13:21 ` Lucas Stach
2019-10-04 13:21 ` Lucas Stach
2019-10-04 13:21 ` Lucas Stach
2019-10-04 13:58 ` Adam Ford
2019-10-04 13:58 ` Adam Ford
2019-10-04 13:58 ` Adam Ford
2019-10-04 17:10 ` Mike Rapoport
2019-10-04 17:10 ` Mike Rapoport
2019-10-04 17:29 ` Mike Rapoport
2019-10-04 17:29 ` Mike Rapoport
2019-10-03 14:46 ` Chris Healy
2019-10-03 14:46 ` Chris Healy
2019-10-03 14:46 ` Chris Healy
2019-10-04 9:12 ` Russell King - ARM Linux admin
2019-10-04 9:12 ` Russell King - ARM Linux admin
2019-01-21 8:03 Mike Rapoport
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=CAHCN7xJ32BYZu-DVTVLSzv222U50JDb8F0A_tLDERbb8kPdRxg@mail.gmail.com \
--to=aford173@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=cphealy@gmail.com \
--cc=dalias@libc.org \
--cc=dennis@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=geert@linux-m68k.org \
--cc=guoren@kernel.org \
--cc=hch@lst.de \
--cc=heiko.carstens@de.ibm.com \
--cc=jcmvbkbc@gmail.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-c6x-dev@linux-c6x.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mattst88@gmail.com \
--cc=msalter@redhat.com \
--cc=richard@nod.at \
--cc=rppt@linux.ibm.com \
--cc=sparclinux@vger.kernel.org \
--cc=uclinux-h8-devel@lists.sourceforge.jp \
--cc=x86@kernel.org \
--cc=ysato@users.sourceforge.jp \
/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.