From: Guenter Roeck <linux@roeck-us.net>
To: Jean Delvare <jdelvare@suse.de>, linux-kernel@vger.kernel.org
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
Marc Zyngier <marc.zyngier@arm.com>,
Wim Van Sebroeck <wim@iguana.be>,
Damien Riegel <damien.riegel@savoirfairelinux.com>
Subject: Re: [PATCH 0/3] Add hardware dependency to TS-4800 board drivers
Date: Tue, 9 Feb 2016 06:28:07 -0800 [thread overview]
Message-ID: <56B9F777.7000608@roeck-us.net> (raw)
In-Reply-To: <20160209111549.7e9b4fbb@endymion>
On 02/09/2016 02:15 AM, Jean Delvare wrote:
> Hi all,
>
> This adds hardware dependency to 3 drivers for the Technologic Systems
> TS-4800 board. Thanks to these dependencies, users of other systems
> will not accidentally enable these drivers.
>
> Once again I must urge subsystem maintainers to add such dependencies
> to all new drivers which needs them. The lack of such dependencies
> makes distribution kernel maintainers' lives a nightmare.
>
> [PATCH 1/3] watchdog: ts4800: add hardware dependency
> [PATCH 2/3] Input: ts4800: add hardware dependency
> [PATCH 3/3] irqchip/ts4800: Add hardware dependency
>
How about TOUCHSCREEN_TS4800 ?
Guenter
next prev parent reply other threads:[~2016-02-09 14:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 10:15 [PATCH 0/3] Add hardware dependency to TS-4800 board drivers Jean Delvare
2016-02-09 10:17 ` [PATCH 1/3] watchdog: ts4800: add hardware dependency Jean Delvare
2016-02-09 14:28 ` Guenter Roeck
2016-03-04 19:36 ` Wim Van Sebroeck
2016-02-09 10:18 ` [PATCH 2/3] Input: " Jean Delvare
2016-03-04 19:42 ` Dmitry Torokhov
2016-02-09 10:19 ` [PATCH 3/3] irqchip/ts4800: Add " Jean Delvare
2016-02-18 1:44 ` Jason Cooper
2016-02-09 14:28 ` Guenter Roeck [this message]
2016-02-09 15:14 ` [PATCH 0/3] Add hardware dependency to TS-4800 board drivers Jean Delvare
2016-02-09 15:08 ` Damien Riegel
2016-02-09 15:16 ` Guenter Roeck
2016-02-09 15:24 ` Jean Delvare
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=56B9F777.7000608@roeck-us.net \
--to=linux@roeck-us.net \
--cc=damien.riegel@savoirfairelinux.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jason@lakedaemon.net \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=tglx@linutronix.de \
--cc=wim@iguana.be \
/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.