On Fri, Apr 10, 2015 at 3:44 PM, Joe Perches wrote:
> On Fri, 2015-04-10 at 15:30 -0700, Andy Lutomirski wrote:
>> On Fri, Aug 22, 2014 at 11:14 AM, Joe Perches wrote:
>> > On Fri, 2014-08-22 at 11:05 -0700, Andy Lutomirski wrote:
>> >> ENOSYS means that a nonexistent system call was called. We
On Fri, 2015-04-10 at 15:30 -0700, Andy Lutomirski wrote:
> On Fri, Aug 22, 2014 at 11:14 AM, Joe Perches wrote:
> > On Fri, 2014-08-22 at 11:05 -0700, Andy Lutomirski wrote:
> >> ENOSYS means that a nonexistent system call was called. We have a
> >> bad habit of using it for things like invalid
On Fri, Aug 22, 2014 at 11:14 AM, Joe Perches wrote:
> On Fri, 2014-08-22 at 11:05 -0700, Andy Lutomirski wrote:
>> ENOSYS means that a nonexistent system call was called. We have a
>> bad habit of using it for things like invalid operations on
>> otherwise valid syscalls. We should avoid this i
On Fri, 2014-08-22 at 11:05 -0700, Andy Lutomirski wrote:
> ENOSYS means that a nonexistent system call was called. We have a
> bad habit of using it for things like invalid operations on
> otherwise valid syscalls. We should avoid this in new code.
Seems sensible thanks for persisting.
Andrew
ENOSYS means that a nonexistent system call was called. We have a
bad habit of using it for things like invalid operations on
otherwise valid syscalls. We should avoid this in new code.
Signed-off-by: Andy Lutomirski
---
Pervasive incorrect usage of ENOSYS came up at the kernel summit ABI
revi
5 matches
Mail list logo
