From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: "Philip A. Prindeville" <philipp@redfish-solutions.com>
Cc: John Linville <linville@tuxdriver.com>,
wireless <linux-wireless@vger.kernel.org>,
Pavel Roskin <proski@gnu.org>
Subject: Re: [PATCH] Don't build PCMCIA modules when PCMCIA isn't present
Date: Tue, 18 Aug 2009 16:34:24 -0700 [thread overview]
Message-ID: <43e72e890908181634y435b0c8wdab9fb423046a08f@mail.gmail.com> (raw)
In-Reply-To: <4A864BB1.8020307@redfish-solutions.com>
On Fri, Aug 14, 2009 at 10:46 PM, Philip A.
Prindeville<philipp@redfish-solutions.com> wrote:
> From: Philip A Prindeville <philipp@redfish-solutions.com>
>
> If you're building for a platform that has (for example) no PCMCIA/
> Cardbus, then having a single knob to turn to disable this is a
> major win. Especially if more devices get add later that are
> PCMCIA-based.
Applied, thanks Phillip.
Luis
prev parent reply other threads:[~2009-08-18 23:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-15 5:46 [PATCH] Don't build PCMCIA modules when PCMCIA isn't present Philip A. Prindeville
2009-08-18 23:34 ` Luis R. Rodriguez [this message]
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=43e72e890908181634y435b0c8wdab9fb423046a08f@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=philipp@redfish-solutions.com \
--cc=proski@gnu.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).