[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141030161752.GB21989@kroah.com>
Date: Thu, 30 Oct 2014 09:17:52 -0700
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Arnd Bergmann <arnd@...db.de>
Cc: linux-api@...r.kernel.org, linux-kernel@...r.kernel.org,
john.stultz@...aro.org, tj@...nel.org, marcel@...tmann.org,
desrt@...rt.ca, hadess@...ess.net, dh.herrmann@...il.com,
tixxdz@...ndz.org, simon.mcvittie@...labora.co.uk,
daniel@...que.org, alban.crequy@...labora.co.uk,
javier.martinez@...labora.co.uk, teg@...m.no
Subject: Re: [PATCH 00/12] Add kdbus implementation
On Thu, Oct 30, 2014 at 09:33:56AM +0100, Arnd Bergmann wrote:
> On Wednesday 29 October 2014 15:00:44 Greg Kroah-Hartman wrote:
> > drivers/misc/Kconfig | 1 +
> > drivers/misc/Makefile | 1 +
> > drivers/misc/kdbus/Kconfig | 11 +
> > drivers/misc/kdbus/Makefile | 19 +
> > drivers/misc/kdbus/bus.c | 450 ++++++
> > drivers/misc/kdbus/bus.h | 107 ++
> > drivers/misc/kdbus/connection.c | 1751 +++++++++++++++++++++
> > drivers/misc/kdbus/connection.h | 177 +++
> > drivers/misc/kdbus/domain.c | 477 ++++++
> >
>
> One very high-level common:
>
> Since this is going to be a very commonly used IPC mechanism, I don't
> like the idea of stuffing it into drivers/misc.
>
> How about putting it into drivers/kdbus or ipc/kdbus instead?
ipc/kdbus seems good to me. I didn't want to "pollute" drivers/ with
any new subdirectories, it seems to grow fast enough as it is...
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists