Re: what is the current/ongoing state of userspace access to GPIO?

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

Subject: Re: what is the current/ongoing state of userspace access to GPIO?
From: Greg KH <greg@xxxxxxxxx>
Date: Thu, 25 May 2017 21:14:50 +0200
Cc: Clemens Gruber <clemens.gruber@xxxxxxxxxxxx>, kernelnewbies@xxxxxxxxxxxxxxxxx
In-reply-to: <alpine.LFD.2.20.1705250827430.18747@localhost.localdomain>
References: <alpine.LFD.2.20.1705240751450.19470@localhost.localdomain> <20170524125015.GA1245@archie.localdomain> <alpine.LFD.2.20.1705250827430.18747@localhost.localdomain>
User-agent: Mutt/1.8.2 (2017-04-18)

On Thu, May 25, 2017 at 03:02:24PM -0400, Robert P. J. Day wrote:
> 
>   thoughts?

Why not ask on the linux-gpio mailing list?

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Follow-Ups:
- Re: what is the current/ongoing state of userspace access to GPIO?
  - From: Robert P. J. Day

References:
- what is the current/ongoing state of userspace access to GPIO?
  - From: Robert P. J. Day
- Re: what is the current/ongoing state of userspace access to GPIO?
  - From: Clemens Gruber
- Re: what is the current/ongoing state of userspace access to GPIO?
  - From: Robert P. J. Day

Prev by Date: Lock contention determination
Next by Date: Re: what is the current/ongoing state of userspace access to GPIO?
Previous by thread: Re: what is the current/ongoing state of userspace access to GPIO?
Next by thread: Re: what is the current/ongoing state of userspace access to GPIO?
Index(es):
- Date
- Thread

[Index of Archives] [Newbies FAQ] [Linux Kernel Mentors] [Linux Kernel Development] [IETF Annouce] [Git] [Networking] [Security] [Bugtraq] [Yosemite] [MIPS Linux] [ARM Linux] [Linux RAID] [Linux SCSI] [Linux ACPI]

Powered by Linux