From: Christoph Hellwig <hch@infradead.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>
Subject: Re: [GIT PULL] Staging driver patches for 3.19-rc1
Date: Wed, 17 Dec 2014 01:28:04 -0800 [thread overview]
Message-ID: <20141217092804.GA9424@infradead.org> (raw)
In-Reply-To: <20141215185638.GA8036@kroah.com>
On Mon, Dec 15, 2014 at 10:56:38AM -0800, Greg KH wrote:
> Ok, that was a bit snotty on my part, I apologize.
>
> But really, this is self-contained, doesn't touch any core
> infrastructure, and is really just like any other driver for hardware
> that people don't use. It shouldn't affect anything elsewhere in the
> kernel, so objecting to it seems odd to me.
I does dig into internals in quite nasty ways. I driver that is always
modular and just uses existing exported APIs in proper ways and adds no
to little new userspaces ABIs is one things. A new IPCs mechanisms that
pokes into internals and exposes a huge ABI/API is a totally different
thing.
next prev parent reply other threads:[~2014-12-17 9:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 17:55 [GIT PULL] Staging driver patches for 3.19-rc1 Greg KH
2014-12-15 18:23 ` Richard Weinberger
2014-12-15 18:30 ` Greg KH
2014-12-15 18:36 ` Richard Weinberger
2014-12-15 18:44 ` Greg KH
2014-12-15 19:04 ` Richard Weinberger
2014-12-15 19:32 ` Greg KH
2014-12-28 17:52 ` Pavel Machek
2014-12-15 18:39 ` Christoph Hellwig
2014-12-15 18:41 ` Greg KH
2014-12-15 18:56 ` Greg KH
2014-12-16 9:35 ` Richard Weinberger
2014-12-17 9:28 ` Christoph Hellwig [this message]
2014-12-28 17:53 ` Andoid Binder sneaking in [was Re: [GIT PULL] Staging driver patches for 3.19-rc1] Pavel Machek
2014-12-28 17:53 ` Pavel Machek
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=20141217092804.GA9424@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.weinberger@gmail.com \
--cc=torvalds@linux-foundation.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 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.