From: "Chris Verges" <chrisv-TDbMi1wZJFNf2ZY+IB7+a9BPR1lH4CV8@public.gmane.org>
To: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>,
linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Dmitry Torokhov
<dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: uclinux-dist-devel-ZG0+EudsQA8dtHy/vicBwGD2FQJk+8+b@public.gmane.org,
Luotao Fu <l.fu-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
Michael Hennerich
<michael.hennerich-OyLXuOCK7orQT0dZR+AlfA@public.gmane.org>,
Barry Song <barry.song-OyLXuOCK7orQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH v3] input/misc: new ADXL345/346 driver
Date: Tue, 20 Oct 2009 11:46:08 -0700 [thread overview]
Message-ID: <68FBE0F3CE97264395875AC1C468F22C1CA0D8@mail03.cyberswitching.local> (raw)
In-Reply-To: 1256028039-15044-1-git-send-email-vapier@gentoo.org
Hi Mike and Michael,
>+config INPUT_ADXL34X
>+config INPUT_ADXL34X_I2C
>+config INPUT_ADXL34X_SPI
Should the INPUT_ADXL34X option be auto-selected when the _I2C or _SPI
counterparts are selected? Something like:
config HAVE_INPUT_ADXL34X
config INPUT_ADXL34X
depends on HAVE_INPUT_ADXL34X
config INPUT_ADXL34X_I2C
bool "..."
depends on I2C
select HAVE_INPUT_ADXL34X
config INPUT_ADXL34X_SPI
bool "..."
depends on SPI_MASTER
select HAVE_INPUT_ADXL34X
The end user would only see the INPUT_ADXL34X_SPI and INPUT_ADXL34X_I2C
options, with the common INPUT_ADXL34X option being automagically
selected due to the reverse dependencies.
Chris
next prev parent reply other threads:[~2009-10-20 18:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 10:27 [PATCH] input/misc: new ADXL345/346 driver Mike Frysinger
[not found] ` <1255516029-30023-1-git-send-email-vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2009-10-14 10:54 ` [PATCH v2] " Mike Frysinger
2009-10-16 4:36 ` Dmitry Torokhov
[not found] ` <20091016043627.GC11582-WlK9ik9hQGAhIp7JRqBPierSzoNAToWh@public.gmane.org>
2009-10-16 5:39 ` Mike Frysinger
[not found] ` <8bd0f97a0910152239v3c889a95rd9b100e3e7204e98-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-16 5:44 ` Dmitry Torokhov
[not found] ` <20091016054414.GE11582-WlK9ik9hQGAhIp7JRqBPierSzoNAToWh@public.gmane.org>
2009-10-16 5:53 ` Mike Frysinger
2009-10-16 6:57 ` [Uclinux-dist-devel] " Mike Frysinger
2009-10-16 7:22 ` Dmitry Torokhov
[not found] ` <20091016072216.GH11582-WlK9ik9hQGAhIp7JRqBPierSzoNAToWh@public.gmane.org>
2009-10-16 8:20 ` Mike Frysinger
2009-10-16 9:06 ` Hennerich, Michael
2009-10-20 8:40 ` [PATCH v3] " Mike Frysinger
2009-10-20 18:46 ` Chris Verges [this message]
2009-10-21 2:32 ` [Uclinux-dist-devel] " Mike Frysinger
2010-06-25 7:14 ` Dmitry Torokhov
[not found] ` <20100625071425.GA631-WlK9ik9hQGAhIp7JRqBPierSzoNAToWh@public.gmane.org>
2010-06-25 13:59 ` Hennerich, Michael
2010-07-01 7:53 ` Dmitry Torokhov
2010-07-01 9:15 ` Hennerich, Michael
2010-07-01 16:08 ` Dmitry Torokhov
2010-07-21 13:50 ` [Uclinux-dist-devel] " Mike Frysinger
2010-07-23 6:44 ` Dmitry Torokhov
2010-08-05 12:30 ` Hennerich, Michael
2010-08-06 5:37 ` Dmitry Torokhov
2009-10-21 3:14 Dmitry Torokhov
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=68FBE0F3CE97264395875AC1C468F22C1CA0D8@mail03.cyberswitching.local \
--to=chrisv-tdbmi1wzjfnf2zy+ib7+a9bpr1lh4cv8@public.gmane.org \
--cc=barry.song-OyLXuOCK7orQT0dZR+AlfA@public.gmane.org \
--cc=dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=l.fu-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=michael.hennerich-OyLXuOCK7orQT0dZR+AlfA@public.gmane.org \
--cc=uclinux-dist-devel-ZG0+EudsQA8dtHy/vicBwGD2FQJk+8+b@public.gmane.org \
--cc=vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.