From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932587AbcERQEJ (ORCPT ); Wed, 18 May 2016 12:04:09 -0400 Received: from mx1.redhat.com ([209.132.183.28]:60787 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932410AbcERQEG (ORCPT ); Wed, 18 May 2016 12:04:06 -0400 From: Jes Sorensen To: Greg KH Cc: David Kershner , corbet@lwn.net, tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com, erik.arfvidson@unisys.com, timothy.sell@unisys.com, hofrat@osadl.org, dzickus@redhat.com, alexander.curtin@unisys.com, janani.rvchndrn@gmail.com, sudipm.mukherjee@gmail.com, prarit@redhat.com, david.binder@unisys.com, nhorman@redhat.com, dan.j.williams@intel.com, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, driverdev-devel@linuxdriverproject.org, sparmaintainer@unisys.com Subject: Re: [PATCH 0/5] add bus driver for Unisys s-Par paravirtualized devices to arch/x86 References: <1463470081-24223-1-git-send-email-david.kershner@unisys.com> <20160517135133.GC18227@kroah.com> <20160517142735.GA19617@kroah.com> <20160518000359.GA325@kroah.com> Date: Wed, 18 May 2016 12:03:58 -0400 In-Reply-To: <20160518000359.GA325@kroah.com> (Greg KH's message of "Tue, 17 May 2016 17:03:59 -0700") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Wed, 18 May 2016 16:04:01 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Greg KH writes: > On Tue, May 17, 2016 at 07:49:53PM -0400, Jes Sorensen wrote: >> > Ok, but still no need to put it under arch/ anything, it should go in >> > drivers/ like all other drivers and busses are, no matter what the arch >> > it happens to run on is. >> >> I don't think thats obvious. arch/x86/kvm is an example of this, Sparc >> and PPC also have their stuff under arch/. > > For some things, yes, but let's not make the same mistakes as others :) > > Look at drivers/hv/ for an example of a very x86-only bus and driver > subsystem living in drivers/ Please don't burry driver stuff in arch/ > the ARM developers are trying to fix their mistakes of the past and move > all of their cruft out of arch/ for that reason. Works for me. So should they put it in drivers/visorbus or drivers/bus/visorbus? What about drivers/virt? Would you suggest hv and xen gets moved in there? Cheers, Jes