The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Tim Chen <tim.c.chen@linux.intel.com>
To: linux@treblig.org, mingo@redhat.com, peterz@infradead.org,
	 juri.lelli@redhat.com, vincent.guittot@linaro.org,
	dietmar.eggemann@arm.com,  rostedt@goodmis.org,
	bsegall@google.com, mgorman@suse.de, vschneid@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched/wait: Remove unused bit_wait_io_timeout
Date: Thu, 03 Oct 2024 14:13:56 -0700	[thread overview]
Message-ID: <1da9dc550bf97d31468f562aa8f498a756238651.camel@linux.intel.com> (raw)
In-Reply-To: <20241001234016.231696-1-linux@treblig.org>

On Wed, 2024-10-02 at 00:40 +0100, linux@treblig.org wrote:
> From: "Dr. David Alan Gilbert" <linux@treblig.org>
> 
> bit_wait_io_timeout has been unused since 2016's
> commit 62906027091f ("mm: add PageWaiters indicating tasks are waiting for a page bit")
> 
> Remove it.

Double check the code.  Indeed bit_wait_io_timeout() was no longer used since v4.10
and can be removed.

Reviewed-by: Tim Chen <tim.c.chen@linux.intel.com>

> 
> Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
> ---
>  include/linux/wait_bit.h |  1 -
>  kernel/sched/wait_bit.c  | 14 --------------
>  2 files changed, 15 deletions(-)
> 
> diff --git a/include/linux/wait_bit.h b/include/linux/wait_bit.h
> index 7725b7579b78..d9c23377dc75 100644
> --- a/include/linux/wait_bit.h
> +++ b/include/linux/wait_bit.h
> @@ -49,7 +49,6 @@ int wake_bit_function(struct wait_queue_entry *wq_entry, unsigned mode, int sync
>  extern int bit_wait(struct wait_bit_key *key, int mode);
>  extern int bit_wait_io(struct wait_bit_key *key, int mode);
>  extern int bit_wait_timeout(struct wait_bit_key *key, int mode);
> -extern int bit_wait_io_timeout(struct wait_bit_key *key, int mode);
>  
>  /**
>   * wait_on_bit - wait for a bit to be cleared
> diff --git a/kernel/sched/wait_bit.c b/kernel/sched/wait_bit.c
> index 134d7112ef71..c6aab3db70bf 100644
> --- a/kernel/sched/wait_bit.c
> +++ b/kernel/sched/wait_bit.c
> @@ -228,20 +228,6 @@ __sched int bit_wait_timeout(struct wait_bit_key *word, int mode)
>  }
>  EXPORT_SYMBOL_GPL(bit_wait_timeout);
>  
> -__sched int bit_wait_io_timeout(struct wait_bit_key *word, int mode)
> -{
> -	unsigned long now = READ_ONCE(jiffies);
> -
> -	if (time_after_eq(now, word->timeout))
> -		return -EAGAIN;
> -	io_schedule_timeout(word->timeout - now);
> -	if (signal_pending_state(mode, current))
> -		return -EINTR;
> -
> -	return 0;
> -}
> -EXPORT_SYMBOL_GPL(bit_wait_io_timeout);
> -
>  void __init wait_bit_init(void)
>  {
>  	int i;


  reply	other threads:[~2024-10-03 21:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-01 23:40 [PATCH] sched/wait: Remove unused bit_wait_io_timeout linux
2024-10-03 21:13 ` Tim Chen [this message]
2024-10-08  7:56 ` [tip: sched/core] " tip-bot2 for Dr. David Alan Gilbert

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=1da9dc550bf97d31468f562aa8f498a756238651.camel@linux.intel.com \
    --to=tim.c.chen@linux.intel.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@treblig.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.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