From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Manuel Lauss <manuel.lauss@gmail.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Revert "MIPS: unhide PATA_PLATFORM"
Date: Fri, 9 Jun 2023 10:21:58 +0200 [thread overview]
Message-ID: <20230609082158.GF8160@alpha.franken.de> (raw)
In-Reply-To: <alpine.DEB.2.21.2306011335100.59991@angie.orcam.me.uk>
On Thu, Jun 01, 2023 at 01:56:36PM +0100, Maciej W. Rozycki wrote:
> Revert commit 75b18aac6fa3 ("MIPS: unhide PATA_PLATFORM") now that
> HAVE_PATA_PLATFORM is set selectively for all the relevant platforms.
>
> Verified with `db1xxx_defconfig' and `sb1250_swarm_defconfig' by making
> sure PATA_PLATFORM is still there in `.config' with this change applied,
> and with `malta_defconfig' by making sure it's now gone.
>
> Signed-off-by: Maciej W. Rozycki <macro@orcam.me.uk>
> ---
> arch/mips/Kconfig | 1 -
> 1 file changed, 1 deletion(-)
>
> linux-mips-no-pata-platform.diff
> Index: linux-macro/arch/mips/Kconfig
> ===================================================================
> --- linux-macro.orig/arch/mips/Kconfig
> +++ linux-macro/arch/mips/Kconfig
> @@ -79,7 +79,6 @@ config MIPS
> select HAVE_LD_DEAD_CODE_DATA_ELIMINATION
> select HAVE_MOD_ARCH_SPECIFIC
> select HAVE_NMI
> - select HAVE_PATA_PLATFORM
> select HAVE_PERF_EVENTS
> select HAVE_PERF_REGS
> select HAVE_PERF_USER_STACK_DUMP
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2023-06-09 8:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 12:56 [PATCH 0/2] MIPS: Fix recent clutter with PATA_PLATFORM Maciej W. Rozycki
2023-06-01 12:56 ` [PATCH 1/2] MIPS: Alchemy: Enable PATA_PLATFORM support Maciej W. Rozycki
2023-06-09 8:21 ` Thomas Bogendoerfer
2023-06-01 12:56 ` [PATCH 2/2] Revert "MIPS: unhide PATA_PLATFORM" Maciej W. Rozycki
2023-06-09 8:21 ` Thomas Bogendoerfer [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=20230609082158.GF8160@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=manuel.lauss@gmail.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