From: Dan Carpenter <dan.carpenter@oracle•com>
To: "Song Bao Hua (Barry Song)" <song.bao.hua@hisilicon•com>
Cc: Dan Carpenter <error27@gmail•com>,
"lkp@intel•com" <lkp@intel•com>,
"catalin.marinas@arm•com" <catalin.marinas@arm•com>,
"kbuild@lists•01.org" <kbuild@lists•01.org>,
John Garry <john.garry@huawei•com>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
Linuxarm <linuxarm@huawei•com>,
"iommu@lists•linux-foundation.org"
<iommu@lists•linux-foundation.org>,
Jonathan Cameron <jonathan.cameron@huawei•com>,
"kbuild-all@lists•01.org" <kbuild-all@lists•01.org>,
"robin.murphy@arm•com" <robin.murphy@arm•com>,
"hch@lst•de" <hch@lst•de>,
"linux-arm-kernel@lists•infradead.org"
<linux-arm-kernel@lists•infradead.org>,
"m.szyprowski@samsung•com" <m.szyprowski@samsung•com>
Subject: Re: [PATCH 1/3] dma-direct: provide the ability to reserve per-numa CMA
Date: Fri, 5 Jun 2020 11:57:51 +0300 [thread overview]
Message-ID: <20200605085751.GQ30374@kadam> (raw)
In-Reply-To: <B926444035E5E2439431908E3842AFD24E0011@DGGEMI525-MBS.china.huawei.com>
On Fri, Jun 05, 2020 at 06:04:31AM +0000, Song Bao Hua (Barry Song) wrote:
>
>
> > -----Original Message-----
> > From: Dan Carpenter [mailto:dan.carpenter@oracle•com]
> > Sent: Thursday, June 4, 2020 11:37 PM
> > To: kbuild@lists•01.org; Song Bao Hua (Barry Song)
> > <song.bao.hua@hisilicon•com>; hch@lst•de; m.szyprowski@samsung•com;
> > robin.murphy@arm•com; catalin.marinas@arm•com
> > Cc: lkp@intel•com; Dan Carpenter <error27@gmail•com>;
> > kbuild-all@lists•01.org; iommu@lists•linux-foundation.org;
> > linux-arm-kernel@lists•infradead.org; linux-kernel@vger•kernel.org; Linuxarm
> > <linuxarm@huawei•com>; Jonathan Cameron
> > <jonathan.cameron@huawei•com>; John Garry <john.garry@huawei•com>
> > Subject: Re: [PATCH 1/3] dma-direct: provide the ability to reserve per-numa
> > CMA
> >
> > Hi Barry,
> >
> > url:
> > https://github.com/0day-ci/linux/commits/Barry-Song/support-per-numa-CM
> > A-for-ARM-server/20200603-104821
> > base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
> > for-next/core
> > config: x86_64-randconfig-m001-20200603 (attached as .config)
> > compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
> >
> > If you fix the issue, kindly add following tag as appropriate
> > Reported-by: kernel test robot <lkp@intel•com>
> > Reported-by: Dan Carpenter <dan.carpenter@oracle•com>
>
> Dan, thanks! Good catch!
> as this patch has not been in mainline yet, is it correct to add these "reported-by" in patch v2?
These are just an automated email from the zero day bot. I look over
the Smatch warnings and then forward them on.
regards,
dan carpenter
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-06-05 8:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 2:42 [PATCH 0/3] support per-numa CMA for ARM server Barry Song
2020-06-03 2:42 ` [PATCH 1/3] dma-direct: provide the ability to reserve per-numa CMA Barry Song
2020-06-03 6:55 ` kbuild test robot
2020-06-03 7:18 ` kbuild test robot
2020-06-03 7:18 ` [RFC PATCH] dma-direct: dma_contiguous_pernuma_area[] can be static kbuild test robot
2020-06-04 11:36 ` [PATCH 1/3] dma-direct: provide the ability to reserve per-numa CMA Dan Carpenter
2020-06-05 6:04 ` Song Bao Hua (Barry Song)
2020-06-05 8:57 ` Dan Carpenter [this message]
2020-06-06 3:46 ` [kbuild-all] " Philip Li
2020-06-06 10:15 ` Song Bao Hua (Barry Song)
2020-06-05 13:57 ` kernel test robot
2020-06-03 2:42 ` [PATCH 2/3] arm64: mm: reserve hugetlb CMA after numa_init Barry Song
2020-06-03 3:22 ` Roman Gushchin
2020-06-07 20:14 ` Matthias Brugger
2020-06-08 0:50 ` Song Bao Hua (Barry Song)
2020-06-09 15:33 ` Matthias Brugger
2020-06-03 2:42 ` [PATCH 3/3] arm64: mm: reserve per-numa " Barry Song
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=20200605085751.GQ30374@kadam \
--to=dan.carpenter@oracle$(echo .)com \
--cc=catalin.marinas@arm$(echo .)com \
--cc=error27@gmail$(echo .)com \
--cc=hch@lst$(echo .)de \
--cc=iommu@lists$(echo .)linux-foundation.org \
--cc=john.garry@huawei$(echo .)com \
--cc=jonathan.cameron@huawei$(echo .)com \
--cc=kbuild-all@lists$(echo .)01.org \
--cc=kbuild@lists$(echo .)01.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxarm@huawei$(echo .)com \
--cc=lkp@intel$(echo .)com \
--cc=m.szyprowski@samsung$(echo .)com \
--cc=robin.murphy@arm$(echo .)com \
--cc=song.bao.hua@hisilicon$(echo .)com \
/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