From: Ian Abbott <abbotti@mev.co.uk>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"fmhess@users.sourceforge.net" <fmhess@users.sourceforge.net>,
Ian Abbott <ian.abbott@mev.co.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/4] staging: comedi: Kconfig: menuconfig options should be bool not tristate
Date: Tue, 19 Jun 2012 09:35:25 +0100 [thread overview]
Message-ID: <4FE039CD.8070209@mev.co.uk> (raw)
In-Reply-To: <ADE657CA350FB648AAC2C43247A983F0020698DBD3D9@AUSP01VMBX24.collaborationhost.net>
On 2012-06-19 02:01, H Hartley Sweeten wrote:
> On Monday, June 18, 2012 5:31 PM, Greg KH wrote:
>> Below is the .config I use. Apply your patch, and select 'y' for the
>> different options it asks for when running 'make oldconfig' and then see
>> the build errors.
>
> Ok. It looks like the patch below should fix it. Can you test it?
> config COMEDI_ADL_PCI7296
> tristate "ADLink PCI-7296 96 ch. digital io board support"
> + select COMED_8255
> ---help---
> Enable support for ADlink PCI-7296 96 ch. digital io board support
That one has a typo bug.
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=-
-=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
next prev parent reply other threads:[~2012-06-19 8:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 22:20 [PATCH 1/4] staging: comedi: Kconfig: menuconfig options should be bool not tristate H Hartley Sweeten
2012-06-18 23:59 ` Greg KH
2012-06-19 0:01 ` H Hartley Sweeten
2012-06-19 0:16 ` H Hartley Sweeten
2012-06-19 0:30 ` Greg KH
2012-06-19 1:01 ` H Hartley Sweeten
2012-06-19 8:35 ` Ian Abbott [this message]
2012-06-19 16:32 ` H Hartley Sweeten
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=4FE039CD.8070209@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=fmhess@users.sourceforge.net \
--cc=gregkh@linuxfoundation.org \
--cc=hartleys@visionengravers.com \
--cc=ian.abbott@mev.co.uk \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox