From: Florian Fainelli <f.fainelli@gmail.com>
To: Wolfram Sang <wsa@kernel.org>,
Jonas Gorski <jonas.gorski@gmail.com>,
linux-kernel@vger.kernel.org,
Greg KH <gregkh@linuxfoundation.org>,
linux-mips@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] vlynq: remove bus support
Date: Mon, 18 Sep 2023 11:33:47 -0700 [thread overview]
Message-ID: <19db0278-b11d-49f3-819b-cbc998769832@gmail.com> (raw)
In-Reply-To: <ZQhOGY+tr25CDuI3@shikoro>
On 9/18/23 06:18, Wolfram Sang wrote:
> Hi all,
>
>> Agreed, TI AR7 is nearly 25 years old now, we should be able to remove that.
>> Wolfram, do you feel like doing that or would you rather have me do it, say
>> next week?
>
> So, I pushed out an RC here:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git renesas/cleanup/remove_ar7
>
> Just waiting for the buildbot report before I send out patches. buildbot
> was already happy with my protoype, though. But I needed to reorder the
> patches. (I do wonder, though, if they build AR7. I would have expected
> a build failure with my prototype).
Looks good to me, just a few nits:
arch/arm/configs/pxa_defconfig:CONFIG_MTD_AR7_PARTS=m
this is clearly a stray reference to begin with, but should be folded in
your commit removing the MTD partition parser.
Other than that, LGTM and thanks for doing that clean up.
--
Florian
next prev parent reply other threads:[~2023-09-18 18:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 9:11 [RFC PATCH 0/2] vlynq: remove bus support Wolfram Sang
2023-09-16 9:11 ` [RFC PATCH 1/2] MIPS: AR7: remove VLYNQ init Wolfram Sang
2023-09-16 11:11 ` [RFC PATCH 0/2] vlynq: remove bus support Jonas Gorski
2023-09-16 16:42 ` Florian Fainelli
2023-09-16 17:02 ` Wolfram Sang
2023-09-18 13:18 ` Wolfram Sang
2023-09-18 18:33 ` Florian Fainelli [this message]
2023-09-19 6:37 ` Wolfram Sang
2023-09-16 11:43 ` Greg KH
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=19db0278-b11d-49f3-819b-cbc998769832@gmail.com \
--to=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonas.gorski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=wsa@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).