From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 0/2] MIPS: SiByte: Update SWARM defconfig for PATA support
Date: Wed, 24 Mar 2021 11:02:04 +0100 [thread overview]
Message-ID: <20210324100204.GI2378@alpha.franken.de> (raw)
In-Reply-To: <alpine.DEB.2.21.2103212028360.21463@angie.orcam.me.uk>
On Sun, Mar 21, 2021 at 08:55:37PM +0100, Maciej W. Rozycki wrote:
> Hi,
>
> In the course of looking into Christoph's recent proposal to drop legacy
> IDE drivers I have noticed that SiByte SWARM's defconfig does not enable
> the pata_platform driver for the onboard PATA interface. I think default
> configuration ought to enable all the supported onboard devices unless
> there are specific reasons so as not to, and the PATA interface is one of
> the boot devices supported by the CFE firmware, so I think even more then
> that it should be included by default.
>
> Change split into two because the defconfig has become stale since the
> last update, so 1/2 first regenerates it, and then 2/2 applies the actual
> modification.
>
> Sadly I'm currently away from my SWARM board for the foreseeable future
> and I have no remote access to it either, but this is supposed not to need
> run-time verification. Build-tested only then.
>
> Please apply.
series 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:[~2021-03-24 10:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-21 19:55 Maciej W. Rozycki
2021-03-21 19:55 ` [PATCH 1/2] MIPS: SiByte: Regenerate stale SWARM defconfig Maciej W. Rozycki
2021-03-21 19:55 ` [PATCH 2/2] MIPS: SiByte: Enable pata_platform with " Maciej W. Rozycki
2021-03-24 10:02 ` 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=20210324100204.GI2378@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@orcam.me.uk \
/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
all inboxes | Powered by JetHome®