All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergej Bauer <sergej.bauer@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: Arnd Bergmann <arnd@arndb.de>, Paul Bolle <pebolle@tiscali.nl>,
	linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org
Subject: Re: [PATCH 1/1] Add mkopci driver
Date: Sat, 21 Mar 2015 21:29:18 +0300	[thread overview]
Message-ID: <201503212129.18159.sergej.bauer@gmail.com> (raw)
In-Reply-To: <550DAB20.5090504@nod.at>

Thanks a lot :)

But the driver is really very insignificant.
I was wondering about sysfs before, but consumers will not be very happy to get another revision of userspace tools/library.
So this is their own problems :)

Thanks again and sorry for this uselessness dialogue :)

On Saturday 21 March 2015 20:32:16 Richard Weinberger wrote:
> Am 21.03.2015 um 18:24 schrieb Sergej Bauer:
> > Ok, I realized uselessness of merging this driver...
> 
> Please don't give up that fast!
> See: http://airlied.livejournal.com/#item80112
> 
> > And you brought me to a standstill:
> >> passthrough. In either case, both the ioctl interface and the procfs interface have no future
> > But what will be after ioctl?
> 
> We will not drop the ioctl() system call. But having a character device with random
> ioctl()s is not really a good driver design.
> Today we have much more elegant ways to interact between kernel and userspace than ioctl().
> For example sysfs or netlink.
> 
> Thanks,
> //richard
> 

  reply	other threads:[~2015-03-21 18:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-20 12:10 [PATCH 1/1] Add mkopci driver sergej.bauer
2015-03-20 12:43 ` Richard Weinberger
2015-03-20 12:44   ` Richard Weinberger
2015-03-21 12:11   ` Paul Bolle
2015-03-21 14:41   ` Sergej Bauer
2015-03-21 15:41     ` Arnd Bergmann
2015-03-21 17:24       ` Sergej Bauer
2015-03-21 17:32         ` Richard Weinberger
2015-03-21 18:29           ` Sergej Bauer [this message]
2015-03-26 22:47 ` 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=201503212129.18159.sergej.bauer@gmail.com \
    --to=sergej.bauer@gmail.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    --cc=richard@nod.at \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.