stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thadeu Lima de Souza Cascardo <cascardo@canonical.com>
To: Petr Vorel <pvorel@suse.cz>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v4.9-stable] alarmtimer: Change remaining ENOTSUPP to EOPNOTSUPP
Date: Fri, 8 Nov 2019 13:58:13 -0300	[thread overview]
Message-ID: <20191108165813.GB3753@calabresa> (raw)
In-Reply-To: <20191108155050.12786-1-pvorel@suse.cz>

On Fri, Nov 08, 2019 at 04:50:50PM +0100, Petr Vorel wrote:
> Fix backport of commit f18ddc13af981ce3c7b7f26925f099e7c6929aba upstream.
> 
> Update backport to change ENOTSUPP to EOPNOTSUPP in
> alarm_timer_{del,set}(), which were removed in
> f2c45807d3992fe0f173f34af9c347d907c31686 in v4.13-rc1.
> 
> Fixes: 65b7a5a36afb11a6769a70308c1ef3a2afae6bf4
> 
> Signed-off-by: Petr Vorel <pvorel@suse.cz>

Nice catch!

Acked-by: Thadeu Lima de Souza Cascardo <cascardo@canonical.com>

> ---
>  kernel/time/alarmtimer.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/time/alarmtimer.c b/kernel/time/alarmtimer.c
> index a519d3cab1a2..6aef4a0bed29 100644
> --- a/kernel/time/alarmtimer.c
> +++ b/kernel/time/alarmtimer.c
> @@ -586,7 +586,7 @@ static void alarm_timer_get(struct k_itimer *timr,
>  static int alarm_timer_del(struct k_itimer *timr)
>  {
>  	if (!rtcdev)
> -		return -ENOTSUPP;
> +		return -EOPNOTSUPP;
>  
>  	if (alarm_try_to_cancel(&timr->it.alarm.alarmtimer) < 0)
>  		return TIMER_RETRY;
> @@ -610,7 +610,7 @@ static int alarm_timer_set(struct k_itimer *timr, int flags,
>  	ktime_t exp;
>  
>  	if (!rtcdev)
> -		return -ENOTSUPP;
> +		return -EOPNOTSUPP;
>  
>  	if (flags & ~TIMER_ABSTIME)
>  		return -EINVAL;
> -- 
> 2.16.4
> 

  reply	other threads:[~2019-11-08 16:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-08 15:50 [PATCH v4.9-stable] alarmtimer: Change remaining ENOTSUPP to EOPNOTSUPP Petr Vorel
2019-11-08 16:58 ` Thadeu Lima de Souza Cascardo [this message]
2019-11-08 17:34 ` Greg KH

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=20191108165813.GB3753@calabresa \
    --to=cascardo@canonical.com \
    --cc=pvorel@suse.cz \
    --cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).