Re: [PATCH v3.16] alarmtimer: Use EOPNOTSUPP instead of ENOTSUPP

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH v3.16] alarmtimer: Use EOPNOTSUPP instead of ENOTSUPP
From: Petr Vorel <pvorel@xxxxxxx>
Date: Tue, 19 Nov 2019 15:53:02 +0100
Cc: stable@xxxxxxxxxxxxxxx, Thadeu Lima de Souza Cascardo <cascardo@xxxxxxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>
In-reply-to: <43b375712cdd400695af9e4e8e4a9381706601fc.camel@decadent.org.uk>
Reply-to: Petr Vorel <pvorel@xxxxxxx>
User-agent: Mutt/1.11.3 (2019-02-01)

Hi Ben,

> I've queued this up, thanks.
Thanks!
> In future please remember to include the upstream commit hash.
I'm sorry, I'll remember next time.


Kind regards,
Petr

References:
- [PATCH v3.16] alarmtimer: Use EOPNOTSUPP instead of ENOTSUPP
  - From: Petr Vorel
- Re: [PATCH v3.16] alarmtimer: Use EOPNOTSUPP instead of ENOTSUPP
  - From: Ben Hutchings

Prev by Date: Re: [PATCH 3.16 58/87] cifs: add spinlock for the openFileList to cifsInodeInfo
Next by Date: Re: [PATCH 3.16 000/132] 3.16.74-rc1 review
Previous by thread: Re: [PATCH v3.16] alarmtimer: Use EOPNOTSUPP instead of ENOTSUPP
Next by thread: stable 4.19.80 and 4.19.81: BAD! BarrierAck seen in drbd
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel] [Kernel Development Newbies] [Linux USB Devel] [Video for Linux] [Linux Audio Users] [Yosemite Hiking] [Linux Kernel] [Linux SCSI]

Powered by Linux