Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S941762AbcJZXUo (ORCPT ); Wed, 26 Oct 2016 19:20:44 -0400 Received: from mail-ua0-f171.google.com ([209.85.217.171]:34238 "EHLO mail-ua0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S936286AbcJZXUL (ORCPT ); Wed, 26 Oct 2016 19:20:11 -0400 MIME-Version: 1.0 In-Reply-To: <20161026191810.12275-3-dh.herrmann@gmail.com> References: <20161026191810.12275-1-dh.herrmann@gmail.com> <20161026191810.12275-3-dh.herrmann@gmail.com> From: Andy Lutomirski Date: Wed, 26 Oct 2016 16:19:50 -0700 Message-ID: Subject: Re: [RFC v1 02/14] bus1: provide stub cdev /dev/bus1 To: David Herrmann Cc: Tom Gundersen , Hannes Reinecke , Jiri Kosina , "linux-kernel@vger.kernel.org" , Andrew Morton , Josh Triplett , Greg KH , Arnd Bergmann , Steven Rostedt , Linus Torvalds Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 447 Lines: 11 On Oct 26, 2016 12:21 PM, "David Herrmann" wrote: > > From: Tom Gundersen > > Add the CONFIG_BUS1 option to enable the bus1 kernel messaging bus. If > enabled, provide the bus1.ko module with a stub cdev /dev/bus1. So far > it does not expose any API, but the full intended uapi is provided in > include/uapi/linux/bus1.h already. > This may have been covered elsewhere, but could this use syscalls instead?