From: Randy Dunlap <rdunlap@infradead.org>
To: Bjorn Helgaas <helgaas@kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Vidya Sagar <vidyas@nvidia.com>,
akpm@linux-foundation.org, broonie@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-next@vger.kernel.org, mhocko@suse.cz,
mm-commits@vger.kernel.org, sfr@canb.auug.org.au,
linux-pci <linux-pci@vger.kernel.org>
Subject: Re: mmotm 2020-03-23-21-29 uploaded (pci/controller/dwc/pcie-tegra194.c)
Date: Wed, 25 Mar 2020 14:34:08 -0700 [thread overview]
Message-ID: <c1538231-196e-c99e-db48-a802bbab049d@infradead.org> (raw)
In-Reply-To: <20200325212048.GA72586@google.com>
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
prev parent reply other threads:[~2020-03-25 21:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 4:30 mmotm 2020-03-23-21-29 uploaded akpm
2020-03-24 15:16 ` mmotm 2020-03-23-21-29 uploaded (pci/controller/dwc/pcie-tegra194.c) Randy Dunlap
2020-03-24 16:18 ` Bjorn Helgaas
2020-03-25 15:13 ` Vidya Sagar
2020-03-25 15:52 ` Randy Dunlap
2020-03-25 17:01 ` Lorenzo Pieralisi
2020-03-25 21:20 ` Bjorn Helgaas
2020-03-25 21:34 ` Randy Dunlap [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=c1538231-196e-c99e-db48-a802bbab049d@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=helgaas@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=vidyas@nvidia.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).