From: Daniel Vetter <daniel@ffwll.ch>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
David Airlie <airlied@linux.ie>,
y2038@lists.linaro.org, intel-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] i915: remove timespec_to_jiffies_timeout
Date: Mon, 18 Jun 2018 18:07:35 +0200 [thread overview]
Message-ID: <20180618160735.GL22478@phenom.ffwll.local> (raw)
In-Reply-To: <20180618153855.2126048-1-arnd@arndb.de>
On Mon, Jun 18, 2018 at 05:38:43PM +0200, Arnd Bergmann wrote:
> This function has been unused since commit 5ed0bdf21a85 ("drm: i915:
> Use nsec based interfaces"). Let's remove the definition as well now
> to help get rid of all uses of 'timespec'.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Applied, thanks for the patch.
-Daniel
> ---
> drivers/gpu/drm/i915/i915_drv.h | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
> index 34c125e2d90c..5f61676e8fb8 100644
> --- a/drivers/gpu/drm/i915/i915_drv.h
> +++ b/drivers/gpu/drm/i915/i915_drv.h
> @@ -3673,14 +3673,6 @@ static inline unsigned long nsecs_to_jiffies_timeout(const u64 n)
> return min_t(u64, MAX_JIFFY_OFFSET, nsecs_to_jiffies64(n) + 1);
> }
>
> -static inline unsigned long
> -timespec_to_jiffies_timeout(const struct timespec *value)
> -{
> - unsigned long j = timespec_to_jiffies(value);
> -
> - return min_t(unsigned long, MAX_JIFFY_OFFSET, j + 1);
> -}
> -
> /*
> * If you need to wait X milliseconds between events A and B, but event B
> * doesn't happen exactly after event A, you record the timestamp (jiffies) of
> --
> 2.9.0
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
prev parent reply other threads:[~2018-06-18 16:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 15:38 Arnd Bergmann
2018-06-18 16:07 ` Daniel Vetter [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=20180618160735.GL22478@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@linux.ie \
--cc=arnd@arndb.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=y2038@lists.linaro.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
all inboxes | Powered by JetHome®