From: Linus Torvalds <torvalds@linux-foundation.org>
To: Anup Patel <anup@brainfault.org>
Cc: Carlos Eduardo de Paula <me@carlosedp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Atish Patra <Atish.Patra@wdc.com>,
Alistair Francis <Alistair.Francis@wdc.com>,
"paul.walmsley@sifive.com" <paul.walmsley@sifive.com>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>, "hch@lst.de" <hch@lst.de>
Subject: Re: [GIT PULL] Second set of RISC-V updates for v5.5-rc1
Date: Fri, 6 Dec 2019 13:22:55 -0800 [thread overview]
Message-ID: <CAHk-=wjGqZk7XcmtqJ7J0Em_XP1ECYU4CDBwFuMOjLrBH0-AHw@mail.gmail.com> (raw)
In-Reply-To: <CAAhSdy0BXtkZPbav3QRtdMN9GcYG0SuxBDpwjFC8B_pr35s+Kg@mail.gmail.com>
On Fri, Dec 6, 2019 at 1:15 PM Anup Patel <anup@brainfault.org> wrote:
>
> Better approach is to have a fragmented .config for extra DEBUG options.
Guys, stop this silly thread already.
The fact is, defconfig is useful for basic smoke testing - automated
compile and boot testing, and getting perhaps random people to test
something.
But it is not appropriate for a distro to use. Anybody who makes that
argument is wrong. If you actually know what you are doing, the
defconfig is entirely irrelevant, and no, trying to make special debug
fragments isn't going to make it more so.
So if you are a RISC-V distro: stop using the defconfig. You shouldn't
have used it in the first place. It's not meant to be a usable one.
And no, don't start making "more defconfigs". We've had that mess too.
It's broken too.
If you are a distro maintainer and you cannot be bothered to make your
own config file, then you should just stop being a distro maintainer,
and maybe take up farming instead.
Right now you guys are just wasting everybody elses time. Stop it.
Or at least remove me from the cc, because I'm not interested in this
whiny "I'm too lazy to maintain my own config, and I _insist_ that the
defconfig is meant only for me".
Linus
next prev parent reply other threads:[~2019-12-06 21:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 8:52 [GIT PULL] Second set of RISC-V updates for v5.5-rc1 Paul Walmsley
2019-12-04 12:52 ` Anup Patel
2019-12-04 18:38 ` Alistair Francis
2019-12-04 19:38 ` Paul Walmsley
2019-12-04 19:50 ` Alistair Francis
2019-12-04 23:46 ` Anup Patel
2019-12-05 2:54 ` Paul Walmsley
2019-12-05 3:58 ` Alistair Francis
2019-12-05 5:35 ` David Abdurachmanov
2019-12-05 13:19 ` Anup Patel
2019-12-05 23:12 ` Paul Walmsley
2019-12-05 23:35 ` Alistair Francis
2019-12-05 23:46 ` Alistair Francis
2019-12-06 21:12 ` Carlos Eduardo de Paula
2019-12-06 21:15 ` Anup Patel
2019-12-06 21:21 ` Carlos Eduardo de Paula
2019-12-06 21:22 ` Linus Torvalds [this message]
2019-12-04 19:25 ` pr-tracker-bot
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='CAHk-=wjGqZk7XcmtqJ7J0Em_XP1ECYU4CDBwFuMOjLrBH0-AHw@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=Alistair.Francis@wdc.com \
--cc=Atish.Patra@wdc.com \
--cc=anup@brainfault.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=me@carlosedp.com \
--cc=paul.walmsley@sifive.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).