From: Randy Dunlap <randy.dunlap@oracle.com>
To: Alexander Kurz <linux@blala.de>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
Frank Mori Hess <fmhess@users.sourceforge.net>,
Dominik Brodowski <linux@dominikbrodowski.net>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging/comedi: new Kconfig and Makefiles, drivers grouped by bustype.
Date: Mon, 10 May 2010 10:19:53 -0700 [thread overview]
Message-ID: <4BE84039.6000703@oracle.com> (raw)
In-Reply-To: <alpine.DEB.1.10.1005081218220.5727@blala.de>
On 05/08/10 01:21, Alexander Kurz wrote:
> This is a new Kconfig and Makefikes for staging/comedi.
> The drivers are sorted now alphabetically in sub-menus
> depending on the bustype.
> I did some basiy dependancy tests, but there still may
> be a lot that I missed.
>
> From c53596606230a4a8ee7dd76b48cf6b10a059e8f7 Mon Sep 17 00:00:00 2001
> From: Alexander Kurz <linux@kbdbabel.org>
> Date: Fri, 7 May 2010 22:46:17 +0200
> Subject: [PATCH] staging/comedi: new Kconfig and Makefiles, drivers grouped by bustype.
> PC/104-drivers went into ISA,
> PC/104+ went into PCI,
> Drivers without a bustype went into "misc".
> In doubt drivers supporting both ISA/PCI went into PCI.
> Drivers without any detailed hardware info went into ISA, e.g. fl512.c
> Some NI drivers are used by other NI drivers from different bustypes
> are grouped seperately in NI_COMMON.
Hi,
I didn't review the patch in detail (I'm surprised to see such a large Kconfig
file patch), it does seem to do what is needed to prevent build errors that I was
seeing, but it needs more testing time...
Thanks.
> Signed-off-by: Alexander Kurz <linux@kbdbabel.org>
> ---
> drivers/staging/comedi/Kconfig | 1274 +++++++++++++++++++++++++++-
> drivers/staging/comedi/drivers/Makefile | 245 +++---
> drivers/staging/comedi/kcomedilib/Makefile | 2 +-
> 3 files changed, 1392 insertions(+), 129 deletions(-)
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-05-10 17:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-08 8:21 [PATCH] staging/comedi: new Kconfig and Makefiles, drivers grouped by bustype Alexander Kurz
2010-05-10 17:19 ` Randy Dunlap [this message]
2010-05-14 19:01 ` Greg KH
2010-05-15 0:29 ` Frank Mori Hess
2010-05-15 3:44 ` Greg KH
2010-05-19 17:32 ` Randy Dunlap
2010-05-19 20:32 ` [PATCH 2/2] staging/comedi: fixing ni_tio to mite PCI dependancy Alexander Kurz
2010-05-19 21:10 ` Randy Dunlap
2010-05-15 12:03 ` [PATCH] staging/comedi: new Kconfig and Makefiles, drivers grouped by bustype Alexander Kurz
2010-05-16 19:30 ` Frank Mori Hess
2010-05-15 12:09 ` [PATCH] staging/comedi: Kconfig dependancy fixes Alexander Kurz
2010-05-18 21:28 ` Greg KH
2010-05-19 19:13 ` [PATCH] staging/comedi: fixing 8255 and DAS08 Kconfig dependancies Alexander Kurz
2010-05-15 18:48 ` [PATCH] staging/comedi: new Kconfig and Makefiles, drivers grouped by bustype Ian Abbott
2010-05-24 10:05 ` Martyn Welch
2010-05-24 18:41 ` Greg KH
2010-05-25 7:04 ` Martyn Welch
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=4BE84039.6000703@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=fmhess@users.sourceforge.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@blala.de \
--cc=linux@dominikbrodowski.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).