[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c1538231-196e-c99e-db48-a802bbab049d@infradead.org>
Date: Wed, 25 Mar 2020 14:34:08 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Bjorn Helgaas <helgaas@...nel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>
Cc: Vidya Sagar <vidyas@...dia.com>, akpm@...ux-foundation.org,
broonie@...nel.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-next@...r.kernel.org, mhocko@...e.cz,
mm-commits@...r.kernel.org, sfr@...b.auug.org.au,
linux-pci <linux-pci@...r.kernel.org>
Subject: Re: mmotm 2020-03-23-21-29 uploaded
(pci/controller/dwc/pcie-tegra194.c)
On 3/25/20 2:20 PM, Bjorn Helgaas wrote:
> On Wed, Mar 25, 2020 at 05:01:43PM +0000, Lorenzo Pieralisi wrote:
>> On Wed, Mar 25, 2020 at 08:43:32PM +0530, Vidya Sagar wrote:
>>> Also, I wanted to know how can I catch this locally? i.e. How can I
>>> generate the config file attached by Randy locally so that I can get the
>>> source ready without these kind of issues?
>
> Randy attached the config-r1578 file to his initial report. I saved
> that attachment, then:
>
> $ git checkout next
> $ make mrproper
> $ cp ~/Downloads/config-r1578 .config
> $ make drivers/pci/controller/
Hi Vidya,
All I do is run 20 of these on each linux-next and mmotm release:
$ make clean; make randconfig; make all
and see what happens.
--
~Randy
Powered by blists - more mailing lists