linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: John Crispin <john@phrozen.org>,
	linux-mips@vger.kernel.org, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: ath79: remove obsolete ATH79_DEV_* configs
Date: Fri, 17 Mar 2023 11:22:32 +0100	[thread overview]
Message-ID: <20230317102232.GA7054@alpha.franken.de> (raw)
In-Reply-To: <20230316114952.26253-1-lukas.bulwahn@gmail.com>

On Thu, Mar 16, 2023 at 12:49:52PM +0100, Lukas Bulwahn wrote:
> Commit 85b9686dae30 ("MIPS: ath79: drop platform device registration code")
> removes all files arch/mips/ath79/dev-*.[ch], adjusts the Makefile, but
> misses to adjust the Kconfig file. Hence, since then, the configs
> ATH79_DEV_* are really dead.
> 
> Commit 3a77e0d75eed ("MIPS: ath79: drop machfiles") already removes all
> configs that select ATH79_DEV_* config. So at that point, they was not a
> way to enable them with a kernel build configuration.
> 
> Remove these obsolete ATH79_DEV_* configs.
> 
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
>  arch/mips/ath79/Kconfig | 16 ----------------
>  1 file changed, 16 deletions(-)

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 ]

      reply	other threads:[~2023-03-17 10:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-16 11:49 [PATCH] MIPS: ath79: remove obsolete ATH79_DEV_* configs Lukas Bulwahn
2023-03-17 10:22 ` 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=20230317102232.GA7054@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=john@phrozen.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=lukas.bulwahn@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;
as well as URLs for NNTP newsgroup(s).