public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Aleksander Jan Bajkowski <olek2@wp.pl>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: lantiq: remove unused function declaration
Date: Wed, 5 Apr 2023 10:26:54 +0200	[thread overview]
Message-ID: <20230405082654.GC5556@alpha.franken.de> (raw)
In-Reply-To: <20230329210328.9320-1-olek2@wp.pl>

On Wed, Mar 29, 2023 at 11:03:28PM +0200, Aleksander Jan Bajkowski wrote:
> The removed function declaration is a leftover of the old gphy firmware
> loader, that has been removed in d5103604f78e1afc29e586785af540c82b573f3a.
> 
> Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
> ---
>  arch/mips/include/asm/mach-lantiq/xway/lantiq_soc.h | 3 ---
>  1 file changed, 3 deletions(-)
> 
> diff --git a/arch/mips/include/asm/mach-lantiq/xway/lantiq_soc.h b/arch/mips/include/asm/mach-lantiq/xway/lantiq_soc.h
> index 4790cfa190d6..c2e0acb755cd 100644
> --- a/arch/mips/include/asm/mach-lantiq/xway/lantiq_soc.h
> +++ b/arch/mips/include/asm/mach-lantiq/xway/lantiq_soc.h
> @@ -94,9 +94,6 @@ extern __iomem void *ltq_cgu_membase;
>  #define LTQ_MPS_BASE_ADDR	(KSEG1 + 0x1F107000)
>  #define LTQ_MPS_CHIPID		((u32 *)(LTQ_MPS_BASE_ADDR + 0x0344))
>  
> -/* allow booting xrx200 phys */
> -int xrx200_gphy_boot(struct device *dev, unsigned int id, dma_addr_t dev_addr);
> -
>  /* request a non-gpio and set the PIO config */
>  #define PMU_PPE			 BIT(13)
>  extern void ltq_pmu_enable(unsigned int module);
> -- 
> 2.30.2

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-04-05  8:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29 21:03 [PATCH] MIPS: lantiq: remove unused function declaration Aleksander Jan Bajkowski
2023-04-05  8:26 ` 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=20230405082654.GC5556@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=olek2@wp.pl \
    /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