public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: linux@treblig.org
Cc: bp@alien8.de, mingo@redhat.com, tglx@linutronix.de,
	dave.hansen@linux.intel.com, hpa@zytor.com, x86@kernel.org,
	linux-rtc@vger.kernel.org, arnd@arndb.de,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rtc: Remove hpet_rtc_dropped_irq()
Date: Mon, 13 Jan 2025 00:26:00 +0100	[thread overview]
Message-ID: <20250112232600ca0c0fd4@mail.local> (raw)
In-Reply-To: <20241215022356.181625-1-linux@treblig.org>

Dear x86 maintainers,

On 15/12/2024 02:23:56+0000, linux@treblig.org wrote:
> From: "Dr. David Alan Gilbert" <linux@treblig.org>
> 
> hpet_rtc_dropped_irq() has been unused since
> commit f52ef24be21a ("rtc/alpha: remove legacy rtc driver")
> 
> Remove it in rtc, and x86 hpet code.
> 

I'm willing t take this patch, can I get an ack?

> Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
> ---
>  arch/x86/include/asm/hpet.h | 1 -
>  arch/x86/kernel/hpet.c      | 6 ------
>  drivers/rtc/rtc-cmos.c      | 5 -----
>  3 files changed, 12 deletions(-)
> 
> diff --git a/arch/x86/include/asm/hpet.h b/arch/x86/include/asm/hpet.h
> index ab9f3dd87c80..ab0c78855ecb 100644
> --- a/arch/x86/include/asm/hpet.h
> +++ b/arch/x86/include/asm/hpet.h
> @@ -84,7 +84,6 @@ extern int hpet_set_rtc_irq_bit(unsigned long bit_mask);
>  extern int hpet_set_alarm_time(unsigned char hrs, unsigned char min,
>  			       unsigned char sec);
>  extern int hpet_set_periodic_freq(unsigned long freq);
> -extern int hpet_rtc_dropped_irq(void);
>  extern int hpet_rtc_timer_init(void);
>  extern irqreturn_t hpet_rtc_interrupt(int irq, void *dev_id);
>  extern int hpet_register_irq_handler(rtc_irq_handler handler);
> diff --git a/arch/x86/kernel/hpet.c b/arch/x86/kernel/hpet.c
> index c96ae8fee95e..7e21018a0e04 100644
> --- a/arch/x86/kernel/hpet.c
> +++ b/arch/x86/kernel/hpet.c
> @@ -1392,12 +1392,6 @@ int hpet_set_periodic_freq(unsigned long freq)
>  }
>  EXPORT_SYMBOL_GPL(hpet_set_periodic_freq);
>  
> -int hpet_rtc_dropped_irq(void)
> -{
> -	return is_hpet_enabled();
> -}
> -EXPORT_SYMBOL_GPL(hpet_rtc_dropped_irq);
> -
>  static void hpet_rtc_timer_reinit(void)
>  {
>  	unsigned int delta;
> diff --git a/drivers/rtc/rtc-cmos.c b/drivers/rtc/rtc-cmos.c
> index 78f2ce12c75a..9c8ce7510c56 100644
> --- a/drivers/rtc/rtc-cmos.c
> +++ b/drivers/rtc/rtc-cmos.c
> @@ -151,11 +151,6 @@ static inline int hpet_set_periodic_freq(unsigned long freq)
>  	return 0;
>  }
>  
> -static inline int hpet_rtc_dropped_irq(void)
> -{
> -	return 0;
> -}
> -
>  static inline int hpet_rtc_timer_init(void)
>  {
>  	return 0;
> -- 
> 2.47.1
> 

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2025-01-12 23:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-15  2:23 [PATCH] rtc: Remove hpet_rtc_dropped_irq() linux
2025-01-12 23:26 ` Alexandre Belloni [this message]
2025-01-13  9:59   ` Borislav Petkov
2025-01-13 22:10 ` Alexandre Belloni

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=20250112232600ca0c0fd4@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=arnd@arndb.de \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=linux@treblig.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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