mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Baolin Wang <baolin.wang@linaro.org>
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org, y2038@lists.linaro.org
Subject: Re: [PATCH v2 04/15] posix timers:Introduce the 64bit methods with timespec64 type for k_clock structure
Date: Tue, 5 May 2015 15:31:39 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.11.1505051529160.4225@nanos> (raw)
In-Reply-To: <1430381527-26349-1-git-send-email-baolin.wang@linaro.org>

On Thu, 30 Apr 2015, Baolin Wang wrote:
> diff --git a/include/linux/posix-timers.h b/include/linux/posix-timers.h
> index 907f3fd..35786c5 100644
> --- a/include/linux/posix-timers.h
> +++ b/include/linux/posix-timers.h
> @@ -98,9 +98,13 @@ struct k_itimer {
>  
>  struct k_clock {
>  	int (*clock_getres) (const clockid_t which_clock, struct timespec *tp);
> +	int (*clock_getres64) (const clockid_t which_clock, struct timespec64 *tp);
>  	int (*clock_set) (const clockid_t which_clock,
>  			  const struct timespec *tp);
> +	int (*clock_set64) (const clockid_t which_clock,
> +			    const struct timespec64 *tp);
>  	int (*clock_get) (const clockid_t which_clock, struct timespec * tp);
> +	int (*clock_get64) (const clockid_t which_clock, struct timespec64 *tp);
>  	int (*clock_adj) (const clockid_t which_clock, struct timex *tx);
>  	int (*timer_create) (struct k_itimer *timer);
>  	int (*nsleep) (const clockid_t which_clock, int flags,
> @@ -109,10 +113,15 @@ struct k_clock {
>  	int (*timer_set) (struct k_itimer * timr, int flags,
>  			  struct itimerspec * new_setting,
>  			  struct itimerspec * old_setting);
> +	int (*timer_set64) (struct k_itimer *timr, int flags,
> +			    struct itimerspec64 *new_setting,
> +			    struct itimerspec64 *old_setting);
>  	int (*timer_del) (struct k_itimer * timr);
>  #define TIMER_RETRY 1
>  	void (*timer_get) (struct k_itimer * timr,
>  			   struct itimerspec * cur_setting);
> +	void (*timer_get64) (struct k_itimer *timr,
> +			     struct itimerspec64 *cur_setting);

I asked you last time to provide a conversion for a single instance
first and I gave you even step by step instructions.

But you insist on resending the whole mess in one go. Try again.

Thanks,

	tglx

  reply	other threads:[~2015-05-05 13:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30  8:12 Baolin Wang
2015-05-05 13:31 ` Thomas Gleixner [this message]
     [not found]   ` <CAMz4kuJSPkY1pV4pOzjYAT1eb5M_G+eJ2dX58J1ADhXrhbJUtg@mail.gmail.com>
2015-05-06  8:06     ` Thomas Gleixner

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=alpine.DEB.2.11.1505051529160.4225@nanos \
    --to=tglx@linutronix.de \
    --cc=arnd@arndb.de \
    --cc=baolin.wang@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --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®