From: "Woodhouse, David" <david.woodhouse-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: Linux I2C <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Hans de Goede <hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] i2c-i801: Don't depend on other kernel driver config options
Date: Fri, 13 May 2011 11:23:06 +0100 [thread overview]
Message-ID: <1305282187.30435.343.camel@i7.infradead.org> (raw)
In-Reply-To: <20110513120100.4d47410a-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 658 bytes --]
On Fri, 2011-05-13 at 11:01 +0100, Jean Delvare wrote:
> Don't let other driver config options influence us, as it makes the
> code more complex and fragile for a small benefit. There's nothing
> wrong with instantiating I2C devices even if they don't have a driver.
> And we're talking about 835 extra bytes in the binary on x86-64,
> that's hardly worth arguing about.
Looks sane to me; thanks. Should it be CONFIG_DMI instead of (or in
addition to) CONFIG_X86?
--
David Woodhouse Open Source Technology Centre
David.Woodhouse-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org Intel Corporation
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 6242 bytes --]
next prev parent reply other threads:[~2011-05-13 10:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 10:01 [PATCH] i2c-i801: Don't depend on other kernel driver config options Jean Delvare
[not found] ` <20110513120100.4d47410a-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2011-05-13 10:23 ` Woodhouse, David [this message]
[not found] ` <1305282187.30435.343.camel-W2I5cNIroUsVm/YvaOjsyQ@public.gmane.org>
2011-05-15 11:12 ` 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=1305282187.30435.343.camel@i7.infradead.org \
--to=david.woodhouse-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@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 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).