From: Paul Walmsley <paul.walmsley@sifive.com>
To: Anup Patel <anup@brainfault.org>
Cc: Anup Patel <Anup.Patel@wdc.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Atish Patra <Atish.Patra@wdc.com>,
Alistair Francis <Alistair.Francis@wdc.com>,
Christoph Hellwig <hch@lst.de>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] RISC-V: Add debug defconfigs
Date: Thu, 5 Dec 2019 09:01:02 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1912050900030.218941@viisi.sifive.com> (raw)
In-Reply-To: <CAAhSdy1RQw3MVcVT5y1EHr72LDNADKRL5nO2E8OrzBi+tpuvtA@mail.gmail.com>
On Thu, 5 Dec 2019, Anup Patel wrote:
> I understand that you need DEBUG options for SiFive internal
> use
[ ... ]
> This is the right time to introduce debug defconfigs so that you can
> use it for your SiFive internal use
[ ... ]
> and you can find an alternative way to enable DEBUG options for SiFive
> internal use.
What leads you to conclude that this was done for SiFive internal use?
- Paul
WARNING: multiple messages have this Message-ID (diff)
From: Paul Walmsley <paul.walmsley@sifive.com>
To: Anup Patel <anup@brainfault.org>
Cc: Albert Ou <aou@eecs.berkeley.edu>,
Anup Patel <Anup.Patel@wdc.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Atish Patra <Atish.Patra@wdc.com>,
Alistair Francis <Alistair.Francis@wdc.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] RISC-V: Add debug defconfigs
Date: Thu, 5 Dec 2019 09:01:02 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1912050900030.218941@viisi.sifive.com> (raw)
In-Reply-To: <CAAhSdy1RQw3MVcVT5y1EHr72LDNADKRL5nO2E8OrzBi+tpuvtA@mail.gmail.com>
On Thu, 5 Dec 2019, Anup Patel wrote:
> I understand that you need DEBUG options for SiFive internal
> use
[ ... ]
> This is the right time to introduce debug defconfigs so that you can
> use it for your SiFive internal use
[ ... ]
> and you can find an alternative way to enable DEBUG options for SiFive
> internal use.
What leads you to conclude that this was done for SiFive internal use?
- Paul
next prev parent reply other threads:[~2019-12-05 17:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 0:56 [PATCH] RISC-V: Add debug defconfigs Anup Patel
2019-12-05 0:56 ` Anup Patel
2019-12-05 3:03 ` Paul Walmsley
2019-12-05 3:03 ` Paul Walmsley
2019-12-05 16:33 ` Anup Patel
2019-12-05 16:33 ` Anup Patel
2019-12-05 16:47 ` Daniel Thompson
2019-12-05 16:47 ` Daniel Thompson
2019-12-05 17:09 ` Anup Patel
2019-12-05 17:09 ` Anup Patel
2019-12-05 17:01 ` Paul Walmsley [this message]
2019-12-05 17:01 ` Paul Walmsley
2019-12-05 17:05 ` Anup Patel
2019-12-05 17:05 ` Anup Patel
2019-12-05 23:14 ` Paul Walmsley
2019-12-05 23:14 ` Paul Walmsley
2019-12-05 23:23 ` Anup Patel
2019-12-05 23:23 ` Anup Patel
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=alpine.DEB.2.21.9999.1912050900030.218941@viisi.sifive.com \
--to=paul.walmsley@sifive.com \
--cc=Alistair.Francis@wdc.com \
--cc=Anup.Patel@wdc.com \
--cc=Atish.Patra@wdc.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.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 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.