From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>, X86 ML <x86@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>
Subject: Re: [RFC PATCH] x86: slightly reduce defconfigs
Date: Thu, 19 Mar 2020 15:15:13 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.2.21.2003191514290.1745527@eddie.linux-mips.org> (raw)
In-Reply-To: <433f203e-4e00-f317-2e6b-81518b72843c@infradead.org>
On Tue, 25 Feb 2020, Randy Dunlap wrote:
> Eliminate 2 config symbols from both x86 defconfig files:
> HAMRADIO and FDDI.
>
> The FDDI Kconfig file even says (for the FDDI config symbol):
> Most people will say N.
For CONFIG_FDDI:
Acked-by: Maciej W. Rozycki <macro@linux-mips.org>
Maciej
next prev parent reply other threads:[~2020-03-19 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 5:14 [RFC PATCH] x86: slightly reduce defconfigs Randy Dunlap
2020-03-19 15:15 ` Maciej W. Rozycki [this message]
2020-03-19 18:03 ` [tip: x86/cleanups] x86/configs: Slightly " tip-bot2 for Randy Dunlap
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.LFD.2.21.2003191514290.1745527@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=x86@kernel.org \
/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).